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.

The goal of this paper is to present a new model of fuzzy topological relations for simple spatial objects in Geographic Information Sciences (GIS). The concept of computational fuzzy topological space is applied to simple fuzzy objects to efficiently and more accurately solve fuzzy topological relations, extending and improving upon previous research in this area. Firstly, we propose a new definition for simple fuzzy line segments and simple fuzzy regions based on computational fuzzy topology. And then, we also propose a new model to compute fuzzy topological relations between simple spatial objects, an analysis of the new model exposes:(1) the topological relations of two simple crisp objects; (2) the topological relations between one simple crisp object and one simple fuzzy object; (3) the topological relations between two simple fuzzy objects. In the end, we have discussed some examples to demonstrate the validity of the new model, through an experiment and comparisons of existing models, we showed that the proposed method can make finer distinctions, as it is more expressive than the existing fuzzy models.

Download In State Plane Projection Here. ** The Street Centerline feature class now follows the NG911/State of Illinois data specifications including a StreetNameAlias table. The download hyperlink above also contains a full network topology for use with the Esri Network Analyst extension ** These street centerlines were developed for a myriad of uses including E-911, as a cartographic base, and for use in spatial analysis. This coverage should include all public and selected private roads within Lake County, Illinois. Roads are initially entered using recorded documents and then later adjusted using current aerial photography. This dataset should satisfy National Map Accuracy Standards for a 1:1200 product. These centerlines have been provided to the United States Census Bureau and were used to conflate the TIGER road features for Lake County. The Census Bureau evaluated these centerlines and, based on field survey of 109 intersections, determined that there is a 95% confidence level that the coordinate positions in the centerline dataset fall within 1.9 meters of their true ground position. The fields PRE_DIR, ST_NAME, ST_TYPE and SUF_DIR are formatted according to United States Postal Service standards. Update Frequency: This dataset is updated on a weekly basis.

Countywide Surface Topology

This Administration feature is the single most valuable feature maintained by the GIS Services staff. It combines the maintenance of many individual polygon features in one main overall feature.It is part of a ArcGIS Topology class maintained with our parcel and zoning features in the Editing Feature Data Set.We use the shared editing capabilities of this topology class to leverage our maintenance procedures as simply as possible. Weekly, the individual features maintained with our Administration feature are created with ArcGIS dissolve function. These include Jurisdiction boundaries, Public Safety Response areas, Voting Precincts, Schools Attendance Zones, Inspections, Library Service Zones, and more.Generally, maintenance of this feature is controlled thru shared editing performed with our parcel/zoning edits with the use of the Topology features in ArcGIS. Changes to features maintained in the Administration feature are caused by a number of issues. Parcel edits, new Public Safety Stations, changes in Voting Precincts, Police Reporting districts and other changes occur often. Most changes can be facilitated by selecting one or more “Administrative” polygons and changing the appropriate attribute value. Use of the “Cut Polygon” task may be necessary in those cases where part of a polygon must be changed from a district to another. The appropriate attribute can be changed in the affected area as necessary.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE. A spatial representation of a subset of parcel features that contain special use characteristics. This polygon feature class is maintained in a geodatabase using topology with the TaxParcel feature class. The key attribute is AccessType, which describes the type of access (Prescriptive, Dedicated, or Private) on the feature.

This feature dataset includes feature classes for Surface Management Status and Federal Mineral Estate for Wyoming. This dataset is intended to represent the ownership & management information on BLM Master Title Plats(MTPs). Surface management will be identified by the Agency of Jurisdiction, when the surface is Federal. All other lands will be identified as either Private, Local Government, Wind River Indian Reservation (for tribal lands), State, State Parks & Historic Sites, University of Wyoming, or Wyoming Game & Fish Department. Private parcels do not identify the name of the individual owner. Mineral estate identifies only the Federal mineral interest. The feature dataset also includes topology rules established by the BLM Surface Management Agency National Data Standard. Updates for the June 2016 version includes multiple correction surface and mineral status, as well as conformance with the most recent version of CadNSDI PLSS data (current to June 6, 2016).

This polygon feature class is a data set compiled by DWR employees in 2013 and represents the statewide Groundwater Management Plan (Plan) boundaries predating the Sustainable Groundwater Management Act (SGMA) requirements. Each polygon represents the area in which a Plan is to be implemented. The boundaries were provided to DWR by the affiliated public agency and compiled into a single statewide data set. Spatial plan boundaries were provided by agencies to DWR either via shapefiles or PDFs. PDFs were georeferenced and turned into GIS layers by DWR employees. This feature class is for legacy purposes only and will not be changed nor updated. It needs to be memorialized for spatial coverage of Groundwater Management Plans prior to SGMA and because SGMA only requires medium and high priority basins to have a Groundwater Sustainability Plan. The Plans outlined in this shapefile by medium and high priority basins are in effect until SGMA goes into effect. Some low and very low priority basins will likely use the existing plans to get funding for future basin management (since it is only voluntary for them to provide a Plan under SGMA, but they already have one in place). The data set is considered complete because of its legacy status. However, anyone using the data set will notice boundary inconsistencies, agency plan overlaps, mismatches, and other topology errors. The data set is based on boundary estimations and in the cases of medium and high priority basins will be outdated with in implementation of SGMA.The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.1, dated September 11, 2019. This data set was not produced by DWR. Data were originally developed and supplied by each individual plan agency and compiled by DWR. DWR makes no warranties or guarantees — either expressed or implied— as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to GIS@water.ca.gov.

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 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 development of map units (map classes) and construction of a map legend is an iterative process that integrates the ecological vegetation classification units (plant associations, groups, etc.) described above with their spatial distribution as determined by the quality of the remote sensing imagery and on-the-ground reconnaissance work. Following NPS guidelines, the desired target is the development of map units that correspond to the plant-association level of the national classification, but this is contingent on being able to discern differences in the available imagery at that level using various remote techniques. Once a final supervised classification was completed, the resulting 45 classes were recoded into one of the 23 map units that best represented them. The image polygons developed from the object-oriented classification were imported as a feature dataset polygon layer in ESRI ArcGIS (v. 9.3), the file quality controlled, and topology built. The image polygons were then overlaid onto the recoded classification and the majority map unit was assigned as that polygon’s map unit.

This dataset is very large and detailed. As a result, there is no option to download a single dataset of the entire City as a shapefile (.shp) since it would exceed the 2 GB file size limit. If you intend to use this data in a CAD program, you should download the zone(s) in shapefile format and attach the data to your project.

 Download Shapefile by Zone(click on a zone to start the download)



  Zone A





  Zone C


  Zone B





  Zone D

The geographic data are built from the Technical Information Management System (TIMS). TIMS consists of two separate databases: an attribute database and a spatial database. The attribute information for offshore activities is stored in the TIMS database. The spatial database is a combination of the ARC/INFO and FINDER databases and contains all the coordinates and topology information for geographic features. The attribute and spatial databases are interconnected through the use of common data elements in both databases, thereby creating the spatial datasets. The data in the mapping files are made up of straight-line segments. If an arc existed in the original data, it has been replaced with a series of straight lines that approximate the arc. The Gulf of America OCS Region stores all its mapping data in longitude and latitude format. All coordinates are in NAD 27. Data can be obtained in three types of digital formats: INTERACTIVE MAP: The ArcGIS web maps are an interactive display of geographic information, containing a basemap, a set of data layers (many of which include interactive pop-up windows with information about the data), an extent, navigation tools to pan and zoom, and additional tools for geospatial analysis. SHP: A Shapefile is a digital vector (non-topological) storage format for storing geometric location and associated attribute information. Shapefiles can support point, line, and area features with attributes held in a dBASE format file. GEODATABASE: An ArcGIS geodatabase is a collection of geographic datasets of various types held in a common file system folder, a Microsoft Access database, or a multiuser relational DBMS (such as Oracle, Microsoft SQL Server, PostgreSQL, Informix, or IBM DB2). The geodatabase is the native data structure for ArcGIS and is the primary data format used for editing and data management.

GIS data digitised from 2 DigitalGlobe images at a scale of 1:1000.
The features were digitised using ArcGIS Pro and were created within a topology to ensure the spatial integrity of the data. Line data include coastlines, ice fronts and grounding lines. Polygon data include continent, island, ice tongue and rock features.

The images and data are of the Bølingen Islands and surrounding area, in the Prydz Bay region of Antarctica.
(18FEB23042505-P2AS-017311657010_01_P001.TIL; 18FEB23042504-M2AS-017311657010_01_P001.TIL)
(24MAR16035205-P2AS-017311660010_01_P001.TIL; 24MAR16035205-M2AS-017311660010_01_P001.TIL)
Copyright 2024 DigitalGlobe Incorporated, Longmont CO USA 80503-6493

The MassGIS Protected and Recreational OpenSpace data comprise a set of related data layers that represent parklands, forests, golf courses, playgrounds, wildlife sanctuaries, conservation lands, water supply areas, cemeteries, school ball fields, and other open land that may be classified as protected and/or recreational in use. Not all lands in this layer are protected in perpetuity, though nearly all have at least some level of protection. The layer includes lands owned by the state, cities and towns, federal agencies, and private and non-profit entities. The following types of land are included in this polygon datalayer: - conservation land - habitat protection with minimal recreation, such as walking trails - recreation land - outdoor facilities such as town parks, commons, playing fields, school fields, golf courses, bike paths, scout camps, and fish and game clubs. These may be privately or publicly owned facilities. - town forests - parkways - green buffers along roads, if they are a recognized conservation resource - agricultural land - land protected under an Agricultural Preservation Restriction (APR) and administered by the state Department of Agricultural Resources (DAR, formerly the Dept. of Food and Agriculture (DFA)) - aquifer protection land - not zoning overlay districts - watershed protection land - not zoning overlay districts - cemeteries - if a recognized conservation or recreation resource - forest land -- if designated as a Forest Legacy Area The OpenSpace layer includes two feature classes: * OPENSPACE_POLY - polygons of recreational and conservation lands as described above * OPENSPACE_ARC - attributed lines that represent boundaries of the polygons These feature classes are stored in a feature dataset named OPENSPACE that includes ArcGIS geodatabase topology.

This data set contains surface locations for oil and gas wells located in the Gulf of Mexico federal waters. Note: Wells are being added or modified continuously; obtaining updates of this database are required to know the true distribution of well data.Because GIS projection and topology functions can change or generalize coordinates, these GIS files are considered to be approximate and are NOT an OFFICIAL record.Contains the well surface locations as of March 2015.

State House Districts: The Virginia House of Delegates Districts is one of two parts in the Virginia General Assembly, the other being the Senate of Virginia. It has 100 members elected for terms of two years; unlike most states, these elections take place during odd-numbered years. State House districts are maintained within the Administration Feature and is dissolved out weekly.Administration is a polygon feature consisting of the smallest statistical areas bounded by visible features such as roads, streams, railroad tracks, and mountain ridges, as well as by nonvisible boundaries such as jurisdictional limits, school district, public safety boundaries, voting precincts, and census blocks. This methodology allows for single stream editing to move coincidental boundaries across many aggregate datasets simultaneously. Administration is maintained though an ArcGIS topology class in conjunction with County Parcels and Zoning. The topology prevents self-intersection and gaps, while ensuring complete coverage amongst the participating features.

Source: 1 foot contours were generated for each production block from the final bare earth DEMs using ArcGIS software. Using ArcGIS software, the contours were validated for correct topology, including must not intersect, must not self intersect, and must not have dangles. Contours are then manually reviewed with the 3D breaklines to ensure complete coverage, correct coding, data integrity and that contours behave correctly around water bodies, water crossings, and elevated features such as overpasses. The contours are then clipped to individual tiles as creating one dataset for the entire project renders the feature class un-usable. Enclosed contours completely within building footprints were removed from the final contour dataset.Coordinate System:The data was developed based on a horizontal datum/projection of NAD83 (2011), State Plane Connecticut, U.S. Survey Feet and vertical datum of NAVD88 (GEOID18)Use Constraints:There are no formal use restrictions. However, users should be aware the conditions may have changed since the data was originally collected, and some areas may no longer accurately reflect current surface features. This data should not be used for critical decision-making without a full understanding of their limitations.

The North American Rail Network (NARN) Rail Nodes dataset was created in 2016 and was updated on September 30, 2025 from the Federal Railroad Administration (FRA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The NARN Rail Nodes dataset is a database of North America's railway system at 1:24,000 or better within the United States. The data set covers all 50 States, the District of Columbia, Mexico, and Canada. The dataset holds topology of the network and provides geographic location information. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529070

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. ecologists used field data (plot data, observation points, photographs, and field notes) and digital aerial imagery (NAIP 2005) to map draft vegetation polygons for BEOL within an ESRI personal geodatabase. In most cases, the map units are equivalent to vegetation associations, although one is represented at the alliance level. Table relationships were used to create a drop-down list of plant associations and map unit categories in the attribute table to ensure consistent data entry. A CNHP GIS Specialist then cleaned the layer topology, removing overlaps, gaps, slivers, and any data inconsistencies. FGDC compliant metadata was created for the vegetation layers and the layers were exported from the geodatabase as ESRI shapefiles. The layers are all in the coordinate system UTM Zone 13, North American Datum 1983.