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.

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.

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.

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 dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows:

This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application.

The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale.

In the ESRI version, a layer file is provided which presents the units in the colours and patterns used on the printed hard copy map. For Map Info users, a simplified colour palette is provided without patterns. However a georeferenced image of the hard copy map is included and can be displayed as a background in both Arc Map and Map Info.

The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics).

For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info.

Dataset History

Details on the source data can be found in the xml file associated with data layer.

Data in this release

*ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology

*ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework

*ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology

*Georeferenced Queensland geology map, gravity and magnetic images

*Queensland geology map, structural framework and schematic diagram PDF files

*Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94

Accessing the data

Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites").

Metadata

Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders.

Disclaimer

The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites.

Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination.

The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason.

The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way.

WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties.

Please view the 'readme.html' and 'licence.html' file for further, more complete information

Dataset Citation

Geological Survey of Queensland (2012) Queensland geology and structural framework - GIS data July 2012. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/69da6301-04c1-4993-93c1-4673f3e22762.

This dataset is a combination of 2 data projects: 1- Data were updated within NYC watershed portions using 1m resolution LiDAR and 1ft orthoimagery collected in 2009 as part of the NYS Digital Ortho Program under contract with NYCDEP under CAT-371.For NYC reservoir areas only: NYCDEP BWS GIS Staff (T. Spies) edited all artificial path and stream transitions to snap exactly to polygon edges representing NYC reservoirs, where those areas were updated by NYCDEP for correct inundation area based on spillway elevation.QA edits to NHD hydrography, including this feature class, were also made where needed based on field verification and correction of the NYCbasin1m boundary.As an additional departure from standard NHD to meet DEP’s needs, DEP GIS staff attributed all flowlines by their respective NYC reservoir basin and NYC water supply “region” as defined in the feature class “NYCbasin1m”. This was done using the “select by location” tool rather than “identity” tool, so as not to split any flowlines across boundaries. Any flowlines crossing basin boundaries in error were corrected by splitting the lines and snapping their endpoints to the appropriate spillway or basin edge instead. After these edits were made, a new geometric network was built to test and ensure all flowlines in the entire dataset were correctly connected so that they can be used for routing.2- Data was updated within portions of Ulster County outside the NYC watershed using NYS 1ft orthoimagery collected in 2013 and multiple Elevation datasets (2013 NYS DEC 1m Lidar Hudson River, 2005 NYS DEC 3m Lidar Ulster Stream Corridors, 1992 USGS 10m Digital Elevation Model (DEM)).Primary quality control was performed visually using enhanced symbology and supporting reference data. A detailed QC checklist is provided in the QC report. Specific emphasis was placed on the areas bordering the NYC Watershed and the areas encompassed by the Town of Woodstock’s local hydrography data. To the extent connections occurred, the data captured on this project was “snapped” to the corresponding locations in the NYC Watershed so that the data could be seamlessly integrated. The hydrography data from the Town of Woodstock, however, was inconsistent when applied to the data capture protocol. Many locally derived features did not appear to be supported by the source data (i.e., they did not exist) and were not included. All visual inspections were made at 1:1000 scale or better. During data capture, the Data Capture Analyst used a separate point feature class named “Flags” to identify locations where there may have been some interpretation or confusion. Later, the QC Analyst also used additional bookmarks in ArcGIS to track locations where additional investigation or interpretation was required. Finally, after an initial pass through the data, the QC Analyst evaluated and resolved all such flags and bookmarks, collaborating with the Data Capture Analyst as necessary to discuss findings and resolve questions.As data was completed, naming convention and separate storage locations were used for data management to ensure that source and modified datasets were clearly separated. In addition, a detailed QC tracking spreadsheet was used to track and manage effort on completing QC and resolving any issues.Finally, after the initial data delivery, several rounds of QC review were performed by Ulster County to include: additional visual inspection of flow line connectivity, geometric network tracking, and utility network analysisMost of the issues that were not readily apparent in the manual QC process were attributed to minor errors in data capture and discovered here. Examples include digitizing lines in the wrong direction (not downstream), existence of multi-part features, and topology errors. In all cases, issues were evaluated and resolved

This dataset contains point features representing the approximate location of tax parcels contained in County Assessor tax rolls. Individual county data was integrated into this statewide publication by the Arkansas Geographic Information Office (AGIO). The Computer Aided Mass Appraisal (CAMA) systems maintained in each county are used to populate the database attributes for each centroid feature. The entity attribute structure conforms to the Arkansas Cadastral Mapping Standard. The digital cadastral data is provided as a publication version that only represents a snapshot of the production data at the time it was received from the county. Published updates may be made to counties throughout the year. These will occur after new data is digitized or updates to existing data are finished. Production versions of the data exist in the various counties where daily and weekly updates occur. Users should consult the BEGIN_DATE attribute column to determine the age of the data for a given county. This column reflects the date when AGIO received the data from the county. Only parcels with an associated Computer Assisted Mass Appraisal (CAMA) record are provided. This means a CAMA record may exist, but no point geometry or vice-versa. Cadastral data is dynamic by its nature; therefore it is impossible for any county to ever be considered complete. The data is NOT topologically enforced. As a statewide integrator, AGIO publishes the data but does not make judgment calls about where points or polygon lines are meant to be located. Therefore each county data set is published without topology rules being enforced. GIS Technicians use best practices such as polygon closure and vertex snapping, however, topology is not built for each county. Users should be aware, by Arkansas Law (15-21-504 2 B) digital cadastral data does not represent legal property boundary descriptions, nor is it suitable for boundary determination of the individual parcels included in the cadastre. Users requiring a boundary determination should consult an Arkansas Registered Land Surveyor (http://www.arkansas.gov/pels/search/search.php) on boundary questions. The digital cadastral data is intended to be a graphical representation of the tax parcel only. Just because a county is listed does NOT imply the data represents county wide coverage. AGIO worked with each county to determine a level of production that warranted the data was ready to be published. For example, in some counties only the north part of the county was covered or in other cases only rural parcels are covered and yet in others only urban parcels. The approach is to begin incremental publishing as production blocks are ready, even though a county may not have county wide coverage. Each case represents a significant amount of data that will be useful immediately. Users should consult the BEGIN_DATE attribute column to determine the age of the data for a given county. This date reflects when the data was received from the county. Digital cadastral data users should be aware the County Assessor Mapping Program adopted a phased approach for developing cadastral data. Phase One includes the production of a parcel centroid for each parcel that bears the attributes prescribed by the state cadastral mapping standard. Phase Two includes the production of parcel polygon geometry and bears the standard attributes. The Arkansas standard closely mirrors the federal Cadastral Core Data Standard established by the Federal Geographic Data Committee, Subcommittee for Cadastral Data. Counties within this file include: Arkansas, Ashley, Baxter, Boone, Carroll, Chicot, Clark, Clay, Columbia, Conway, Craighead, Crawford, Cross, Desha, Faulkner, Franklin, Hot Spring, Howard, Izard, Jackson, Jefferson, Lafayette, Lincoln, Little River, Logan, Lonoke, Madison, Mississippi, Montgomery, Nevada, Newton, Perry, Pike, Poinsett, Polk, Pope, Pulaski, Randolph, Saline, Sebastian, Stone, Van Buren, Washington and White.

Abstract

The dataset was derived by the Bioregional Assessment Programme from multiple the Queensland geology and structural framework dataset. The source dataset is identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

This dataset contains a polygon shapefile of the Belyando Basin province boundary. The Belyando Basin underlies the eastern margin of the Galilee subregion. Extracted from the QLD Geology and Structural Framework of 2012 - the abstract of which is below.

The data on this DVD contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application.

The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale.

The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics).

For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info.

Purpose

This dataset provides a single, merged representation of the Belyando Basin as interpreted by the QLD Geology and Structural Framework of 2012

Dataset History

This dataset has been extracted directly from the QLD Geology and Structural Framework: QLD_STRUCTURAL_FRAMEWORK.shp.

1. Features with the following 'Heirarchy' attributes were selected and extracted:

a) Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

b) Eromanga Basin>Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

c) Drummond Basin>Belyando Basin>Thomson Orogen

d) Galilee Basin>Drummond Basin>Belyando Basin>Thomson Orogen

1. Features were merged together to produce the Belyando Basin province.

The lineage of the QLD Geology and Structural Framework is below:

Data in this release

*ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology

*ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework

*ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology

*Georeferenced Queensland geology map, gravity and magnetic images

*Queensland geology map, structural framework and schematic diagram PDF files

*Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94

Accessing the data

Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites").

Metadata

Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders.

Disclaimer

The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites.

Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination.

The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason.

The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way.

WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties.

Dataset Citation

Bioregional Assessment Programme (XXXX) Belyando Basin Boundary - QLD Structural Framework. Bioregional Assessment Derived Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/4add856a-eb40-4bb2-bd41-f89788884782.

Dataset Ancestors

• Derived From Queensland geology and structural framework - GIS data July 2012

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.

This dataset is a combination of 2 data projects: 1- Data were updated within NYC watershed portions using 1m resolution LiDAR and 1ft orthoimagery collected in 2009 as part of the NYS Digital Ortho Program under contract with NYCDEP under CAT-371.For NYC reservoir areas only: NYCDEP BWS GIS Staff (T. Spies) edited all artificial path and stream transitions to snap exactly to polygon edges representing NYC reservoirs, where those areas were updated by NYCDEP for correct inundation area based on spillway elevation.QA edits to NHD hydrography, including this feature class, were also made where needed based on field verification and correction of the NYCbasin1m boundary.As an additional departure from standard NHD to meet DEP’s needs, DEP GIS staff attributed all flowlines by their respective NYC reservoir basin and NYC water supply “region” as defined in the feature class “NYCbasin1m”. This was done using the “select by location” tool rather than “identity” tool, so as not to split any flowlines across boundaries. Any flowlines crossing basin boundaries in error were corrected by splitting the lines and snapping their endpoints to the appropriate spillway or basin edge instead. After these edits were made, a new geometric network was built to test and ensure all flowlines in the entire dataset were correctly connected so that they can be used for routing.2- Data was updated within portions of Ulster County outside the NYC watershed using NYS 1ft orthoimagery collected in 2013 and multiple Elevation datasets (2013 NYS DEC 1m Lidar Hudson River, 2005 NYS DEC 3m Lidar Ulster Stream Corridors, 1992 USGS 10m Digital Elevation Model (DEM)).Primary quality control was performed visually using enhanced symbology and supporting reference data. A detailed QC checklist is provided in the QC report. Specific emphasis was placed on the areas bordering the NYC Watershed and the areas encompassed by the Town of Woodstock’s local hydrography data. To the extent connections occurred, the data captured on this project was “snapped” to the corresponding locations in the NYC Watershed so that the data could be seamlessly integrated. The hydrography data from the Town of Woodstock, however, was inconsistent when applied to the data capture protocol. Many locally derived features did not appear to be supported by the source data (i.e., they did not exist) and were not included. All visual inspections were made at 1:1000 scale or better. During data capture, the Data Capture Analyst used a separate point feature class named “Flags” to identify locations where there may have been some interpretation or confusion. Later, the QC Analyst also used additional bookmarks in ArcGIS to track locations where additional investigation or interpretation was required. Finally, after an initial pass through the data, the QC Analyst evaluated and resolved all such flags and bookmarks, collaborating with the Data Capture Analyst as necessary to discuss findings and resolve questions.As data was completed, naming convention and separate storage locations were used for data management to ensure that source and modified datasets were clearly separated. In addition, a detailed QC tracking spreadsheet was used to track and manage effort on completing QC and resolving any issues.Finally, after the initial data delivery, several rounds of QC review were performed by Ulster County to include: additional visual inspection of flow line connectivity, geometric network tracking, and utility network analysisMost of the issues that were not readily apparent in the manual QC process were attributed to minor errors in data capture and discovered here. Examples include digitizing lines in the wrong direction (not downstream), existence of multi-part features, and topology errors. In all cases, issues were evaluated and resolved

Analysis of ‘Pre-SGMA Ground Water Management Plans’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/b423b8df-d657-430a-8e97-2369b63e4275 on 27 January 2022.

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

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.

Pre-SGMA Statewide Groundwater Management Plans based on legislative actions: AB3030 (signed into law in 1992), SB 1938 (signed into law in 2002), and AB 359 (signed into law in 2011). For Groundwater Management Plan documents please email SGMPS@water.ca.gov.There are no access nor distribution constraints.There will be no resource maintenance nor update frequency.

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

DESCRIPTION ---------------- VERSIONS version1.0.1 fixes problem with functions version1.0.2 added table dbeel_rivers.rn_rivermouth with GEREM basin, distance to Gibraltar and link to CCM. version1.0.3 fixes problem with functions version1.0.4 adds views rn_rna and rn_rne to the database ---------------- The SUDOANG project aims at providing common tools to managers to support eel conservation in the SUDOE area (Spain, France and Portugal). VISUANG is the SUDOANG Interactive Web Application that host all these tools . The application consists of an eel distribution atlas (GT1), assessments of mortalities caused by turbines and an atlas showing obstacles to migration (GT2), estimates of recruitment and exploitation rate (GT3) and escapement (chosen as a target by the EC for the Eel Management Plans) (GT4). In addition, it includes an interactive map showing sampling results from the pilot basin network produced by GT6. The eel abundance for the eel atlas and escapement has been obtained using the Eel Density Analysis model (EDA, GT4's product). EDA extrapolates the abundance of eel in sampled river segments to other segments taking into account how the abundance, sex and size of the eels change depending on different parameters. Thus, EDA requires two main data sources: those related to the river characteristics and those related to eel abundance and characteristics. However, in both cases, data availability was uneven in the SUDOE area. In addition, this information was dispersed among several managers and in different formats due to different sampling sources: Water Framework Directive (WFD), Community Framework for the Collection, Management and Use of Data in the Fisheries Sector (EUMAP), Eel Management Plans, research groups, scientific papers and technical reports. Therefore, the first step towards having eel abundance estimations including the whole SUDOE area, was to have a joint river and eel database. In this report we will describe the database corresponding to the river’s characteristics in the SUDOE area and the eel abundances and their characteristics. In the case of rivers, two types of information has been collected: River topology (RN table): a compilation of data on rivers and their topological and hydrographic characteristics in the three countries. River attributes (RNA table): contains physical attributes that have fed the SUDOANG models. The estimation of eel abundance and characteristic (size, biomass, sex-ratio and silver) distribution at different scales (river segment, basin, Eel Management Unit (EMU), and country) in the SUDOE area obtained with the implementation of the EDA2.3 model has been compiled in the RNE table (eel predictions). CURRENT ACTIVE PROJECT The project is currently active here : gitlab forgemia TECHNICAL DESCRIPTION TO BUILD THE POSTGRES DATABASE 1. Build the database in postgres. All tables are in ESPG:3035 (European LAEA). The format is postgreSQL database. You can download other formats (shapefiles, csv), here SUDOANG gt1 database. Initial command # open a shell with command CMD # Move to the place where you have downloaded the file using the following command cd c:/path/to/my/folder # note psql must be accessible, in windows you can add the path to the postgres #bin folder, otherwise you need to add the full path to the postgres bin folder see link to instructions below createdb -U postgres eda2.3 psql -U postgres eda2.3 # this will open a command with # where you can launch the commands in the next box Within the psql command create extension "postgis"; create extension "dblink"; create extension "ltree"; create extension "tablefunc"; create schema dbeel_rivers; create schema france; create schema spain; create schema portugal; -- type \q to quit the psql shell Now the database is ready to receive the differents dumps. The dump file are large. You might not need the part including unit basins or waterbodies. All the tables except waterbodies and unit basins are described in the Atlas. You might need to understand what is inheritance in a database. https://www.postgresql.org/docs/12/tutorial-inheritance.html 2. RN (riversegments) These layers contain the topology (see Atlas for detail) dbeel_rivers.rn france.rn spain.rn portugal.rn Columns (see Atlas) gid idsegment source target lengthm nextdownidsegment path isfrontier issource seaidsegment issea geom isendoreic isinternational country dbeel_rivers.rn_rivermouth seaidsegment geom (polygon) gerem_zone_3 gerem_zone_4 (used in EDA) gerem_zone_5 ccm_wso_id country emu_name_short geom_outlet (point) name_basin dist_from_gibraltar_km name_coast basin_name # dbeel_rivers.rn ! mandatory => table at the international level from which # the other table inherit # even if you don't want to use other countries # (In many cases you should ... there are transboundary catchments) download this first. # the rn network must be restored firt ! #table rne and rna refer to it by foreign keys. pg_restore -U postgres -d ed...

North Dakota statewide ambulance service area polygons. The data was created in 2011 to replace an earlier dataset that was obsolete and contained topology errors. The dataset was compiled from the following data sources: North Dakota state maintained county boundaries, ambulance service area shapefiles provided by some counties, PDF files provided by some counties that showed ambulance service boundaries, and a shapefile from Bullberry Services. Update 3/30/2012: Additional attributes were added to the data to show total area of each ASA in square miles and the total population for each ASA based on the 2010 US Census. The following methodologies were used:Update 3/30/2012: To calculate area in square miles, the calculation was made in ArcGIS Desktop within a data frame where the projection was set to Albers Equal Area in order to preserve area and obtain accurate calculations.Update 3/30/2012: To calculate population totals for each ASA, the following method was used. A shapefile was obtained from the US Census that contained census block geometry with population totals for each block. For each ASA, a spatial query was performed where all census blocks whose geographic centroid was within the ASA were selected. The total population for each of these selected census blocks was then summed and appended to the ASA in question. The resulting population totals for each ASA can be considered as very close approximations of the actual population totals. This is because census block polygons do not precisely match ASA boundaries. In most cases ASA boundaries and census block boundaries do match each other but in some cases they do not. In such cases, the total for the block in question is added to the sum of the ASA where the block centroid falls within. Because census block geographies are much smaller than ASA geographies, the "error" introduced with this method is estimated to be small. Furthermore, given available data, this is considered the best approximation of the true total polulation for each ASA short of conduction a new census based on ASA polygons.Williams County GIS downloaded this data on 2/10/2021 from the NDGISHUB website. It was then edited to show only the areas that touch Williams County.

Summary

Rail Crossings is a spatial file maintained by the Federal Railroad Administration (FRA) for use by States and railroads.

Description

FRA Grade Crossings is a spatial file that originates from the National Highway-Rail Crossing, Inventory Program. The program is to provide information to Federal, State, and local governments, as well as the railroad industry for the improvements of safety at highway-rail crossing.

Credits

Federal Railroad Administration (FRA)

Use limitations

There are no access and use limitations for this item.

Extent

West -79.491008 East -75.178954 North 39.733500 South 38.051719

Scale Range Maximum (zoomed in) 1:5,000 Minimum (zoomed out) 1:150,000,000

ArcGIS Metadata ▼►Topics and Keywords ▼►Themes or categories of the resource  transportation

* Content type  Downloadable Data Export to FGDC CSDGM XML format as Resource Description No

Temporal keywords  2013

Theme keywords  Rail

Theme keywords  Grade Crossing

Theme keywords  Rail Crossings

Citation ▼►Title rr_crossings Creation date 2013-03-15 00:00:00

Presentation formats  * digital map

Citation Contacts ▼►Responsible party  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Responsible party  Organization's name Research and Innovative Technology Administration/Bureau of Transportation Statistics Individual's name National Transportation Atlas Database (NTAD) 2013 Contact's position Geospatial Information Systems Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 e-mail address answers@BTS.gov

Resource Details ▼►Dataset languages  * English (UNITED STATES) Dataset character set  utf8 - 8 bit UCS Transfer Format

Spatial representation type  * vector

* Processing environment Microsoft Windows 7 Version 6.1 (Build 7600) ; Esri ArcGIS 10.2.0.3348

Credits Federal Railroad Administration (FRA)

ArcGIS item properties  * Name USDOT_RRCROSSINGS_MD * Size 0.047 Location withheld * Access protocol Local Area Network

Extents ▼►Extent  Geographic extent  Bounding rectangle  Extent type  Extent used for searching * West longitude -79.491008 * East longitude -75.178954 * North latitude 39.733500 * South latitude 38.051719 * Extent contains the resource Yes

Extent in the item's coordinate system  * West longitude 611522.170675 * East longitude 1824600.445629 * South latitude 149575.449134 * North latitude 752756.624659 * Extent contains the resource Yes

Resource Points of Contact ▼►Point of contact  Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role  custodian

Resource Maintenance ▼►Resource maintenance  Update frequency  annually

Resource Constraints ▼►Constraints  Limitations of use There are no access and use limitations for this item.

Spatial Reference ▼►ArcGIS coordinate system  * Type Projected * Geographic coordinate reference GCS_North_American_1983_HARN * Projection NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet * Coordinate reference details  Projected coordinate system  Well-known identifier 2893 X origin -120561100 Y origin -95444400 XY scale 36953082.294548117 Z origin -100000 Z scale 10000 M origin -100000 M scale 10000 XY tolerance 0.0032808333333333331 Z tolerance 0.001 M tolerance 0.001 High precision true Latest well-known identifier 2893 Well-known text PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1312333.333333333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-77.0],PARAMETER["Standard_Parallel_1",38.3],PARAMETER["Standard_Parallel_2",39.45],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2893]]

Reference system identifier  * Value 2893 * Codespace EPSG * Version 8.1.1

Spatial Data Properties ▼►Vector  ▼►* Level of topology for this dataset  geometry only

Geometric objects  Feature class name USDOT_RRCROSSINGS_MD * Object type  point * Object count 1749

ArcGIS Feature Class Properties  ▼►Feature class name USDOT_RRCROSSINGS_MD * Feature type Simple * Geometry type Point * Has topology FALSE * Feature count 1749 * Spatial index TRUE * Linear referencing FALSE

Data Quality ▼►Scope of quality information  ▼►Resource level  attribute Scope description  Attributes The States and railroads maintain their own file and get updated to the FRA. The information is reported to the FRA on the U.S. DOT-ARR Crossing inventory form.

Attributes The quality of the inventory can vary because a record of grade crossing location is being maintained by each state and railroad that is responsible for maintaining its respective information.

Lineage ▼►Lineage statement The data was downloaded from the HWY-Rail Crossing Inventory Files. All crossings that were closed or abandon were queried out of the data. All of the crossings with a zero within the latitude or longitude were queried out. Any crossing outside a bounding box of box ((Latitude >= 18 & Latitude <= 72) AND (Longitude >= -171 & Longitude <= -63)) were queried out.

Geoprocessing history ▼►Process  Date 2013-08-14 10:41:15 Tool location c:\program files (x86)\arcgis\desktop10.0\ArcToolbox\Toolboxes\Data Management Tools.tbx\Project Command issued Project RR_CROSSINGS_MD_USDOT \shagbfs\gis_projects\Railroad_Crossings_MD\Railroad_Crossings_MD.gdb\RR_CROSSINGS_MD_USDOT_83FTHARN PROJCS['NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet',GEOGCS['GCS_North_American_1983_HARN',DATUM['D_North_American_1983_HARN',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',1312333.333333333],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-77.0],PARAMETER['Standard_Parallel_1',38.3],PARAMETER['Standard_Parallel_2',39.45],PARAMETER['Latitude_Of_Origin',37.66666666666666],UNIT['Foot_US',0.3048006096012192]] WGS_1984_(ITRF00)_To_NAD_1983_HARN GEOGCS['GCS_WGS_1984',DATUM['D_WGS_1984',SPHEROID['WGS_1984',6378137.0,298.25722356]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]] Include in lineage when exporting metadata No

Distribution ▼►Distributor  ▼►Contact information  Individual's name Office of Geospatial Information Systems Organization's name Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) Contact's role  distributor

Contact information  ▼►Phone  Voice 202-366-DATA

Address  Type  Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 Country US e-mail address answers@bts.gov

Available format  Name Shapefile Version 2013 File decompression technique no compression applied

Ordering process  Instructions Call (202-366-DATA), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2013 DVD. The NTAD DVD can be ordered from the online bookstore at www.bts.gov. Individual datasets from the NTAD can also be downloaded from the Office of Geospatial Information Systems website at http://www.bts.gov/programs/geographic_information_services/

Transfer options  Transfer size 6.645

Medium of distribution  Medium name  DVD

How data is written  iso9660 (CD-ROM) Recording density 650 Density units of measure Megabytes

Transfer options  Online source  Description  National Transportation Atlas Databases (NTAD) 2013

Distribution format  * Name Shapefile Version 2013

Transfer options  * Transfer size 0.047

Online source  Location http://www.bts.gov/programs/geographic_information_services/

Fields ▼►Details for object USDOT_RRCROSSINGS_MD ▼►* Type Feature Class * Row count 1749

Field FID ▼►* Alias FID * Data type OID * Width 4 * Precision 0 * Scale 0 * Field description Internal feature number.

* Description source ESRI

* Description of values Sequential unique whole numbers that are automatically generated.

Field Shape ▼►* Alias Shape * Data type Geometry * Width 0 * Precision 0 * Scale 0 * Field description Feature geometry.

* Description source ESRI

* Description of values Coordinates defining the features.

Field OBJECTID ▼►* Alias OBJECTID * Data type Integer * Width 9 * Precision 9 * Scale 0

Field CROSSING ▼►* Alias CROSSING * Data type String * Width 7 * Precision 0 * Scale 0 Field description US DOT Valid Crossing ID Number

Description source FRA

Field RAILROAD ▼►* Alias RAILROAD * Data type String * Width 4 * Precision 0 * Scale 0 Field description The

This data set contains OCS block outlines (clipped) to the GOM Planning Area Boundary in ArcGIS shape file format for the BOEM Gulf of Mexico Region. Leases: OCS Lease Blocks that are currently leased from the federal government by industry for the purpose of development of traditional oil or gas energy products and may or may not be actively developed or producing. Leases in state waters are not included in this layer. The Outer Continental Shelf Lands Act (OCSLA) (43 U.S.C. 1331-1356a), as amended, authorizes the Secretary of the Interior to issue, on a competitive basis, leases for oil and gas, and sulfur, in submerged lands of the Outer Continental Shelf. The Act authorizes the Secretary to grant rights-of-way and easements through the submerged lands of the OCS.An OCS lease is an agreement that is issued under section 8 or maintained under section 6 of the Act and that authorizes exploration for, and development and production of, minerals on the OCS. The term also means the area covered by that agreement, whichever the context requires. The areas covered by the lease agreement consist of one or more OCS Lease Blocks, or any leasable portion thereof, bid upon as a single administrative unit, that will be part of a single lease.Blocks: This data set contains OCS block outlines (clipped) to the GOM Planning Area Boundary in ArcGIS shape file format for the BOEM Gulf of Mexico Region. OCS blocks are used to define small geographic areas within an Official Protraction Diagram (OPD) for leasing and administrative purposes. These blocks have been clipped along the Submerged Lands Act (SLA) boundary and along the Continental Shelf Boundaries. Additional details are available from: http://www.boem.gov/uploadedFiles/BOEM/Oil_and_Gas_Energy_Program/Mapping_and_Data/99-0006.pdfBecause 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 Supplemental Official Block Diagrams (SOBDs) serve as the legal definition for BOEM offshore boundary coordinates and area descriptions.

This data set contains point locations for oil and gas platforms (structures) located in the Gulf of Mexico federal waters. Note: Platforms are being added or modified continuously; obtaining updates of this database are required to know the true distribution of platform 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. An oil platform, offshore platform, or (colloquially) oil rig is a large structure with facilities to drill wells (optionally), to extract and process oil and natural gas, or to temporarily store product until it can be brought to shore for refining and marketing. In many cases, the platform contains facilities to house the workforce as well. Depending on the circumstances, the platform may be fixed to the ocean floor, may consist of an artificial island, or may float. Remote subsea wells may also be connected to a platform by flow lines and by umbilical connections. These sub-sea solutions may consist of one or more subsea wells, or of one or more manifold centers for multiple wells.

To operate an ambulance service and ambulances in Arizona, an application must be filed with the Department of Health Services, Bureau of Emergency Medical Services & Trauma System, and a Certificate of Necessity (CON) granted by the Director. This dataset contains a representation of the CON service boundaries. While this dataset is complete for Arizona, there are known issues with intra & inter-polygon topology (gaps/slivers) and alignment with features used to create the CON boundaries. Please refer to the service area boundary described in the CON certificate, which can be found on this website. The data was last updated January 2024. For more information visit AZ the Dept. of Health Services Ground Ambulance Program Certificate of Necessity (CON) Holders.

This data set contains point locations for oil and gas platforms (structures) located in the Gulf of Mexico federal waters. Note: Platforms are being added or modified continuously; obtaining updates of this database are required to know the true distribution of platform 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.An oil platform, offshore platform, or (colloquially) oil rig is a large structure with facilities to drill wells (optionally), to extract and process oil and natural gas, or to temporarily store product until it can be brought to shore for refining and marketing. In many cases, the platform contains facilities to house the workforce as well.Depending on the circumstances, the platform may be fixed to the ocean floor, may consist of an artificial island, or may float. Remote subsea wells may also be connected to a platform by flow lines and by umbilical connections. These sub-sea solutions may consist of one or more subsea wells, or of one or more manifold centers for multiple wells.

This data set contains point locations for oil and gas platforms (structures) located in the Gulf of Mexico federal waters. Note: Platforms are being added or modified continuously; obtaining updates of this database are required to know the true distribution of platform 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. An oil platform, offshore platform, or (colloquially) oil rig is a large structure with facilities to drill wells (optionally), to extract and process oil and natural gas, or to temporarily store product until it can be brought to shore for refining and marketing. In many cases, the platform contains facilities to house the workforce as well. Depending on the circumstances, the platform may be fixed to the ocean floor, may consist of an artificial island, or may float. Remote subsea wells may also be connected to a platform by flow lines and by umbilical connections. These sub-sea solutions may consist of one or more subsea wells, or of one or more manifold centers for multiple wells.