Imagine you are sailing down a wide river and observing the changing landscape on either side. Fields give way to forests, tributaries and streams flow into the river, bridges cross over, and you know that one side of the river is managed by a government agency, while the other is subdivided into land ownership parcels of different sizes. The connectedness, adjacency, and proximity between these features can be summed up in one word: topology.Geodatabase topology allows you to define the spatial relationships you want protected in your GIS data. By doing so, no matter how much you edit, twist, bend, or squash your feature data, things stay connected, adjacent, or within the areas they belong. This course is designed to get you started with geodatabase topology.After completing this course, you will be able to:Use visual inspection and topology to identify and correct errors.Build a geodatabase topology.Choose and apply topology rules.

Countywide Surface Topology

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. The transfer process for the CHCU vegetation mapping project involved taking the interpreted line work and rendering it into a comprehensive digital network of attributed polygons. To accomplish this, we created an ArcInfo© GIS database using in-house protocols. The protocols consist of a shell (master file) of Arc Macro Language (AML) scripts and menus (nearly 100 files) that automate the transfer process, thus insuring that all spatial and attribute data are consistent and stored properly. The actual transfer of information from the interpreted orthophotos to a digital, geo-referenced format involved scanning, rasterizing, vectorizing, cleaning, building topology, and labeling each polygon.

The two versions of the printed Topographic Map Index are:

• the 1:100,000 / 1:250,000 Topographic Map Index
• the 1:50,000 Topographic Map Index

Topographic map indexes are also available as digital data.
Maps are
listed by name on the back of the index. The 1:50,000 Index also lists availability of Orthophoto Map (OPM) and Topographic Line Map (TLM) for available 1:50,000 maps.
Both indexes are available in printed form from your nearest topographic map retailer or from the Geoscience Australia
Sales Centre. You can also download PDFs of each index.
Note: To print these PDFs at 100% requires an A0 printer. They are best for viewing on-screen. For new maps which may have been released after these indexes were published, please refer to the new releases page or use the Product
Search tool.
Product Specifications Coverage: Australia Currency: 2004 (PDF); 2004 (data) Coordinates: Geographical Datum: GDA94 Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif; PDF (maps only); Paper Map (maps only) Medium: GIS Data Free online, free folded map or CD-ROM (fee applies) Forward Program: Updated annually

City of Cambridge, MA, GIS basemap development project encompasses the land area of City of Cambridge with a 200-foot fringe surrounding the area and Charles River shoreline towards Boston. The basemap data was developed at 1" = 40' mapping scale using digital photogrammetric techniques. Planimetric features; both man-made and natural features like vegetation, rivers have been depicted. These features are important to all GIS/mapping applications and publication. A set of data layers such as Buildings, Roads, Rivers, Utility structures, 1 ft interval contours are developed and represented in the geodatabase. The features are labeled and coded in order to represent specific feature class for thematic representation and topology between the features is maintained for an accurate representation at the 1:40 mapping scale for both publication and analysis. The basemap data has been developed using procedures designed to produce data to the National Standard for Spatial Data Accuracy (NSSDA) and is intended for use at 1" = 40 ' mapping scale. Where applicable, the vertical datum is NAVD1988.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription TYPE type: Stringwidth: 50precision: 0 All types are flight of stairs (plaza stairs in layer plazas)

TOP_GL type: Doublewidth: 8precision: 38 Elevation of highest point above ground level (NAVD88)

ELEV_SL type: Doublewidth: 8precision: 38 Elevation of stairs above sea level (NAVD88)

TOP_SL type: Doublewidth: 8precision: 38 Elevation of highest point above sea level (NAVD88)

BASE_ELEV type: Doublewidth: 8precision: 38 Base elevation of structure (NAVD88)

STAIR_TYPE type: Stringwidth: 10precision: 0 Building or walkway

ELEV_GL type: Doublewidth: 8precision: 38 Elevation of roofline edge above ground level (NAVD88)

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This map is suitable for school, office and home use as a single-sheet wall poster or as a handy reference item. The map includes more than 2000 named features as well as a gazetteer on the back of the map as an aid to locating places of interest. At this scale 1cm on the map represents 50km on the ground. Available flat (98.5cm x 84cm) or folded with cover (11cm x 23cm). Digital data at this scale, suitable for use in a GIS is also available for free download. Product Specifications Coverage: Complete coverage of Australia Currency: Last revised 2007 Coordinates:Geographical Datum: (GDA94); AHD Projection: Lambert Conformal Conic on two standard parallels (18o and 36o) Medium: Paper - flat and folded copies

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The Office of the Geographer’s Global Large Scale International Boundary Detailed Polygons file combines two datasets, the Office of the Geographer’s Large Scale International Boundary Lines and NGA shoreline data. The LSIB is believed to be the most accurate worldwide (non- W. Europe) international boundary vector line file available. The lines reflect U.S. government (USG) policy and thus not necessarily de facto control. The 1:250,000 scale World Vector Shoreline (WVS) coastline data was used in places and is generally shifted by several hundred meters to over a km. There are no restrictions on use of this public domain data. The Tesla Government PiX team performed topology checks and other GIS processing while merging data sets, created more accurate island shoreline in numerous cases, and worked closely with the US Dept. of State Office of the Geographer on quality control checks.

Methodology: Tesla Government’s Protected Internet Exchange (PiX) GIS team converted the LSIB linework and the island data provided by the State Department to polygons. The LSIB Admin 0 world polygons (Admin 0 polygons) were created by conflating the following datasets: Eurasia_Oceania_LSIB7a_gen_polygons, Africa_Americas_LSIB7a_gen_polygons, Africa_Americas_LSIB7a, Eurasia_LSIB7a, additional updates from LSIB8, WVS shoreline data, and other shoreline data from United States Government (USG) sources. The two simplified polygon shapefiles were merged, dissolved, and converted to lines to create a single global coastline dataset. The two detailed line shapefiles (Eurasia_LSIB7a and Africa_Americas_LSIB7a) were merged with each other and the coastlines to create an international boundary shapefile with coastlines. The dataset was reviewed for the following topological errors: must not self overlap, must not overlap, and must not have dangles. Once all topological errors were fixed, the lines were converted to polygons. Attribution was assigned by exploding the simplified polygons into multipart features, converting to centroids, and spatially joining with the newly created dataset. The polygons were then dissolved by country name. Another round of QC was performed on the dataset through the data reviewer tool to ensure that the conversion worked correctly. Additional errors identified during this process consisted of islands shifted from their true locations and not representing their true shape; these were adjusted using high resolution imagery whereupon a second round of QC was applied with SRTM digital elevation model data downloaded from USGS. The same procedure was performed for every individual island contained in the islands from other USG sources.
After the island dataset went through another round of QC, it was then merged with the Admin 0 polygon shapefile to form a comprehensive world dataset. The entire dataset was then evaluated, including for proper attribution for all of the islands, by the Office of the Geographer.

These data contain a Gulf of Mexico OCS Region NAD27 scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries and are updated as needed. OPDs are mapping products produced and used by the BOEM to delineate areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered when leasing offshore waters. The OPDs serve as the legal definition for BOEM offshore boundary coordinates and area descriptions. These data show only the outline of the maps that are available from BOEM. Only the most recently published paper or pdf versions of the OPDs should be used for official or legal purposes. Further information on the history of the development of OPDs can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

Background

The soil map of Israel was first published by Rabinovitch et al. in 1969. It was a massive work that took place 5 years. The map was published in a printed format at a 1:250,000 scale. Until now, a digital version of this map was not available. Accordingly, we carefully digitized the soil map of Rabinovitch and provided the map herein.

Materials and Methods

This dataset contains georeferenced raster layers of the soil map (1:250,000) of Israel published by Ravikovitch (1969). The georectification was done using control points located on the borders of Israel. With this information, it was possible to create polygons over the georeferenced raster layers. This was done using the editing tool of ArcGIS 10.3. For each polygon we assigned the same classification provided by Ravikovitch (1969). Once all the polygons were created, topological corrections were applied using the method of Longley et al., (2015) in order to rectify possible inaccuracies in the digitation. To this end, we used the topology tool of ArcGIS 10.3 applying two rules:

• polygons must not have gaps
• polygons must not overlap.

Following these corrections, the polygons were re-evaluated and further edited where necessary to improve accuracy.

This publication contains:

• the northern and the southern sections of the Israel map of soils after the georectification in geotif format
• the final product of the cartographic edition of the Israel map of soils in shapefile format

Please, if you are going to make use of this map, cite this publication properly.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. Instrumental to the photo interpretive effort was the use of the GPS located vegetation plots collected by the field crew. These plots provided an idea of what the signatures of the individual map units should look like. In addition to the tablular data associated with each vegetation plot were five photographs collected at each plot. These photographs helped not only in identifying the immediate area but also provided us with a “look” at the areas surrounding the vegetation plot which might be a different map unit. These photographs may be “hyperlinked” within ArcMap to the salient vegetation observation point for a better concept of on the ground conditions.All interpreted mylar layers were scanned at 300 dpi. Each scanned mylar was then rectified to the NAIP base layer using recognizable ground features as registration points. The resulting scan produced a raster image that was subsequently vectorized. Each vectorized output was then extensively edited to produce clean digital vector lines. From the digitized vectors we created polygons by building topology in the GIS program. Finally, we created labels for each polygon and used these to add the attribute information. Attribution for all the polygons at CHIC included information pertaining to map units, NVC associations, Anderson land-use classes, and other relevant data. Attribute data were taken directly from the interpreted photos or were added later using the orthophotos as a guide.

Ordnance Survey’s OS Terrain 50 DTM is a dataset representing the physical shape of the real world. The dataset includes 50metre GRID. The DTM data is captured from Ordnance Survey’s large scale aerial imagery. The product is updated and maintained annually. A free to use topology GIS dataset, to help you visualise simple landscapes in 3D and bring your geographic analysis to life.

This file is based on the Geospatial Services Division's Official Protraction Diagram (OPD)and Leasing Maps (LM). Each offshore area is defined by an API Number corresponding to those in the API Bulletin Number D12A. OPDs are numbered using the United Nations International Map of the World Numbering System, and are generally named for land or hydrographic features contained within the limits of the diagram. This data set contains Official Protraction Diagram (OPD) and Leasing Map (LM) outlines in ESRI shape file formats for the BOEM Gulf of Mexico Region. The use of OPDs and LMs makes it easier to refer to individual blocks within a region or planning area. These diagrams were clipped along the Submerged Lands Act (SLA) boundary and along lines contained in the Continental Shelf Boundaries (CSB) GIS data files to show only those blocks or portions thereof within federal jurisdiction. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for the exact OPD boundaries. Only the paper OPD or a digital image of them serves as OFFICIAL records.Official Protraction Diagrams and other cadastre information the BOEM produces are generated in accordance with 30 Code of Federal Regulations (CFR) Part 556.8 Subpart A, (formerly Part 256.8 Subpart A (2010)) to support Federal land ownership and mineral resource management. Further information on the SLA and development of this line from baseline points can be found in OCS Report BOEM 99-0006: Boundary Development on the Outer Continental Shelf. https://www.boem.gov/BOEM-Newsroom/Library/Publications/1999/99-0006-pdf.aspx Because GIS projection and topology functions can change or generalize coordinates, and because shapefiles cannot represent true arcs, these GIS files are considered to be approximate and are NOT an OFFICIAL record for the exact block coordinates or areas. The Official Protraction Diagrams (OPDs)and Leasing Maps (LMs) and Supplemental Official Block Diagrams (SOBDs) serve as the legal definition for BOEM offshore boundary coordinates and area descriptions and can be found at the following location: https://www.boem.gov/Official-Protraction-Diagrams/. Contains the protraction polygons clipped on the fedstate (SLA-Boundary) as of March 15, 2013. Used ArcCatalog to create shape files.

This data set contains boundary lines in ESRI Arc/Info export and Arc/View shape file formats the for Santa Barbara Channel Ecological Preserve and Buffer Zone offshore of Southern California. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for exact ecological preserve boundaries.

Aliquots are generated from Outer Continental Shelf (OCS) blocks by subdividing each block into 16ths, and this further subdivision allows for more detailed boundary delineation in offshore energy leasing. These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries. The aliquots use a letter designation in addition to their parent protraction number and OCS block number (e.g., NK18-02, 6822F). A full OCS block is 4800 x 4800 meters, while an aliquot measures 1200 x 1200 meters. Smaller, clipped aliquots are found along the Federal/State OCS boundary and along UTM zone borders. Only the most recently published paper or PDF versions of the Official Protraction Aliquot Diagram (OPAD) should be used for official or legal purposes.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

City of Cambridge, MA, GIS basemap development project encompasses the land area of City of Cambridge with a 200-foot fringe surrounding the area and Charles River shoreline towards Boston. The basemap data was developed at 1" = 40' mapping scale using digital photogrammetric techniques. Planimetric features; both man-made and natural features like vegetation, rivers have been depicted. These features are important to all GIS/mapping applications and publication. A set of data layers such as Buildings, Roads, Rivers, Utility structures, 1 ft interval contours are developed and represented in the geodatabase. The features are labeled and coded in order to represent specific feature class for thematic representation and topology between the features is maintained for an accurate representation at the 1:40 mapping scale for both publication and analysis. The basemap data has been developed using procedures designed to produce data to the National Standard for Spatial Data Accuracy (NSSDA) and is intended for use at 1" = 40 ' mapping scale. Where applicable, the vertical datum is NAVD1988.

City of Cambridge, MA, GIS basemap development project encompasses the land area of City of Cambridge with a 200-foot fringe surrounding the area and Charles River shoreline towards Boston. The basemap data was developed at 1" = 40' mapping scale using digital photogrammetric techniques. Planimetric features; both man-made and natural features like vegetation, rivers have been depicted. These features are important to all GIS/mapping applications and publication. A set of data layers such as Buildings, Roads, Rivers, Utility structures, 1 ft interval contours are developed and represented in the geodatabase. The features are labeled and coded in order to represent specific feature class for thematic representation and topology between the features is maintained for an accurate representation at the 1:40 mapping scale for both publication and analysis. The basemap data has been developed using procedures designed to produce data to the National Standard for Spatial Data Accuracy (NSSDA) and is intended for use at 1" = 40 ' mapping scale. Where applicable, the vertical datum is NAVD1988.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription TYPE type: Stringwidth: 50precision: 0 Type of pool (above ground or in-ground)

TOP_GL type: Doublewidth: 8precision: 38 Elevation of highest point above ground level (NAVD88)

TOP_SL type: Doublewidth: 8precision: 38 Elevation of highest point above sea level (NAVD88)

BASE_ELEV type: Doublewidth: 8precision: 38 Base elevation of structure (NAVD88)

ELEV_GL type: Doublewidth: 8precision: 38 Elevation of pool above ground level (NAVD88)

ELEV_SL type: Doublewidth: 8precision: 38 Elevation of pool above sea level (NAVD88)

description: This data set contains Official Protraction Diagram (OPD) outlines in ESRI Arc/Info export and Arc/View shape file formats for the BOEM Pacific Region. The use of OPD s makes it easier to refer to individual blocks within a region or planning area. Further information on the historic development of OPD s can be found in OCS Report BOEM 99-0006: Boundary Development on the Outer Continental Shelf. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for the exact OPD boundaries. Only the paper OPD or a digital image of them serve as OFFICIAL records.; abstract: This data set contains Official Protraction Diagram (OPD) outlines in ESRI Arc/Info export and Arc/View shape file formats for the BOEM Pacific Region. The use of OPD s makes it easier to refer to individual blocks within a region or planning area. Further information on the historic development of OPD s can be found in OCS Report BOEM 99-0006: Boundary Development on the Outer Continental Shelf. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for the exact OPD boundaries. Only the paper OPD or a digital image of them serve as OFFICIAL records.

View full metadata: https://www.cambridgema.gov/GIS/gisdatadictionary/Hydro/HYDRO_Wetlands

Description City of Cambridge, MA GIS basemap development project encompasses the land area of City of Cambridge with a 200 foot fringe surrounding the area and Charles River shoreline towards Boston. The basemap data was developed at 1" = 40' mapping scale using digital photogrammetric techniques. Planimetric features; both man-made and natural features like vegetation, rivers have been depicted. These features are important to all GIS/mapping applications and publication. A set of data layers such as Buildings, Roads, Rivers, Utility structures, 1 ft interval contours are developed and represented in the geodatabase. The features are labeled and coded in order to represent specific feature class for thematic representation and topology between the features is maintained for an accurate representation at the 1:40 mapping scale for both publication and analysis. The basemap data has been developed using procedures designed to produce data to the National Standard for Spatial Data Accuracy (NSSDA) and is intended for use at 1" = 40 ' mapping scale.

Purpose City of Cambridge 1" - 40' base map layers from an April 14, 2010 flyover. Basemap layers created by Infotech America.

About Edit Dates This data is automatically updated on a set schedule. The Socrata edit date may not reflect the actual edit dates in the data. For more details please see the update date on the full metadata page or view the edit date within the data rows.