This data set has been updated and the more recent (2013) database is available at the link below. The registry is composed of a geodatabase with two files that represents observations and survey effort. The database is compiled by US Fish and Wildlife Service in cooperation with the Bureau of Land Management to serve as the prime repository for yellow-billed loon distribution information. A contacts file of research leaders is also included (yblo_2009con.dbf). A shapefile dataset is also provided. This database is updated annually and is also available in shapefile format from USFWS. Please see link to 2013 update.

The Geodatabase to Shapefile Warning Tool examines feature classes in input file geodatabases for characteristics and data that would be lost or altered if it were transformed into a shapefile. Checks include:
1) large files (feature classes with more than 255 fields or over 2GB), 2) field names longer than 10 characters
string fields longer than 254 characters, 3) date fields with time values 4) NULL values, 5) BLOB, guid, global id, and raster field types, 6) attribute domains or subtypes, and 7) annotation or topology

The results of this inspection are written to a text file ("warning_report_[geodatabase_name]") in the directory where the geodatabase is located. A section at the top provides a list of feature classes and information about the geodatabase as a whole. The report has a section for each valid feature class that returned a warning, with a summary of possible warnings and then more details about issues found.

The tool can process multiple file geodatabases at once. A separate text file report will be created for each geodatabase. The toolbox was created using ArcGIS Pro 3.7.11.

For more information about this and other related tools, explore the Geospatial Data Curation toolkit

This packaged data collection contains all of the outputs from our primary model, including the following data layers: Habitat Cores (vector polygons) Least-cost Paths (vector lines) Least-cost Corridors (raster) Least-cost Corridors (vector polygon interpretation) Modeling Extent (vector polygon) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) or raster GeoTIFF (.tif) formats.

This data release contains the analytical results and evaluated source data files of geospatial analyses for identifying areas in Alaska that may be prospective for different types of lode gold deposits, including orogenic, reduced-intrusion-related, epithermal, and gold-bearing porphyry. The spatial analysis is based on queries of statewide source datasets of aeromagnetic surveys, Alaska Geochemical Database (AGDB3), Alaska Resource Data File (ARDF), and Alaska Geologic Map (SIM3340) within areas defined by 12-digit HUCs (subwatersheds) from the National Watershed Boundary dataset. The packages of files available for download are: 1. LodeGold_Results_gdb.zip - The analytical results in geodatabase polygon feature classes which contain the scores for each source dataset layer query, the accumulative score, and a designation for high, medium, or low potential and high, medium, or low certainty for a deposit type within the HUC. The data is described by FGDC metadata. An mxd file, and cartographic feature classes are provided for display of the results in ArcMap. An included README file describes the complete contents of the zip file. 2. LodeGold_Results_shape.zip - Copies of the results from the geodatabase are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file. 3. LodeGold_SourceData_gdb.zip - The source datasets in geodatabase and geotiff format. Data layers include aeromagnetic surveys, AGDB3, ARDF, lithology from SIM3340, and HUC subwatersheds. The data is described by FGDC metadata. An mxd file and cartographic feature classes are provided for display of the source data in ArcMap. Also included are the python scripts used to perform the analyses. Users may modify the scripts to design their own analyses. The included README files describe the complete contents of the zip file and explain the usage of the scripts. 4. LodeGold_SourceData_shape.zip - Copies of the geodatabase source dataset derivatives from ARDF and lithology from SIM3340 created for this analysis are also provided in shapefile and CSV formats. The included README file describes the complete contents of the zip file.

The New Hampshire Hydrography Dataset (NHHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the state's surface water drainage system. The NHHD, developed at 1:24,000 scale, is an extract from the high-resolution National Hydrography Dataset (NHD) housed at the US Geological Survey.The NHHD Shapefile Extract contains the NHDFlowline, NHDWaterbody and NHDArea feature classes from the original NHHD geodatabase. These shapefiles cover the extent of the sixteen cataloging units that intersect the State of NH, and contain reach codes for networked features, stream order, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the the Atlantic Ocean. However, because this data is no longer contained in the original geodatabase, the networking capabilities of the NHDFlowline has been lost.

social system, socio-economic resources, justice, BES, Environmental disamentities, Environmental Justice, Zoning Board of Appeals

   Summary


   For use in the environmental injustices study of Baltimore relating to patterns of environmental disamenties in relation to low income/minority communities.


   Description


   This feature class layer is a point dataset of authorizing ordinances from the Baltimore City Council and Mayor from 1930 until 1999 concerning identified environmental disamentities. The data was gathered from records from the City Council since 1930 relating to decisions concerning land-uses considered to be environmental disamentities and is to be used to examine environmental injustices involving low income/minority communities in Baltimore. To examine if environmental injustices exist in Baltimore, this point layer will be overlayed with race/income data to determine if patterns of inequity exist. Points were placed manually using the associated addresses from the Ordinance_master dataset and using ISTAR 2004 data in conjunction with Baltimore parcel data. The Ordinance_ID number associated with each point relates to its appeal number from the City Council. Multiple points on the data layer have the same Ordinance_ID. This point layer can be joined with the Ordinance_master data layer based on the field "Ordinance_ID" and using the relationship "Ordinance_point_relationship".


   Credits


   UVM Spatial Analysis Lab


   Use limitations


   None. There are no restrictions on the use of this dataset. The authors of this dataset make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data.


   Extent



   West -76.707701  East -76.526991 

   North 39.371885  South 39.200794 



   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The New Hampshire Hydrography Dataset (NHHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the state's surface water drainage system. The NHHD, developed at 1:24,000 scale, is an extract from the high-resolution National Hydrography Dataset (NHD) housed at the US Geological Survey.The NHHD Shapefile Extract contains the NHDFlowline, NHDWaterbody and NHDArea feature classes from the original NHHD geodatabase. These shapefiles cover the extent of the sixteen cataloging units that intersect the State of NH, and contain reach codes for networked features, stream order, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the the Atlantic Ocean. However, because this data is no longer contained in the original geodatabase, the networking capabilities of the NHDFlowline has been lost. This dataset contains data published by USGS in April 2019.

Mineral resource occurrence data covering the world, most thoroughly within the U.S. This database contains the records previously provided in the Mineral Resource Data System (MRDS) of USGS and the Mineral Availability System/Mineral Industry Locator System (MAS/MILS) originated in the U.S. Bureau of Mines, which is now part of USGS. The MRDS is a large and complex relational database developed over several decades by hundreds of researchers and reporters. While database records describe mineral resources worldwide, the compilation of information was intended to cover the United States completely, and its coverage of resources in other countries is incomplete. The content of MRDS records was drawn from reports previously published or made available to USGS researchers. Some of those original source materials are no longer available. The information contained in MRDS was intended to reflect the reports used as sources and is current only as of the date of those source reports. Consequently MRDS does not reflect up-to-date changes to the operating status of mines, ownership, land status, production figures and estimates of reserves and resources, or the nature, size, and extent of workings. Information on the geological characteristics of the mineral resource are likely to remain correct, but aspects involving human activity are likely to be out of date.

The Watershed Boundary Dataset (WBD) from The National Map (TNM) defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The drainage areas are nested within each other so that a large drainage area, such as the Upper Mississippi River, is composed of multiple smaller drainage areas, such as the Wisconsin River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds. For additional information on the WBD, go to https://nhd.usgs.gov/wbd.html. The USGS National Hydrography Dataset (NHD) service is a companion dataset to the WBD. The NHD is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000-scale maps and referred to as high resolution NHD, and the other based on 1:100,000-scale maps and referred to as medium resolution NHD. Additional selected areas in the United States are available based on larger scales, such as 1:5,000-scale or greater, and referred to as local resolution NHD. For more information on the NHD, go to https://nhd.usgs.gov/index.html. Hydrography data from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. Hydrography data is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain WBD and NHD data in either Esri File or Personal Geodatabase, or Shapefile formats. The Watershed Boundary Dataset is being developed under the leadership of the Subcommittee on Spatial Water Data, which is part of the Advisory Committee on Water Information (ACWI) and the Federal Geographic Data Committee (FGDC). The USDA Natural Resources Conservation Service (NRCS), along with many other federal agencies and national associations, have representatives on the Subcommittee on Spatial Water Data. As watershed boundary geographic information systems (GIS) coverages are completed, statewide and national data layers will be made available via the Geospatial Data Gateway to everyone, including federal, state, local government agencies, researchers, private companies, utilities, environmental groups, and concerned citizens. The database will assist in planning and describing water use and related land use activities. Resources in this dataset:Resource Title: Watershed Boundary Dataset (WBD). File Name: Web Page, url: https://www.nrcs.usda.gov/wps/portal/nrcs/detail/national/water/watersheds/dataset/?cid=nrcs143_021630 Web site for the Watershed Boundary Dataset (WBD), including links to:

Review Data Availability (Status Maps) Obtain Data by State, County, or Other Area Obtain Seamless National Data offsite link image
Geospatial Data Tools National Technical and State Coordinators Information about WBD dataset

These datasets each consist of a folder containing a personal geodatabase of the NHD, and shapefiles used in the HydroDEM process. These files are provided as a means to document exactly which lines were used to develop the HydroDEMs. Each folder contains a line shapefile named for the 8-digit HUC code, containing the NHD flowlines that comprise the coastline for that island. The “hydrolines.shp” shapefile contains the lines that were burned into the DEM. These lines were selected from the NHD flowlines, with some minor editing in places. The “wbpolys.shp” shapefile contains the water-body polygons that were selected from the NHD and used in the bathymetric gradient process. The folders for HUCs 20010000 (Hawaii) and 20020000 (Maui) also contain a “walls.shp” shapefile, which contains the lines that were superimposed on the surface as “walls.”

Baltimore City Highways. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. When compared to high-resolution imagery and detailed street data offsets as great as 50m were observed. Due to positional accuracy errors this dataset should be used with caution. There are no attributes associated with this dataset. For the best available transportation data use the Roads_GDT_MSA dataset.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Detailed street center lines for Baltimore City. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. This dataset depicts the linear boundaries for street and paved areas in Baltimore City and has an extremely high degree of positional accuracy. For the best available transportation data use the Roads_GDT_MSA dataset. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The Digital Geologic-GIS Map of Santa Rosa Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sris_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sris_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sris_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sris_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sris_geology_metadata.txt or sris_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Abstract

The dataset was derived by the Bioregional Assessment Programme from multiple datasets. 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.

Combined groundwater bores database for the Hunter subregion drawn from source data. The data are stored in an ArcGIS file geodatabase. The geodatabase consists of five piont shapefiles (associated with the input datasets in the lineage) and three tables. The shapefiles are:

Alluvium_bores.shp

HUN_GW_BOM_bores_from_AssetsDB.shp

HUN_GW_BOM_bores_from_AssetsDB_20150908.shp

HUN_GW_bores_from_HYDMEA_2012_v01.shp

HUN_GW_bores_from_NSW_NGIS_201407

There are 2121 bores in the Aluvium_bores.shp, 7377 bores in the HUN_GW_BOM_bores_from_AssetsDB.shp, 7377 bores in the HUN_GW_BOM_bores_from_AssetsDB_20150908.shp (same as previous but with extra attributes added to the table), 590 bores in the HUN_GW_bores_from_HYDMEA_2012_v01.shp and 7753 bores in the HUN_GW_bores_from_NSW_NGIS_201407.shp.

Dataset History

Bore location point features from the the two source datasets were selected for the Hunter subregion and compiled in a file geodatabase. Also contains subsets of this collection. Eg bores on Alluvium which was derived by selecting bores from the NGIS dataset which were located within the HUN Alluvium (1:1m Geology). Attributes relating to the EC, depth and water sources relating to selected bores (where data were available) were added (joined) to the table of HUN_GW_BOM_bores_from_AssetsDB.shp to create HUN_GW_BOM_bores_from_AssetsDB_20150908.shp.

Dataset Citation

Bioregional Assessment Programme (2015) HUN bores v01. Bioregional Assessment Derived Dataset. Viewed 09 October 2018, http://data.bioregionalassessments.gov.au/dataset/97931fff-5ee9-4efb-b59c-ead03345abbe.

Dataset Ancestors

• Derived From NSW Office of Water Surface Water Entitlements Locations v1_Oct2013

• Derived From NSW Office of Water - National Groundwater Information System 20140701

• Derived From Travelling Stock Route Conservation Values

• Derived From NSW Wetlands

• Derived From Threatened migratory shorebird habitat mapping DECCW May 2006

• Derived From Communities of National Environmental Significance Database - RESTRICTED - Metadata only

• Derived From Climate Change Corridors for Nandewar and New England Tablelands

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas

• Derived From Asset database for the Hunter subregion on 27 August 2015

• Derived From Birds Australia - Important Bird Areas (IBA) 2009

• Derived From Estuarine Macrophytes of Hunter Subregion NSW DPI Hunter 2004

• Derived From Hunter CMA GDEs (DRAFT DPI pre-release)

• Derived From Camerons Gorge Grassy White Box Endangered Ecological Community (EEC) 2008

• Derived From Atlas of Living Australia NSW ALA Portal 20140613

• Derived From Spatial Threatened Species and Communities (TESC) NSW 20131129

• Derived From Gippsland Project boundary

• Derived From Bioregional Assessment areas v04

• Derived From Asset database for the Hunter subregion on 24 February 2016

• Derived From Natural Resource Management (NRM) Regions 2010

• Derived From Asset database for the Hunter subregion on 12 February 2015

• Derived From NSW Office of Water Surface Water Offtakes - Hunter v1 24102013

• Derived From National Groundwater Dependent Ecosystems (GDE) Atlas (including WA)

• Derived From Hydstra Groundwater Measurement Update - NSW Office of Water, Nov2013

• Derived From Asset list for Hunter - CURRENT

• Derived From Species Profile and Threats Database (SPRAT) - Australia - Species of National Environmental Significance Database (BA subset - RESTRICTED - Metadata only)

• Derived From Northern Rivers CMA GDEs (DRAFT DPI pre-release)

• Derived From GEODATA TOPO 250K Series 3, File Geodatabase format (.gdb)

• Derived From Ramsar Wetlands of Australia

• Derived From Native Vegetation Management (NVM) - Manage Benefits

• Derived From GEODATA TOPO 250K Series 3

• Derived From NSW Catchment Management Authority Boundaries 20130917

• Derived From Geological Provinces - Full Extent

• Derived From NSW Office of Water Surface Water Licences Processed for Hunter v1 20140516

• Derived From GW Element Bores with Unknown FTYPE Hunter NSW Office of Water 20150514

• Derived From New South Wales NSW Regional CMA Water Asset Information WAIT tool databases, RESTRICTED Includes ALL Reports

• Derived From Commonwealth Heritage List Spatial Database (CHL)

• Derived From Bioregional Assessment areas v03

• Derived From Bioregional Assessment areas v06

• Derived From Bioregional Assessment areas v05

• Derived From National Heritage List Spatial Database (NHL) (v2.1)

• Derived From Climate Change Corridors (Dry Habitat) for North East NSW

• Derived From Groundwater Entitlement Hunter NSW Office of Water 20150324

• Derived From Asset database for the Hunter subregion on 20 July 2015

• Derived From NSW Office of Water combined geodatabase of regulated rivers and water sharing plan regions

• Derived From NSW Office of Water Groundwater Licence Extract, North and South Sydney - Oct 2013

• Derived From Asset database for the Hunter subregion on 16 June 2015

• Derived From Australia World Heritage Areas

• Derived From Lower Hunter Spotted Gum Forest EEC 2010

• Derived From NSW Office of Water GW licence extract linked to spatial locations for NorthandSouthSydney v3 13032014

• Derived From Fauna Corridors for North East NSW

• Derived From Surface Geology of Australia, 1:1 000 000 scale, 2012 edition

• Derived From Climate Change Corridors Coastal North East NSW

• Derived From Groundwater Economic Elements Hunter NSW 20150520 PersRem v02

• Derived From NSW Office of Water - GW licence extract linked to spatial locations for North and South Sydney v2 20140228

• Derived From HUN AssetList Database v1p2 20150128

• Derived From [New

The Northern Canada geodatabase contains a selection of the data from the Atlas of Canada Reference Map - Northern Canada / Nord du Canada (MCR 36). The geodatabase is comprised of two feature data sets (annotation and geometry), and the shaded relief. The annotation feature dataset comprises the annotation feature classes. All annotation feature classes were derived for MCR 36 and all text placements are based on the font type and size used for the reference map. The geometry feature dataset is comprised of data for: boundaries, roads, railways, airports, seaplane bases, ports, populated places, rivers, lakes, mines, oil/natural gas fields, hydroelectric generating stations, federal protected areas, ice shelves, permanent polar sea ice limit and the treeline. The geodatabase can be downloaded as feature data sets or as shapefiles.

24K Hydro File Geodatabase, including bank lines, flow lines, junction points, hydro lines, water bodies, hydro points, and a network. Access the user guide, data dictionaries, and metadata below.The DNR Hydrography database was developed statewide using several 1:24,000-scale sources. This data layer includes information about surface water features represented on the USGS 1:24,000-scale topographic map series such as perennial and intermittent streams, lakes, etc. Because the sources of the Hydrography data span many years and originate from several sources, the data may reflect areas of transition from one source to another. As a result, the water features as represented in the Hydrography data may not always match what you see on a particular USGS quad or Digital Raster Graphic (DRG). General source information is presented on this map: Wisconsin Hydrography Source Information. Note: Wetlands delineations are not included in the DNR Hydrography data layer. For information about DNR Wetlands data, see the Wisconsin Wetland Inventory web page.Report errors in this data to Dennis Wiese (dennis.wiese@wisconsin.gov) with the following information:HYDROID of the feature in question; OR if the feature is missing, a location coordinate or description (e.g. latitude/longitude, Public Land Survey System Township, Range, and Section identifier) that identifies the area in question.Optional but very helpful: a screen capture of the area in question, or the Water Body Identification Code (WBIC) of the feature in question.DNR staff can access the hydrography database in the agency's central GIS data repository. The hydrography feature classes are stored in the feature dataset "W23324.WD_HYDRO_DATA_24K".USER GUIDES AND DOCUMENTATION: WDNR_HYDRO_24k_GETTING STARTED WDNR HYDRO 24K UPDATES DOCUMENT 24K HYDRO DECISION RULESData Dictionaries and Metadata WDNR_HYDRO_24k_waterbody_data_dict WDNR_HYDRO_24k_waterbody_metadata WDNR_HYDRO_24k_flowline_data_dict WDNR_HYDRO_24k_flowline_metadata WDNR_HYDRO_24k_bank_data_dict WDNR_HYDRO_24k_bank_metadata WDNR_HYDRO_24k_junction_data_dict WDNR_HYDRO_24k_junction_metadata WDNR_HYDRO_24k_line_data_dict WDNR_HYDRO_24k_line_metadata WDNR_HYDRO_24k_flowline_wbic_data_dict WDNR_HYDRO_24k_flowline_wbic_metadata WDNR_HYDRO_24k_waterbody_wbic_data_dict WDNR_HYDRO_24k_waterbody_wbic_metadataArcMap Layer (.lyr) Files 24k Hydro Flowline Duration 24k Hydro Bank Lines 24k Hydro Flowline Streams 24k Hydro Waterbody Open Water

Single light rail line that runs north/south through Baltimore City and into Baltimore County. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. When compared to high-resolution imagery and other transportation datasets positional inaccuracies were observed. As a result caution should be taken when using this dataset. There are no attributes associated with this dataset. For the best available railroads data use the Railroads_GDT_MSA dataset. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The New Hampshire Hydrography Dataset (NHHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that make up the state's surface water drainage system. The NHHD, developed at 1:24,000 scale, is an extract from the high-resolution National Hydrography Dataset (NHD) housed at the US Geological Survey.The NHHD Shapefile Extract contains the NHDFlowline, NHDWaterbody and NHDArea feature classes from the original NHHD geodatabase. These shapefiles cover the extent of the sixteen cataloging units that intersect the State of NH, and contain reach codes for networked features, stream order, flow direction, names, and centerline representations for areal water bodies. Reaches are also defined on waterbodies and the approximate shorelines of the the Atlantic Ocean. However, because this data is no longer contained in the original geodatabase, the networking capabilities of the NHDFlowline has been lost. This dataset contains data published by USGS in April 2019.

Obtain the Complete WRQS DatasetClick the link below to download the dataset in a geodatabase format:

WRQS (Geodatabase)

Please note, the complete dataset is too large for shapefile format due to the 2GB size limitation of shapefiles. The geodatabase format allows for larger file sizes, making it ideal for the complete WRQS dataset.

If you only need a portion of the WRQS dataset (less than 2,000 records), use the interactive map interface in DNRC's Open Data Portal to filter and select specific features and download your selected data in various available formats. This method is ideal for users who require only specific regions or feature types or prefer working with smaller, more manageable file sizes.Details

The Montana Water Right Query System Dataset contains water rights information for the state of Montana. It comprises 10 datasets. The spatial datasets include Points of Diversion (Estimated locations of water right diversion points), Places of Use (Polygons representing areas where water rights are utilized), Reservoirs (Point locations of water storage facilities). Additionally, the dataset includes 7 associated tables: Public Versions, Owners, Change Authorization Scanned Docs, Geocodes, Other Versions, Cases, and Water Right Types.

This comprehensive dataset is derived from the Department of Natural Resources and Conservation (DNRC) Water Rights Query Systems Database. It provides spatial and tabular information crucial for understanding water rights distribution and management in Montana.

For the most up-to-date version of the water rights database or detailed reference information, users should contact the DNRC Water Resources Division at https://dnrc.mt.gov/Water-Resources/Water-Rights/ or call 406-444-6610.

The Northern Canada geodatabase contains a selection of the data from the Atlas of Canada Reference Map - Northern Canada / Nord du Canada (MCR 36). The geodatabase is comprised of two feature data sets (annotation and geometry), and the shaded relief. The annotation feature dataset comprises the annotation feature classes. All annotation feature classes were derived for MCR 36 and all text placements are based on the font type and size used for the reference map. The geometry feature dataset is comprised of data for: boundaries, roads, railways, airports, seaplane bases, ports, populated places, rivers, lakes, mines, oil/natural gas fields, hydroelectric generating stations, federal protected areas, ice shelves, permanent polar sea ice limit and the treeline. The geodatabase can be downloaded as feature data sets or as shapefiles.