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.

A digital dataset of the geomorphology of the Lower Mississippi River Valley in Missouri, Kentucky, Arkansas, Tennessee, Louisiana, and Mississippi was developed from Roger T. Saucier’s “Geomorphology and Quaternary Geologic History of the Lower Mississippi Valley, Volumes I and II” (1994) as part of the Mississippi Alluvial Plain (MAP) Regional Water Availability Study. The maps included in the 1994 reports provide a comprehensive overview of the previously misunderstood alluvial valley geology and characterize twenty-nine Pleistocene and Holocene alluvial deposits, such as point bars, abandoned channels, backswamps, and natural levees. Each map was georeferenced to North American Datum 1983 and projected to USA Contiguous Albers Equal Conic (U.S. Geological Survey version) projection (standard parallels 29.5 and 45.5 degrees, central meridian -96 degrees, and latitude of origin 23 degrees). Once georeferenced (using ArcMap v 10.4.1), individual geomorphological features were digitized manually. Each polygon was validated using a geodatabase topology and the Topology Editor tools in ArcMap; this step was completed to create individual polygons without gaps or overlap. Efforts were made to match colors in the original map legend to the digital product, with the exception of a few features listed in the original key (for example, feature “Pve” does not match the exact color in the plates). Updated colors were selected to ease the distinction between similarly colored features. Saucier envisioned his work to be utilized by engineering geologists conducting studies that were focused at both the local and regional scale in the Lower Mississippi River Valley (Saucier, 1994). Creating a digital dataset of Saucier’s seminal geomorphological work increases the usability of the map layers for current and future scientific investigations focused on regional groundwater availability in the Mississippi Alluvial Plain. References Saucier, R.T., 1994, Geomorphology and Quaternary Geologic History of the Lower Mississippi Valley: U.S. Army Engineer Waterways Experiment Station, Vicksburg, MS, Vols. I and II, 398 p. and 28 plates

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.

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.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

Resource contains an ArcGIS file geodatabase raster for the National Vegetation Information System (NVIS) Major Vegetation Groups - Australia-wide, present extent (FGDB_NVIS4_1_AUST_MVG_EXT).

Related datasets are also included: FGDB_NVIS4_1_KEY_LAYERS_EXT - ArcGIS File Geodatabase Feature Class of the Key Datasets that make up NVIS Version 4.1 - Australia wide; and FGDB_NVIS4_1_LUT_KEY_LAYERS - Lookup table for Dataset Key Layers.

This raster dataset provides the latest summary information (November 2012) on Australia's present (extant) native vegetation. It is in Albers Equal Area projection with a 100 m x 100 m (1 Ha) cell size. A comparable Estimated Pre-1750 (pre-european, pre-clearing) raster dataset is available: - NVIS4_1_AUST_MVG_PRE_ALB. State and Territory vegetation mapping agencies supplied a new version of the National Vegetation Information System (NVIS) in 2009-2011. Some agencies did not supply new data for this version but approved re-use of Version 3.1 data. Summaries were derived from the best available data in the NVIS extant theme as at June 2012. This product is derived from a compilation of data collected at different scales on different dates by different organisations. Please refer to the separate key map showing scales of the input datasets. Gaps in the NVIS database were filled by non-NVIS data, notably parts of South Australia and small areas of New South Wales such as the Curlewis area. The data represent on-ground dates of up to 2006 in Queensland, 2001 to 2005 in South Australia (depending on the region) and 2004/5 in other jurisdictions, except NSW. NVIS data was partially updated in NSW with 2001-09 data, with extensive areas of 1997 data remaining from the earlier version of NVIS. Major Vegetation Groups were identified to summarise the type and distribution of Australia's native vegetation. The classification contains different mixes of plant species within the canopy, shrub or ground layers, but are structurally similar and are often dominated by a single genus. In a mapping sense, the groups reflect the dominant vegetation occurring in a map unit where there are a mix of several vegetation types. Subdominant vegetation groups which may also be present in the map unit are not shown. For example, the dominant vegetation in an area may be mapped as dominated by eucalypt open forest, although it contains pockets of rainforest, shrubland and grassland vegetation as subdominants. The (related) Major Vegetation Subgroups represent more detail about the understorey and floristics of the Major Vegetation Groups and are available as separate raster datasets: - NVIS4_1_AUST_MVS_EXT_ALB - NVIS4_1_AUST_MVS_PRE_ALB A number of other non-vegetation and non-native vegetation land cover types are also represented as Major Vegetation Groups. These are provided for cartographic purposes, but should not be used for analyses. For further background and other NVIS products, please see the links on http://www.environment.gov.au/erin/nvis/index.html.

The current NVIS data products are available from http://www.environment.gov.au/land/native-vegetation/national-vegetation-information-system.

Purpose

For use in Bioregional Assessment land classification analyses

Dataset History

NVIS Version 4.1

The input vegetation data were provided from over 100 individual projects representing the majority of Australia's regional vegetation mapping over the last 50 years. State and Territory custodians translated the vegetation descriptions from these datasets into a common attribute framework, the National Vegetation Information System (ESCAVI, 2003). Scales of input mapping ranged from 1:25,000 to 1:5,000,000. These were combined into an Australia-wide set of vector data. Non-terrestrial areas were mostly removed by the State and Territory custodians before supplying the data to the Environmental Resources Information Network (ERIN), Department of Sustainability Environment Water Population and Communities (DSEWPaC).

Each NVIS vegetation description was written to the NVIS XML format file by the custodian, transferred to ERIN and loaded into the NVIS database at ERIN. A considerable number of quality checks were performed automatically by this system to ensure conformity to the NVIS attribute standards (ESCAVI, 2003) and consistency between levels of the NVIS Information Hierarchy within each description. Descriptions for non-vegetation and non-native vegetation mapping codes were transferred via CSV files.

The NVIS vector (polygon) data for Australia comprised a series of jig-saw pieces, eachup to approx 500,000 polygons - the maximum tractable size for routine geoprocesssing. The spatial data was processed to conform to the NVIS spatial format (ESCAVI, 2003; other papers). Spatial processing and attribute additions were done mostly in ESRI File Geodatabases. Topology and minor geometric corrections were also performed at this stage. These datasets were then loaded into ESRI Spatial Database Engine as per the ERIN standard. NVIS attributes were then populated using Oracle database tables provided by custodians, mostly using PL/SQL Developer or in ArcGIS using the field calculator (where simple).

Each spatial dataset was joined to and checked against a lookup table for the relevant State/Territory to ensure that all mapping codes in the dominant vegetation type of each polygon (NVISDSC1) had a valid lookup description, including an allocated MVG. Minor vegetation components of each map unit (NVISDSC2-6) were not checked, but could be considered mostly complete.

Each NVIS vegetation description was allocated to a Major Vegetation Group (MVG) by manual interpretation at ERIN. The Australian Natural Resources Atlas (http://www.anra.gov.au/topics/vegetation/pubs/native_vegetation/vegfsheet.html) provides detailed descriptions of most Major Vegetation Groups. Three new MVGs were created for version 4.1 to better represent open woodland formations and forests (in the NT) with no further data available. NVIS vegetation descriptions were reallocated into these classes, if appropriate:

• Unclassified Forest

• Other Open Woodlands

• Mallee Open Woodlands and Sparse Mallee Shublands

(Thus there are a total of 33 MVGs existing as at June 2012). Data values defined as cleared or non-native by data custodians were attributed specific MVG values such as 25 - Cleared or non native, 27 - naturally bare, 28 - seas & estuaries, and 99 - Unknown.

As part of the process to fill gaps in NVIS, the descriptive data from non-NVIS sources was also referenced in the NVIS database, but with blank vegetation descriptions. In general. the gap-fill data comprised (a) fine scale (1:250K or better) State/Territory vegetation maps for which NVIS descriptions were unavailable and (b) coarse-scale (1:1M) maps from Commonwealth and other sources. MVGs were then allocated to each description from the available desciptions in accompanying publications and other sources.

Parts of New South Wales, South Australia, QLD and the ACT have extensive areas of vector "NoData", thus appearing as an inland sea. The No Data areas were dealt with differently by state. In the ACT and SA, the vector data was 'gap-filled' and attributed using satellite imagery as a guide prior to rasterising. Most of these areas comprised a mixture of MVG 24 (inland water) and 25 (cleared), and in some case 99 (Unknown). The NSW & QLD 'No Data' areas were filled using a raster mask to fill the 'holes'. These areas were attributed with MVG 24, 26 (water & unclassified veg), MVG 25 (cleared); or MVG 99 Unknown/no data, where these areas were a mixture of unknown proportions.

Each spatial dataset with joined lookup table (including MVG_NUMBER linked to NVISDSC1) was exported to a File Geodatabase as a feature class. These were reprojected into Albers Equal Area projection (Central_Meridian: 132.000000, Standard_Parallel_1: -18.000000, Standard_Parallel_2: -36.000000, Linear Unit: Meter (1.000000), Datum GDA94, other parameters 0).

Each feature class was then rasterised to a 100m raster with extents to a multiple of 1000 m, to ensure alignment. In some instances, areas of 'NoData' had to be modelled in raster. For example, in NSW where non-native areas (cleared, water bodies etc) have not been mapped. The rasters were then merged into a 'state wide' raster. State rasters were then merged into this 'Australia wide' raster dataset.

November 2012 Corrections

Closer inspection of the original 4.1 MVG Extant raster dataset highlighted some issues with the raster creation process which meant that raster pixels in some areas did not align as intended. These were corrected, and the new properly aligned rasters released in November 2012.

Dataset Citation

Department of the Environment (2012) Australia - Present Major Vegetation Groups - NVIS Version 4.1 (Albers 100m analysis product). Bioregional Assessment Source Dataset. Viewed 10 July 2017, http://data.bioregionalassessments.gov.au/dataset/57c8ee5c-43e5-4e9c-9e41-fd5012536374.

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.

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.
A spatial representation of simultaneous conveyances (subdivisions and condominiums). This polygon feature class is maintained in an enterprise geodatabase using topology with other LandManagement feature classes. The key attributes include the name of the subdivision or condominium (Name) and the Oakland County Condominium Plan (OCCP) number, if present.

For the purpose of this document, simultaneous conveyances are subdivisions and condominiums. "A simultaneously created boundary results when several parcels of land are created in the same legal instant by the same person, persons, or agency and by the same instrument" (Brown, 1995, page 295). This polygon feature class represents the extent of the simultaneous conveyances as of the most recent recording.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

The Geological Survey of Queensland (GSQ) has released this Queensland Geology Digital Data update to replace the previous 2008 Geoldata release. Spatial and Graphic Services within GSQ have undertaken a major redevelopment to migrate existing data to an Enterprise Geodatabase. Our ArcInfo workstation platform has been retired. This has allowed us to utilise the inherent data validation, integrity checking and relationship features of the geodatabase to provide improved data quality.

As this is a major milestone, as well as making the data available on this DVD, we are incorporating the Detailed, Regional and Queensland Geology polygonised vector data into the Interactive Resource and Tenure Maps (IRTM) system for display, query and download of ESRI shape files.

Along with new project work, GSQ will continue a maintenance program of the enterprise Geodatabase to edge-match, correct topology and complete a State-wide polygonised vector best scale dataset. It is proposed that data releases will become more frequent. When changes are considered substantial by the Geoscience Manager, digital data will be extracted and a new Geoldata DVD released.

This DVD data was extracted from the feature datasets in the GSQ Geology Enterprise Geodatabase in early November 2011.

This edition provides new and updated geology over the North-West Queensland Mineral and Energy Province, Hodgkinson Province, South-East Queensland, North Connors Province and Drummond Basin. Seamless data is provided within each of these areas and topological errors have been corrected for NWQMEP and Drummond Basin, while validation in other areas is ongoing and will be available in future releases. For the NWQMEP, Georgetown and Charters Towers GIS areas solid geology interpretation has been completed and is provided as an additional dataset.

This edition also includes the August 2012 release of the new Queensland Structural Framework and Queensland Geology.

Dataset History

GEOLDATA for detailed geology was in many cases previously compiled from field mapping over 1:100 000 map extents. These were completed by different geologists sometimes over many field seasons, with different interpretations. The DVD 1 detailed geology dataset has been extracted from the Geodatabase using a GDA94 standard 1:250 000 map tile extent. The DVD 2 detailed geology dataset has been provided as a statewide extract. Edge matching between the 100K tile edges within this 250K extent may still be in progress. The geological data will be seamless where the field mapping was completed for a specific project extent e.g. Yarrol Province.

The original data capture over most of the 100K tile extents, was compiled based on the Australian Geodetic Datum 1966. This data was projected to GDA94 for inclusion in the geodatabase.

The data required to be captured for a specific 100K tile based on AGD66, will not be exactly the same as that needed to cover a 100K tile extent based on GDA94. Currently, there may still exist in a few situations, a 'gap' in geological information between adjoining sheets at the outer edges of project areas. These 'gaps' may occur where older project areas were field mapped and captured for ADG66 map production, and they abut more recent project areas which were field mapped and captured for GDA94 map production. Edge mapping adjustments are to be made.

Similarly GEOLDATA for regional datasets were previously compiled from 1:500 000 or 1:1000 000 hard copy maps which were based on the Australian Geodetic Datum 1966 and so their map boundary latitude and longitudes were derived from that AGD66 Datum.

The digital data captured from these maps was projected to GDA94 for migration to the Geodatabase, and so the GDA94 lat/long extents of the datasets will not coincide with the same lat and long values of the original AGD66 drawn map graticule.

Data matching between Regional Datasets will seldom occur.

Dataset Citation

Geological Survey of Queensland (2012) QLD Geological Digital Data - QLD Geology, Structural Framework, November 2012. Bioregional Assessment Source Dataset. Viewed 10 December 2018, http://data.bioregionalassessments.gov.au/dataset/a841bdfd-376c-4c7b-afd4-e92aba991f06.

The region is the top tier of local government in New Zealand. There are 16 regions of New Zealand (Part 1 of Schedule 2 of the Local Government Act 2002). Eleven are governed by an elected regional council, while five are governed by territorial authorities (the second tier of local government) who also perform the functions of a regional council and thus are known as unitary authorities. These unitary authorities are Auckland Council, Nelson City Council, Gisborne, Tasman, and Marlborough District Councils. The Chatham Islands Council also perform some of the functions of a regional council, but is not strictly a unitary authority. Unitary authorities act as regional councils for the purposes of a wide range of Acts and regulations. Regional council areas are based on water catchment areas. Regional councils are responsible for the administration of many environmental and public transport matters.Regional Councils were established in 1989 after the abolition of the 22 local government regions. The local government act 2002, requires the boundaries of regions to confirm as far as possible to one or more water catchments. When determining regional boundaries, the local Government commission gave consideration to regional communities of interest when selecting water catchments to included in a region. It also considered factors such as natural resource management, land use planning and environmental matters. Some regional boundaries are conterminous with territorial authority boundaries but there are many exceptions. An example is Taupo District, which is split between four regions, although most of its area falls within the Waikato Region. Where territorial local authorities straddle regional council boundaries, the affected area have been statistically defined in complete area units. Generally regional councils contain complete territorial authorities. The unitary authority of the Auckland Council was formed in 2010, under the Local Government (Tamaki Makarau Reorganisation) Act 2009, replacing the Auckland Regional Council and seven territorial authorities.The seaward boundary of any costal regional council is the twelve mile New Zealand territorial limit. Regional councils are defined at meshblock and area unit level.Regional Councils included in the 2013 digital pattern are:Regional Council CodeRegional Council Name01Northland Region02Auckland Region03Waikato Region04Bay of Plenty Region05Gisborne Region06Hawke's Bay Region07Taranaki Region08Manawatu-Wanganui Region09Wellington Region12West Coast Region13Canterbury Region14Otago Region15Southland Region16Tasman Region17Nelson Region18Marlborough Region99Area Outside RegionAs at 1stJuly 2007, Digital Boundary data became freely available.Deriving of Output FilesThe original vertices delineating the meshblock boundary pattern were digitised in 1991 from 1:5,000 scale urban maps and 1:50,000 scale rural maps. The magnitude of error of the original digital points would have been in the range of +/- 10 metres in urban areas and +/- 25 metres in rural areas. Where meshblock boundaries coincide with cadastral boundaries the magnitude of error will be within the range of 1–5 metres in urban areas and 5 - 20 metres in rural areas. This being the estimated magnitude of error of Landonline.The creation of high definition and generalised meshblock boundaries for the 2013 digital pattern and the dissolving of these meshblocks into other geographies/boundaries were completed within Statistics New Zealand using ESRI's ArcGIS desktop suite and the Data Interoperability extension with the following process: 1. Import data and all attribute fields into an ESRI File Geodatabase from LINZ as a shapefile2. Run geometry checks and repairs.3. Run Topology Checks on all data (Must Not Have Gaps, Must Not Overlap), detailed below.4. Generalise the meshblock layers to a 1m tolerance to create generalised dataset. 5. Clip the high definition and generalised meshblock layers to the coastline using land water codes.6. Dissolve all four meshblock datasets (clipped and unclipped, for both generalised and high definition versions) to higher geographies to create the following output data layers: Area Unit, Territorial Authorities, Regional Council, Urban Areas, Community Boards, Territorial Authority Subdivisions, Wards Constituencies and Maori Constituencies for the four datasets. 7. Complete a frequency analysis to determine that each code only has a single record.8. Re-run topology checks for overlaps and gaps.9. Export all created datasets into MapInfo and Shapefile format using the Data Interoperability extension to create 3 output formats for each file. 10. Quality Assurance and rechecking of delivery files.The High Definition version is similar to how the layer exists in Landonline with a couple of changes to fix topology errors identified in topology checking. The following quality checks and steps were applied to the meshblock pattern:Translation of ESRI Shapefiles to ESRI geodatabase datasetThe meshblock dataset was imported into the ESRI File Geodatabase format, required to run the ESRI topology checks. Topology rules were set for each of the layers. Topology ChecksA tolerance of 0.1 cm was applied to the data, which meant that the topology engine validating the data saw any vertex closer than this distance as the same location. A default topology rule of “Must Be Larger than Cluster Tolerance” is applied to all data – this would highlight where any features with a width less than 0.1cm exist. No errors were found for this rule.Three additional topology rules were applied specifically within each of the layers in the ESRI geodatabase – namely “Must Not Overlap”, “Must Not Have Gaps” and “"Area Boundary Must Be Covered By Boundary Of (Meshblock)”. These check that a layer forms a continuous coverage over a surface, that any given point on that surface is only assigned to a single category, and that the dissolved boundaries are identical to the parent meshblock boundaries.Topology Checks Results: There were no errors in either the gap or overlap checks.GeneralisingTo create the generalised Meshblock layer the “Simplify Polygon” geoprocessing tool was used in ArcGIS, with the following parameters:Simplification Algorithm: POINT_REMOVEMaximum Allowable Offset: 1 metreMinimum Area: 1 square metreHandling Topological Errors: RESOLVE_ERRORSClipping of Layers to CoastlineThe processed feature class was then clipped to the coastline. The coastline was defined as features within the supplied Land2013 with codes and descriptions as follows:11- Island – Included12- Mainland – Included21- Inland Water – Included22- Inlet – Excluded23- Oceanic –Excluded33- Other – Included.Features were clipped using the Data Interoperability extension, attribute filter tool. The attribute filter was used on both the generalised and high definition meshblock datasets creating four meshblock layers. Each meshblock dataset also contained all higher geographies and land-water data as attributes. Note: Meshblock 0017001 which is classified as island, was excluded from the clipped meshblock layers, as most of this meshblock is oceanic. Dissolve meshblocks to higher geographiesStatistics New Zealand then dissolved the ESRI meshblock feature classes to the higher geographies, for both the full and clipped dataset, generalised and high definition datasets. To dissolve the higher geographies, a model was built using the dissolver, aggregator and sorter tools, with each output set to include geography code and names within the Data Interoperability extension. Export to MapInfo Format and ShapfilesThe data was exported to MapInfo and Shapefile format using ESRI's Data Interoperability extension Translation tool. Quality Assurance and rechecking of delivery filesThe feature counts of all files were checked to ensure all layers had the correct number of features. This included checking that all multipart features had translated correctly in the new file.

The Churchill Structural Province map (GSC Open File 5744) is one of the datasets used to produce the NWT geological bedrock compilation. This dataset represents the compilation of existing geological maps. The data were originally compiled in shapefile format and can be output for public distribution in shapefile or PDF format. This map has been modified, and converted into a geodatabase, from the original GSC Open File 5744 to fit adjacent provinces, fix topology errors and standardize attributes. GSC Open File 5744 contains information on data sources related to this dataset and additional geological interpretation.

The protected and recreational open space datalayer contains the boundaries of conservation lands and outdoor recreational facilities in Massachusetts. The associated database contains relevant information about each parcel, including ownership, level of protection, public accessibility, assessor’s map and lot numbers, and related legal interests held on the land, including conservation restrictions. Conservation and outdoor recreational facilities owned by federal, state, county, municipal, and nonprofit enterprises are included in this datalayer. Not all lands in this layer are protected in perpetuity, though nearly all have at least some level of protection.Although the initial data collection effort for this data layer has been completed, open space changes continually and this data layer is therefore considered to be under development. Additionally, due to the collaborative nature of this data collection effort, the accuracy and completeness of open space data varies across the state’s municipalities. Attributes, while comprehensive in scope, may be incomplete for many parcels.The OpenSpace layer includes two feature classes:OPENSPACE_POLY - polygons of recreational and conservation lands as described aboveOPENSPACE_ARC - attributed lines that represent boundaries of the polygonsThese feature classes are stored in an ArcSDE feature dataset named OPENSPACE that includes ArcGIS geodatabase topology. OPENSPACE_POLY - The following types of land are included in this 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 resourceforest land -- if designated as a Forest Legacy Area

Analysis of ‘OC Simultaneous Conveyance’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/4893b55d-f6df-4f80-bdf8-8a505511319e on 26 January 2022.

--- Dataset description provided by original source is as follows ---

BY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.
A spatial representation of simultaneous conveyances (subdivisions and condominiums). This polygon feature class is maintained in an enterprise geodatabase using topology with other LandManagement feature classes. The key attributes include the name of the subdivision or condominium (Name) and the Oakland County Condominium Plan (OCCP) number, if present.

For the purpose of this document, simultaneous conveyances are subdivisions and condominiums. "A simultaneously created boundary results when several parcels of land are created in the same legal instant by the same person, persons, or agency and by the same instrument" (Brown, 1995, page 295). This polygon feature class represents the extent of the simultaneous conveyances as of the most recent recording.

--- Original source retains full ownership of the source dataset ---

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 vegetation mapping and characterization process began with the delineation of draft polygons from remote sensing imagery. Field crews then visited each polygon to collect qualitative vegetation cover data and further refine polygon boundaries. Concurrently, vegetation data were collected at both randomly and subjectively placed plots. At the end of each field day, crews transferred all edits made to field maps to a set of “master” paper maps that did not go into the field. Each polygon was then edited in ArcMap to reflect any boundary changes collected in the field on paper maps, and each polygon feature was attributed to reflect any changes in polygon identification numbers and tentative association names. The datasets are housed in a file geodatabase structure (.gdb), enabling the establishment of topology rules and relationships. Strict nomenclature was enforced for polygons, such that unique names were assigned to each polygon; these reflected the verified physiognomic formation type with a prefix of representative letters (W = Woodland, SS = shrub savanna, etc.) followed by a number.

Abstract

This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.

This raster dataset 'NVIS4_1_AUST_MVS_PRE_ALB' provides summary information on Australia's estimated pre-1750 native vegetation classified into Major Vegetation Subgroups. It is in Albers Equal Area projection with a 100 m x 100 m (1 Ha) cell size.

A comparable Extant (present) vegetation raster dataset is available:

• NVIS4_1_AUST_MVS_EXT_ALB.

State and Territory vegetation mapping agencies supplied a new version of the National Vegetation Information System (NVIS) in 2009-2011. Some agencies did not supply new data for this version but approved re-use of Version 3.1 data. Summaries were derived from the best available data in the NVIS extant theme as at June 2012.

This product is derived from a compilation of data collected at different scales on different dates by different organisations. Please refer to the separate key map showing scales of the input datasets. Gaps in the NVIS database were filled by non-NVIS data, notably parts of South Australia and small areas of New South Wales such as the Curlewis area.

Eighty-five (85) Major Vegetation Subgroups identified were created in v4.1 to summarise the type and distribution of Australia's native vegetation. The classification contains an emphasis on the structural and floristic composition of the dominant stratum (as with Major Vegetation Groups), but with additional types identified according to typical shrub or ground layers occurring with a dominant tree or shrub stratum.

In a mapping sense, the subgroups reflect the dominant vegetation occurring in a map unit from a mix of several vegetation types. Less-dominant vegetation subgroups which are also present in the map unit are not shown. For example, the dominant vegetation in an area may be mapped as dominated by eucalypt open forest with a shrubby understorey, although it contains pockets of rainforest, shrubland and grassland vegetation as subdominants.

A number of other non-vegetation and non-native vegetation land cover types are also represented as Major Vegetation Subgroups. These are provided for cartographic purposes, but should not be used for analyses.

This dataset has been provided to the BA Programme for use within the programme only. The current NVIS data products are available from http://www.environment.gov.au/land/native-vegetation/national-vegetation-information-system.

Dataset History

The input vegetation data were provided from over 100 individual projects representing the majority of Australia's regional vegetation mapping over the last 50 years. State and Territory custodians translated the vegetation descriptions from these datasets into a common attribute framework, the National Vegetation Information System (ESCAVI, 2003). Scales of input mapping ranged from 1:25,000 to 1:5,000,000. These were combined into an Australia-wide set of vector data. Non-terrestrial areas were mostly removed by the State and Territory custodians before supplying the data to the Environmental Resources Information Network (ERIN), Department of Sustainability Environment Water Population and Communities (DSEWPaC).

Each NVIS vegetation description was written to the NVIS XML format file by the custodian, transferred to ERIN and loaded into the NVIS database at ERIN. A considerable number of quality checks were performed automatically by this system to ensure conformity to the NVIS attribute standards (ESCAVI, 2003) and consistency between levels of the NVIS Information Hierarchy within each description. Descriptions for non-vegetation and non-native vegetation mapping codes were transferred via CSV files.

The NVIS vector (polygon) data for Australia comprised a series of jig-saw pieces, each up to approx 500,000 polygons - the maximum tractable size for routine geoprocesssing. The spatial data was processed to conform to the NVIS spatial format (ESCAVI, 2003; other papers). Spatial processing and attribute additions were done mostly in ESRI File Geodatabases. Topology and minor geometric corrections were also performed at this stage. These datasets were then loaded into ESRI Spatial Database Engine as per the ERIN standard. NVIS attributes were then populated using database tables provided by custodians, mostly using PL/SQL Developer or in ArcGIS using the field calculator (where simple).

Each spatial dataset was joined to and checked against a lookup table for the relevant State/Territory to ensure that all mapping codes in the dominant vegetation type of each polygon (NVISDSC1) had a valid lookup description, including an allocated MVS. Minor vegetation components of each map unit (NVISDSC2-6) were not checked, but could be considered mostly complete.

Each NVIS vegetation description was allocated to a Major Vegetation Subgroup (MVS) by manual interpretation at ERIN and in consultation with data custodians. 12 new MVSs were created for version 4.1 to better represent open woodland formations, more understorey types and forests (in the NT) with no further data available. Also, a number of MVSs were redefined after creation of the new groups to give a clearer and precise description of of the Subgroup e.g. MVS 9 - 'Eucalyptus woodlands with a grassy understorey' became 'Eucalyptus woodlands with a tussock grass understorey' to distinguish it from MVS10 - 'Eucalyptus woodlands with a hummock grass understorey'.. NVIS vegetation descriptions were reallocated into these classes, if appropriate:

• Warm Temperate Rainforest

• Eucalyptus woodlands with a hummock grass understorey

• Acacia (+/- low) open woodlands and sparse shrublands with a shrubby understorey

• Mulga (Acacia aneura) open woodlands and sparse shrublands +/- tussock grass

• Eucalyptus woodlands with a chenopod or samphire understorey

• Open mallee woodlands and sparse mallee shrublands with a hummock grass understorey

• Open mallee woodlands and sparse mallee shrublands with a tussock grass understorey

• Open mallee woodlands and sparse mallee shrublands with an open shrubby understorey

• Open mallee woodlands and sparse mallee shrublands with a dense shrubby understorey

• Callitris open woodlands

• Casuarina and Allocasuarina open woodlands with a tussock grass understorey

• Casuarina and Allocasuarina open woodlands with a hummock grass understorey

• Casuarina and Allocasuarina open woodlands with a chenopod shrub understorey

• Casuarina and Allocasuarina open woodlands with a shrubby understorey

• Melaleuca open woodlands

• Other Open Woodlands

• Other sparse shrublands and sparse heathlands

• Unclassified Forest

Data values defined as cleared or non-native by data custodians were attributed specific MVS values such as 42 - naturally bare, sand, rock, claypan, mudflat; 43 - salt lakes and lagoons; 44 - freshwater lakes and dams; 46 - seas & estuaries, 90, 91, 92 & 93 - Regrowth Subgroups; 98 - Cleared, non native, buildings; and 99 - Unknown. Note: some of these MVSs are only present in Extant vegetation.

As part of the process to fill gaps in NVIS, the descriptive data from non-NVIS sources was also stored in the NVIS database, but with blank vegetation descriptions. In general, the gap-fill data comprised (a) fine scale (1:250K or better) State/Territory vegetation maps for which NVIS descriptions were unavailable and (b) coarse-scale (1:1M and 1:5M) maps from Commonwealth and other sources. MVSs were then allocated to each description from the available descriptions in accompanying publications and other sources.

Each spatial dataset with joined lookup table (including MVS_NUMBER linked via NVISDSC1) was exported to a File Geodatabase as a feature class. These were reprojected into Albers Equal Area projection (Central_Meridian: 132.000000, Standard_Parallel_1: -18.000000, Standard_Parallel_2: -36.000000, Linear Unit: Meter (1.000000), Datum GDA94, other parameters 0).

In the original extant data, parts of New South Wales, South Australia, Tasmania and the ACT have areas of vector "NoData", thus appearing as an inland sea. Where there were gaps in the spatial coverage of Australia, "artificial" estimated pre-1750 layers were created from datasets available to the ERIN Veg Team. These were managed differently based on available information and complexity of work involved. Pre-1750 vector data for other states were supplied for 4.1 or previously, and did not require modelling. The purpose of this artificial pre-1750 modelling was to ensure that the pre-1750 and extant (present) datasets are comparable in the respective MVG and MVS classifications.

Pre1750 Vector Modelling

Large areas in the original South Australia and the ACT extant vector data had 'NoData'. Pre1750 vector layers were created by filling/cutting in these areas with estimated pre-1750 data from other sources such as the Geoscience Australia (AUSLIG,1990) "Natural" vector data layer. This procedure assumes that extant native vegetation has not changed its type since European settlement. Thus, effectively, only the non-native component was modelled/estimated for pre-1750 extent.

All feature classes were then rasterised to a 100m raster with extents to a multiple of 1000 m, to ensure alignment. In some instances e.g. NSW and TAS, areas of 'NoData' had to be modelled in raster (see below).

Raster modelling

For large parts of NSW, the native component of NVIS extant data were cut into the Geoscience Australia (AUSLIG,1990) "Natural" raster data layer and in some smaller areas, existing pre1750 data layers (e.g. Tumut), using a complex series of raster operations. For Tasmania, the NVIS version 2.0 (i.e. the original NVIS with restructured attributes) pre-European layer was rasterised, and used to fill non-native areas of the extant NVIS vegetation

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 includes one file for each of the 51 counties that were collected, as well as a CA_Merged file with the parcels merged into a single file.Note – this data does not include attributes beyond the parcel ID number (PARNO) – that will be provided when available, most likely by the state of California.DownloadA 1.6 GB zipped file geodatabase is available for download - click here.DescriptionA geodatabase with parcel boundaries for 51 (out of 58) counties in the State of California. The original target was to collect data for the close of the 2013 fiscal year. As the collection progressed, it became clear that holding to that time standard was not practical. Out of expediency, the date requirement was relaxed, and the currently available dataset was collected for a majority of the counties. Most of these were distributed with minimal metadata.The table “ParcelInfo” includes the data that the data came into our possession, and our best estimate of the last time the parcel dataset was updated by the original source. Data sets listed as “Downloaded from” were downloaded from a publicly accessible web or FTP site from the county. Other data sets were provided directly to us by the county, though many of them may also be available for direct download. Â These data have been reprojected to California Albers NAD84, but have not been checked for topology, or aligned to county boundaries in any way. Tulare County’s dataset arrived with an undefined projection and was identified as being California State Plane NAD83 (US Feet) and was assigned by ICE as that projection prior to reprojection. Kings County’s dataset was delivered as individual shapefiles for each of the 50 assessor’s books maintained at the county. These were merged to a single feature class prior to importing to the database.The attribute tables were standardized and truncated to include only a PARNO (APN). The format of these fields has been left identical to the original dataset. The Data Interoperablity Extension ETL tool used in this process is included in the zip file. Where provided by the original data sources, metadata for the original data has been maintained. Please note that the attribute table structure changes were made at ICE, UC Davis, not at the original data sources.Parcel Source InformationCountyDateCollecDateCurrenNotesAlameda4/8/20142/13/2014Download from Alamenda CountyAlpine4/22/20141/26/2012Alpine County PlanningAmador5/21/20145/14/2014Amador County Transportation CommissionButte2/24/20141/6/2014Butte County Association of GovernmentsCalaveras5/13/2014Download from Calaveras County, exact date unknown, labelled 2013Contra Costa4/4/20144/4/2014Contra Costa Assessor’s OfficeDel Norte5/13/20145/8/2014Download from Del Norte CountyEl Dorado4/4/20144/3/2014El Dorado County AssessorFresno4/4/20144/4/2014Fresno County AssessorGlenn4/4/201410/13/2013Glenn County Public WorksHumboldt6/3/20144/25/2014Humbodt County AssessorImperial8/4/20147/18/2014Imperial County AssessorKern3/26/20143/16/2014Kern County AssessorKings4/21/20144/14/2014Kings CountyLake7/15/20147/19/2013Lake CountyLassen7/24/20147/24/2014Lassen CountyLos Angeles10/22/201410/9/2014Los Angeles CountyMadera7/28/2014Madera County, Date Current unclear likely 7/2014Marin5/13/20145/1/2014Marin County AssessorMendocino4/21/20143/27/2014Mendocino CountyMerced7/15/20141/16/2014Merced CountyMono4/7/20144/7/2014Mono CountyMonterey5/13/201410/31/2013Download from Monterey CountyNapa4/22/20144/22/2014Napa CountyNevada10/29/201410/26/2014Download from Nevada CountyOrange3/18/20143/18/2014Download from Orange CountyPlacer7/2/20147/2/2014Placer CountyRiverside3/17/20141/6/2014Download from Riverside CountySacramento4/2/20143/12/2014Sacramento CountySan Benito5/12/20144/30/2014San Benito CountySan Bernardino2/12/20142/12/2014Download from San Bernardino CountySan Diego4/18/20144/18/2014San Diego CountySan Francisco5/23/20145/23/2014Download from San Francisco CountySan Joaquin10/13/20147/1/2013San Joaquin County Fiscal year close dataSan Mateo2/12/20142/12/2014San Mateo CountySanta Barbara4/22/20149/17/2013Santa Barbara CountySanta Clara9/5/20143/24/2014Santa Clara County, Required a PRA requestSanta Cruz2/13/201411/13/2014Download from Santa Cruz CountyShasta4/23/20141/6/2014Download from Shasta CountySierra7/15/20141/20/2014Sierra CountySolano4/24/2014Download from Solano Couty, Boundaries appear to be from 2013Sonoma5/19/20144/3/2014Download from Sonoma CountyStanislaus4/23/20141/22/2014Download from Stanislaus CountySutter11/5/201410/14/2014Download from Sutter CountyTehama1/16/201512/9/2014Tehama CountyTrinity12/8/20141/20/2010Download from Trinity County, Note age of data 2010Tulare7/1/20146/24/2014Tulare CountyTuolumne5/13/201410/9/2013Download from Tuolumne CountyVentura11/4/20146/18/2014Download from Ventura CountyYolo11/4/20149/10/2014Download from Yolo CountyYuba11/12/201412/17/2013Download from Yuba County

These attributes are based on the NHDPlusV2 network geometry and modifications retrieved from the National Water Model V2.1 (NWMv2.1) and "E2NHDPlusV2_us: Database of Ancillary Hydrologic Attributes and Modified Routing for NHDPlus Version 2.1 Flowlines" (E2NHDPlusV2) datasets. The attributes included are: comid, tocomid, ftype, fcode, gnis_name, gnis_id, fromnode, tonode, divergence, streamleve, streamorde, streamcalc, reachcode, frommeas, tomeas, lengthkm, arbolatesu, pathlength, areasqkm, totdasqkm, hwnodesqkm, hydroseq, dnhydroseq, levelpathi, terminalpa, dnlevelpat, terminalfl, terminalfl, wbareatype, wbareacomi, slope, slopelenkm, roughness, vpuin, vpuout, rpuid, vpuid. These attributes are available in four formats: csv, fst, parquet, and geopackage. "fst" is a high-performance format for use with the R programming language "fst" package. "parquet" is a high-performance format for use with multiple programming languages (including python) that support the Apache Arrow Parquet format. Geopackage is an open standard geodatabase format and includes both the attributes and geometry included in this data release. The comid field of these data can be used to join to the National Hydrography Dataset Plus V2.1 (NHDPlusV2) flowline comid or catchment featureid attributes. The included attributes follow the same data model as the NHDPlusV2 but include numerous updates and improvements to network connectivity. All attributes that depend on network connectivity have been recalculated. Version 3.0 includes updated flowline geometry in a geopackage geodatabase file with node geometry digitized in agreement with the network topology and all derived attributes compatible with non-dendritic network assumptions. Version 3.0 also now includes specific records of edits applied to the NHDPlusV2 from the NWMV2.1 and E2NHDPlusV2 in seperate geopackage geodatabases. See the entity and attributes section of this metadata record for more information.

The protected and recreational open space datalayer contains the boundaries of conservation lands and outdoor recreational facilities in Massachusetts. The associated database contains relevant information about each parcel, including ownership, level of protection, public accessibility, assessor’s map and lot numbers, and related legal interests held on the land, including conservation restrictions. Conservation and outdoor recreational facilities owned by federal, state, county, municipal, and nonprofit enterprises are included in this datalayer. Not all lands in this layer are protected in perpetuity, though nearly all have at least some level of protection.Although the initial data collection effort for this data layer has been completed, open space changes continually and this data layer is therefore considered to be under development. Additionally, due to the collaborative nature of this data collection effort, the accuracy and completeness of open space data varies across the state’s municipalities. Attributes, while comprehensive in scope, may be incomplete for many parcels.The OpenSpace layer includes two feature classes:OPENSPACE_POLY - polygons of recreational and conservation lands as described aboveOPENSPACE_ARC - attributed lines that represent boundaries of the polygonsThese feature classes are stored in an ArcSDE feature dataset named OPENSPACE that includes ArcGIS geodatabase topology. OPENSPACE_POLY - The following types of land are included in this 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 resourceforest land -- if designated as a Forest Legacy AreaOPENSPACE ARC- This datalayer includes all arcs that bound openspace polygons. These arcs are coded as being coincident with other map features (town boundary, stream, etc.).

This dataset was created to provide vector mapping of planimetric features derived from aerial photography.Photo Acquisition - The aerial photographic mission was carried out on April 12, 2017. 459 exposures were taken in 16 flight lines at 3300' AMT resulting in a pixel resolution of 0.22' . The photography was collected with 60% overlap to ensure proper stereo viewingAerial Triangulation - The digital photographs were triangulated using KLT software. The interior orientations of each photo were measured, the photos were tied togther within flight lines and lastly each flight line was tied, creating one single unified block. This block was then projected into Massachusetts State Plane NAD 83 coordinates using the14 aerial photo ground control points that were collected by traditional survey. RMS formulas were used to compute error propagation and reduce error.Data Capture - Vector data was collected using the subsequent aerial triangulation which allows photogrammetrists to view the photography in stereo. Data was captured using KLT sofware which allows the user to collect in 3D space in the coordinate system established during aerial triangulation. Each data set was collected on its own layer, which allows the data to be imported into the GIS database. The data was collected at scale of 1"= 40'CAD processing - The vector data collected through the stereocompilation process is edited in KLT Atlas software. Data is checked for errors and then converted into AutoCAD .dxf format.GIS geodatabase production- The AutoCAD .dxf file is imported into ESRI ArcGIS 10.5.1 where a topology is run to eliminate any gaps that may exist in the data. The data is then separated into the appropriate layers as defined in the database design. A topology check is then run on the data prior to delivery to check for inconsistencies.

This dataset was created to provide vector mapping of planimetric features derived from aerial photography.Photo Acquisition - The aerial photographic mission was carried out on April 12, 2017. 459 exposures were taken in 16 flight lines at 3300' AMT resulting in a pixel resolution of 0.22' . The photography was collected with 60% overlap to ensure proper stereo viewingAerial Triangulation - The digital photographs were triangulated using KLT software. The interior orientations of each photo were measured, the photos were tied togther within flight lines and lastly each flight line was tied, creating one single unified block. This block was then projected into Massachusetts State Plane NAD 83 coordinates using the14 aerial photo ground control points that were collected by traditional survey. RMS formulas were used to compute error propagation and reduce error.Data Capture - Vector data was collected using the subsequent aerial triangulation which allows photogrammetrists to view the photography in stereo. Data was captured using KLT sofware which allows the user to collect in 3D space in the coordinate system established during aerial triangulation. Each data set was collected on its own layer, which allows the data to be imported into the GIS database. The data was collected at scale of 1"= 40'CAD processing - The vector data collected through the stereocompilation process is edited in KLT Atlas software. Data is checked for errors and then converted into AutoCAD .dxf format.GIS geodatabase production- The AutoCAD .dxf file is imported into ESRI ArcGIS 10.5.1 where a topology is run to eliminate any gaps that may exist in the data. The data is then separated into the appropriate layers as defined in the database design. A topology check is then run on the data prior to delivery to check for inconsistencies.