Digital data is provided for the indexes of: - 1:100,000 scale topographic maps - 1:250,000 scale topographic maps - 1:1,000,000 scale General Reference maps

These indexes are those used in the online map index dashboards and web maps. They contain value-add attributes, including map number, map name, map title, year published, the latitude and longitude of the extents of the maps sheets and data tiles covering Australia. They also include a link to download the map.

Available in ESRI Shapefile and GDB.

Introduction and Rationale: Due to our increasing understanding of the role the surrounding landscape plays in ecological processes, a detailed characterization of land cover, including both agricultural and natural habitats, is ever more important for both researchers and conservation practitioners. Unfortunately, in the United States, different types of land cover data are split across thematic datasets that emphasize agricultural or natural vegetation, but not both. To address this data gap and reduce duplicative efforts in geospatial processing, we merged two major datasets, the LANDFIRE National Vegetation Classification (NVC) and USDA-NASS Cropland Data Layer (CDL), to produce an integrated land cover map. Our workflow leveraged strengths of the NVC and the CDL to produce detailed rasters comprising both agricultural and natural land-cover classes. We generated these maps for each year from 2012-2021 for the conterminous United States, quantified agreement between input layers and accuracy of our merged product, and published the complete workflow necessary to update these data. In our validation analyses, we found that approximately 5.5% of NVC agricultural pixels conflicted with the CDL, but we resolved a majority of these conflicts based on surrounding agricultural land, leaving only 0.6% of agricultural pixels unresolved in our merged product. Contents: Spatial data Attribute table for merged rasters Technical validation data Number and proportion of mismatched pixels Number and proportion of unresolved pixels Producer's and User's accuracy values and coverage of reference data Resources in this dataset:Resource Title: Attribute table for merged rasters. File Name: CombinedRasterAttributeTable_CDLNVC.csvResource Description: Raster attribute table for merged raster product. Class names and recommended color map were taken from USDA-NASS Cropland Data Layer and LANDFIRE National Vegetation Classification. Class values are also identical to source data, except classes from the CDL are now negative values to avoid overlapping NVC values. Resource Title: Number and proportion of mismatched pixels. File Name: pixel_mismatch_byyear_bycounty.csvResource Description: Number and proportion of pixels that were mismatched between the Cropland Data Layer and National Vegetation Classification, per year from 2012-2021, per county in the conterminous United States.Resource Title: Number and proportion of unresolved pixels. File Name: unresolved_conflict_byyear_bycounty.csvResource Description: Number and proportion of unresolved pixels in the final merged rasters, per year from 2012-2021, per county in the conterminous United States. Unresolved pixels are a result of mismatched pixels that we could not resolve based on surrounding agricultural land (no agriculture with 90m radius).Resource Title: Producer's and User's accuracy values and coverage of reference data. File Name: accuracy_datacoverage_byyear_bycounty.csvResource Description: Producer's and User's accuracy values and coverage of reference data, per year from 2012-2021, per county in the conterminous United States. We defined coverage of reference data as the proportional area of land cover classes that were included in the reference data published by USDA-NASS and LANDFIRE for the Cropland Data Layer and National Vegetation Classification, respectively. CDL and NVC classes with reference data also had published accuracy statistics. Resource Title: Data Dictionary. File Name: Data_Dictionary_RasterMerge.csv

Part of VMREFTAB, the set of Reference Tables for the Victorian Spatial Data Libary (VSDL) suite of products.

The MD_COLUMN_NAME_MAPPING table maps VSDL object column names that are longer than 10 characters to column names that are less than 11 characters long.

This mapping supports the generation and importing of shapefiles whose column names cannot be longer than 10 characters.

In some instances, column name mapping may be explicitly applied to a table. In most instances the default column name mapping will be applied (TABLE_OWNER and TABLE_NAME equal to "_DEFAULT").

Unique mapping of column names for an object is assured when using this table.

Basemap/CityLimits (MapServer)View In: ArcGIS JavaScript ArcGIS.com Map Google Earth ArcMap ArcGIS Explorer View Footprint In: ArcGIS.com Map Service Description: Provides a service with Dallas City Limits Map Name: Layers LegendAll Layers and TablesLayers:City Limits (0)Description: Copyright Text: City of Dallas GIS Services Spatial Reference: 102738 (2276) Single Fused Map Cache: false Initial Extent:XMin: 2458212.14561682YMin: 7001293.823664693XMax: 2564792.701172376YMax: 7015337.379220249Spatial Reference: 102738 (2276) Full Extent:XMin: 2430145.721114889YMin: 6909399.421033725XMax: 2592859.1256743073YMax: 7061339.448517889Spatial Reference: 102738 (2276) Units: esriFeet Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMPDocument Info:Title: Dallas City LimitsAuthor: City of Dallas GIS ServicesComments: Provides a service with Dallas City LimitsSubject: City Limits of Dallas, TXCategory: Keywords: Dallas,base map,City LimitsAntialiasingMode: NoneTextAntialiasingMode: ForceSupports Dynamic Layers: falseMaxRecordCount: 1000MaxImageHeight: 4096MaxImageWidth: 4096Supported Query Formats: JSON, AMFMin Scale: 577792Max Scale: 0Child Resources: Info Supported Operations: Export Map Identify Find Return Updates

Sixty-seven maps from Indian Land Cessions in the United States, compiled by Charles C. Royce and published as the second part of the two-part Eighteenth Annual Report of the Bureau of American Ethnology to the Secretary of the Smithsonian Institution, 1896-1897 have been scanned, georeferenced in JPEG2000 format, and digitized to create this feature class of cession maps. The mapped cessions and reservations included in the 67 maps correspond to entries in the Schedule of Indian Land Cessions, indicating the number and location of each cession by or reservation for the Indian tribes from the organization of the Federal Government to and including 1894, together with descriptions of the tracts so ceded or reserved, the date of the treaty, law or executive order governing the same, the name of the tribe or tribes affected thereby, and historical data and references bearing thereon, as set forth in the subtitle of the Schedule. Go to this URL for full metadata: https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.TRIBALCEDEDLANDS.xml Each Royce map was georeferenced against one or more of the following USGS 1:2,000,000 National Atlas Feature Classes contained in \NatlAtlas_USGS.gdb: cities_2mm, hydro_ln_2mm, hydro_pl_2mm, plss_2mm, states_2mm. Cessions were digitized as a file geodatabase (GDB) polygon feature class, projected as NAD83 USA_Contiguous_Lambert_Conformal_Conic, which is the same projection used to georeference the maps. The feature class was later reprojected to WGS 1984 Web Mercator (auxiliary sphere) to optimize it for the Tribal Connections Map Viewer. Polygon boundaries were digitized as to not deviate from the drawn polygon edge to the extent that space could be seen between the digitized polygon and the mapped polygon at a viewable scale. Topology was maintained between coincident edges of adjacent polygons. The cession map number assigned by Royce was entered into the feature class as a field attribute. The Map Cession ID serves as the link referencing relationship classes and joining additional attribute information to 752 polygon features, to include the following: 1. Data transcribed from Royce's Schedule of Indian Land Cessions: a. Date(s), in the case of treaties, the date the treaty was signed, not the date of the proclamation; b. Tribe(s), the tribal name(s) used in the treaty and/or the Schedule; and c. Map Name(s), the name of the map(s) on which a cession number appears; 2. URLs for the corresponding entry in the Schedule of Indian Land Cessions (Internet Archive) for each unique combination of a Date and reference to a Map Cession ID (historical references in the Schedule are included); 3. URLs for the corresponding treaty text, including the treaties catalogued by Charles J. Kappler in Indian Affairs: Laws and Treaties (HathiTrust Digital Library), executive order or other federal statute (Library of Congress and University of Georgia) identified in each entry with a reference to a Map Cession ID or IDs; 4. URLs for the image of the Royce map(s) (Library of Congress) on which a given cession number appears; 5. The name(s) of the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text, as well as the name of the present-day Indian tribe or tribes; and 6. The present-day states and counties included wholly or partially within a Map Cession boundary. During the 2017-2018 revision of the attribute data, it was noted that 7 of the Cession Map IDs are missing spatial representation in the Feature Class. The missing data is associated with the following Cession Map IDs: 47 (Illinois 1), 65 (Tennessee and Bordering States), 128 (Georgia), 129 (Georgia), 130 (Georgia), 543 (Indian Territory 3), and 690 (Iowa 2), which will be updated in the future. This dataset revises and expands the dataset published in 2015 by the U.S. Forest Service and made available through the Tribal Connections viewer, the Forest Service Geodata Clearinghouse, and Data.gov. The 2018 dataset is a result of collaboration between the Department of Agriculture, U.S. Forest Service, Office of Tribal Relations (OTR); the Department of the Interior, National Park Service, National NAGPRA Program; the U.S. Environmental Protection Agency, Office of International and Tribal Affairs, American Indian Environmental Office; and Dr. Claudio Saunt of the University of Georgia. The Forest Service and Dr. Saunt independently digitized and georeferenced the Royce cession maps and developed online map viewers to display Native American land cessions and reservations. Dr. Saunt subsequently undertook additional research to link Schedule entries, treaty texts, federal statutes and executive orders to cession and reservation polygons, which he agreed to share with the U.S. Forest Service. OTR revised the data, linking the Schedule entries, treaty texts, federal statues and executive orders to all 1,172 entries in the attribute table. The 2018 dataset has incorporated data made available by the National NAGPRA Program, specifically the Indian tribe or tribes related to each mapped cession, including the name as it appeared in the Schedule or the corresponding primary text and the name of the present-day Indian tribe or tribes, as well as the present-day states and counties included wholly or partially within a Map Cession boundary. This data replaces in its entirety the National NAGPRA data included in the dataset published in 2015. The 2015 dataset incorporated data presented in state tables compiled from the Schedule of Indian Land Cessions by the National NAGPRA Program. In recent years the National NAGPRA Program has been working to ensure the accuracy of this data, including the reevaluation of the present-day Indian tribes and the provision of references for their determinations. Changes made by the OTR have not been reviewed or approved by the National NAGPRA Program. The Forest Service will continue to collaborate with other federal agencies and work to improve the accuracy of the data included in this dataset. Errors identified since the dataset was published in 2015 have been corrected, and we request that you notify us of any additional errors we may have missed or that have been introduced. Please contact Rebecca Hill, Policy Analyst, U.S. Forest Service, Office of Tribal Relations, at rebeccahill@fs.usda.gov with any questions or concerns with regard to the data included in this dataset.

Abstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. The polygons in this dataset are a digital representation of the distribution or extent of geological units within the area. Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. These have been extracted from the Rock Units Table held …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. The polygons in this dataset are a digital representation of the distribution or extent of geological units within the area. Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. These have been extracted from the Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database. Purpose To display the geology polygons which define the extent of rock units. Dataset History Supplemental_Information: Data captured at 1:40 000 scale. The data set is sourced from the Department's Geoscience and Resources Database (GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database.(GRDB), a component of the Mineral and Energy Resources Location and Information Network (MERLIN) corporate database. NOTE: GEOLDATA was in most cases compiled based on Datum AGD66. The map tile coverages so compiled have now been projected to geographics based on Datum GDA94. Consequently the boundaries for these map tiles will not conform to the Latitude and Longitude graticule based on Datum GDA94. Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: 9341_r Entity_Type_Definition: Polygons have a range of attributes including unit name, age, lithological description and an abbreviated symbol for use in labelling the polygons. Entity_Type_Definition_Source: The Rock Units Table held in the Department of Natural Resources, Mines and Energy Merlin Database. Attribute: Attribute_Label: FID Attribute_Definition: Internal feature number. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated. Beginning_Date_of_Attribute_Values: March 2004 Attribute: Attribute_Label: Shape Attribute_Definition: Feature geometry. Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Coordinates defining the features. Attribute: Attribute_Label: KEY Attribute_Definition: Unique polygon identifier and relate item for poygon attributes Attribute: Attribute_Label: ROCK_U_NAM Attribute_Definition: The Map Unit Name of the polygon. In the case of named units it comprises of the standard binomial name. Unnamed subdivisions of named units include the binomial name with a letter symbol as a suffix. Unnamed units are represented by a letter symbol, usually in combination with a map sheet number. Attribute: Attribute_Label: AGE Attribute_Definition: Geological age of unit Attribute: Attribute_Label: LITH_SUMMA Attribute_Definition: Provides a brief description of the map units as they have been described in the course of the project work, or as has appeared on relevant hard copy map legends. Attribute: Attribute_Label: ROCK_U_TYP Attribute_Definition: Provides a means of separating map units, eg for constructing a map reference. This item will contain one of the following: STRAT- Stratigraphic unit, including sedimentary, volcanic and metamorphic rock units. INTRU- Intrusive rock units; COMPST- Compound unit where the polygon includes two or more rock units, either stratigraphic, intrusive or both; COMPST- Compound unit, as above where the dominant or topmost unit is of the STRAT type; COMPIN- Compound unit, as above, where the dominant unit is of the INTRU type; WATER- Water bodies- Large dams, lakes, waterholes. Attribute: Attribute_Label: SEQUENCE_N Attribute_Definition: A numeric field to allow sorting of the rock units in approximate stratigraphic order as they would appear on a map legend. Attribute: Attribute_Label: DOMINANT_R Attribute_Definition: A simplified lithological description to allow generation of thematic maps based on broad rock types. Attribute: Attribute_Label: MAP_SYMBOL Attribute_Definition: Provides an abbreviated label for polygons. Mostly based on the letter symbols as they appear on published maps or the original hard copy compilation sheets. These are not unique across the State, but should be unique within a single map tile, and usually adjacent tiles. Attribute: Attribute_Label: NAME_100K Attribute_Definition: Name of 1:100 000 map sheet coincident with the data extent. Overview_Description: Entity_and_Attribute_Overview: Polygon Attribute information includes Polygon Key, Rock Unit Name, Age, Lithology, Rock Unit Type, Map Symbol and 1:100 000 sheet name. Dataset Citation "Queensland Department of Natural Resources, Mines and Energy" (2014) Qld 100k mapsheets - Warwick. Bioregional Assessment Source Dataset. Viewed 28 September 2017, http://data.bioregionalassessments.gov.au/dataset/3e2fa307-1f06-4873-96d3-5c3e5638894a.

Point locations of schools in Maine. Structures data contains name and location data for selected manmade facilities. These data are designed to be used in general mapping and analysis of structure related activities using a geographic information system (GIS) For mapping purposes, structures can be used with other GIS data themes to produce general reference maps as a base map dataset.

Sampling design: random whithin areas of improvement, where the WorldCereal map is performing better (less errors) than the GLAD cropland map 2019.

Number of sample sites: 500

Method of data collection: visual interpreation of various sources of information, including very high resolution images and photos.

Tool for data collection: Geo-Wiki

description: USGS Structures from The National Map (TNM) consists of data to include the name, function, location, and other core information and characteristics of selected manmade facilities. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations. Structures currently being collected are: School, College/University, Fire Station/EMS Station, Law Enforcement, Prison/Correctional Facility, State Capitol, Hospital/Medical Center, Ambulance Services, Cemetery, and Post Office. Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain structures data in either Esri File Geodatabase or Shapefile formats. For additional information on the structures data model, go to https://nationalmap.gov/structures.html.; abstract: USGS Structures from The National Map (TNM) consists of data to include the name, function, location, and other core information and characteristics of selected manmade facilities. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations. Structures currently being collected are: School, College/University, Fire Station/EMS Station, Law Enforcement, Prison/Correctional Facility, State Capitol, Hospital/Medical Center, Ambulance Services, Cemetery, and Post Office. Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain structures data in either Esri File Geodatabase or Shapefile formats. For additional information on the structures data model, go to https://nationalmap.gov/structures.html.

Use Constraints:This mapping tool is for reference and guidance purposes only and is not a binding legal document to be used for legal determinations. The data provided may contain errors, inconsistencies, or may not in all cases appropriately represent the current boundaries of PWSs in California. The data in this map are subject to change at any time and should not be used as the sole source for decision making. By using this data, the user acknowledges all limitations of the data and agrees to accept all errors stemming from its use.Description:This mapping tool provides a representation of the general PWS boundaries for water service, wholesaler and jurisdictional areas. The boundaries were created originally by collection via crowd sourcing by CDPH through the Boundary Layer Tool, this tool was retired as of June 30, 2020. State Water Resources Control Board – Division of Drinking Water is currently in the process of verifying the accuracy of these boundaries and working on a tool for maintaining the current boundaries and collecting boundaries for PWS that were not in the original dataset. Currently, the boundaries are in most cases have not been verified. Map Layers· Drinking Water System Areas – representation of the general water system boundaries maintained by the State Water Board. This layer contains polygons with associated data on the water system and boundary the shape represents.· LPA office locations – represents the locations of the Local Primacy Agency overseeing the water system in that county. Address and contact information are attributes of this dataset.· LPA office locations – represents the locations of the Local Primacy Agency overseeing the water system in that county. Address and contact information are attributes of this dataset· California Senate Districts – represents the boundaries of the senate districts in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.· California Senate Districts – represents the boundaries of the assembly districts in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.· California County – represents the boundaries of the counties in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.Informational Pop-up Box for Boundary layer· Water System No. – unique identifier for each water system· Water System Name – name of water system· Regulating Agency – agency overseeing the water system· System Type – classification of water system.· Population the approximate population served by the water system· Boundary Type – the type of water system boundary being displayed· Address Line 1 – the street or mailing address on file for the water system· Address Line 2 – additional line for street or mailing address on file for the water system, if applicable· City – city where water system located or receives mail· County – county where water system is located· Verification Status – the verification status of the water system boundary· Verified by – if the boundary is verified, the person responsible for the verification Date Created and Sources:This web app was most recently updated on July, 21, 2021. Each layer has a data created date and data source is indicated in the overview/metadata page and is valid up to the date provided.

Beach erosion is a chronic problem along most open-ocean shores of the United States. As coastal populations continue to grow, and community infrastructures are threatened by erosion, there is increased demand for accurate information regarding past and present shoreline changes. There is also need for a comprehensive analysis of shoreline movement that is regionally consistent. To meet these national needs, the USGS National Assessment of Shoreline Change Project has collected and analyzed a comprehensive database of digital vector shorelines by compiling shoreline positions from pre-existing historical shoreline databases and by generating historical and modern shoreline data. This dataset consists of long-term (100+ years) shoreline change rates. Rate calculations were computed using the Digital Shoreline Analysis System (DSAS), an ArcGIS extension developed by the U.S. Geological Survey. Long-term rates of shoreline change were calculated using a linear regression rate based on all available shoreline data. A reference baseline was used as the originating point for the orthogonal transects cast by the DSAS software. The transects intersect each shoreline establishing measurement points, which are then used to calculate long-term rates. To make these results more accessible to the public and other agencies, the USGS created this web service. This web service was created utilizing Esri ArcServer. This service meets open geospatial consortium standards. The data compilation used to derive the shoreline change rates is available in a service with the title USGS Map service: National Shoreline Change - Historic Shorelines by State. The reference baseline used to derive the shoreline change rates is available in a service with the title USGS Map service: National Shoreline Change - Offshore Baseline. The locations of the transects used in the change rate calculation are available in a service with the title USGS Map service: National Shoreline Change - Intersection Points. The geographic information system (GIS) data layers from this web service are cataloged by state for ease of access.

This dataset contains files created, digitized, or georeferenced by Chris DeRolph for mapping the pre-urban renewal community within the boundaries of the Riverfront-Willow St. and Mountain View urban renewal projects in Knoxville TN. Detailed occupant information for properties within boundaries of these two urban renewal projects was extracted from the 1953 Knoxville City Directory. The year 1953 was chosen as a representative snapshot of the Black community before urban renewal projects were implemented. The first urban renewal project to be approved was the Riverfront-Willow Street project, which was approved in 1954 according to the University of Richmond Renewing Inequality project titled ‘Family Displacements through Urban Renewal, 1950-1966’ (link below in the 'Other shapefiles' section). For ArcGIS Online users, the shapefile and tiff layers are available in AGOL and can be found by clicking the ellipsis next to the layer name and selecting 'Show item details' for the layers in this webmap https://knoxatlas.maps.arcgis.com/apps/webappviewer/index.html?id=43a66c3cfcde4f5f8e7ab13af9bbcebecityDirectory1953 is a folder that contains:JPG images of 1953 City Directory for street segments within the urban renewal project boundaries; images collected at the McClung Historical CollectionTXT files of extracted text from each image that was used to join occupant information from directory to GIS address datashp is a folder that contains the following shapefiles:Residential:Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and property ownersBlack_rented_residential_1953.shp: residential entries in the 1953 City Directory identified as Black and non-owners of the propertyNon_Black_owned_residential_1953.shp: residential entries in the 1953 City Directory identified as property owners that were not listed as BlackNon_Black_rented_residential_1953.shp: residential entries in the 1953 City Directory not listed as Black or property ownersResidential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposeslastName: occupant's last namelabelShort: combines the Number and lastName fields for map labeling purposesNon-residential:Black_nonResidential_1953.shp: non-residential entries in the 1953 City Directory listed as Black-occupiedNonBlack_nonResidential_1953.shp: non-residential entries in the 1953 City Directory not listed as Black-occupiedNon-residential shapefile attributes:cityDrctryString: full text string from 1953 City Directory entryfileName: name of TXT file that contains the information for the street segmentsOccupant: the name of the occupant listed in the City Directory, enclosed in square brackets []Number: the address number listed in the 1953 City DirectoryBlackOccpt: flag for whether the occupant was identified in the City Directory as Black, designated by the (c) or (e) character string in the cityDrctryString fieldOwnerOccpd: flag for whether the occupant was identified in the City Directory as the property owner, designated by the @ character in the cityDrctryString fieldUnit: unit if listed (e.g. Apt 1, 2d fl, b'ment, etc)streetName: street name in ~1953Lat: latitude coordinate in decimal degrees for the property locationLon: longitude coordinate in decimal degrees for the property locationNAICS6: 2022 North American Industry Classification System (NAICS) six-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS6title: NAICS6 title/short descriptionNAICS3: 2022 North American Industry Classification System (NAICS) three-digit business code, designated by Chris DeRolph rapidly and without careful considerationNAICS3title: NAICS3 title/short descriptionflag: flags whether the occupant is part of the public sector or an NGO; a flag of '0' indicates the occupant is assumed to be a privately-owned businessrace_own: combines the BlackOccpt and OwnerOccpd fieldsmapLabel: combines the Number and Occupant fields for map labeling purposesOther shapefiles:razedArea_1972.shp: approximate area that appears to have been razed during urban renewal based on visual overlay of usgsImage_grayscale_1956.tif and usgsImage_colorinfrared_1972.tif; digitized by Chris DeRolphroadNetwork_preUrbanRenewal.shp: road network present in urban renewal area before razing occurred; removed attribute indicates whether road was removed or remains today; historically removed roads were digitized by Chris DeRolph; remaining roads sourced from TDOT GIS roads dataTheBottom.shp: the approximate extent of the razed neighborhood known as The Bottom; digitized by Chris DeRolphUrbanRenewalProjects.shp: boundaries of the East Knoxville urban renewal projects, as mapped by the University of Richmond's Digital Scholarship Lab https://dsl.richmond.edu/panorama/renewal/#view=0/0/1&viz=cartogram&city=knoxvilleTN&loc=15/35.9700/-83.9080tiff is a folder that contains the following images:streetMap_1952.tif: relevant section of 1952 map 'Knoxville Tennessee and Surrounding Area'; copyright by J.U.G. Rich and East Tenn Auto Club; drawn by R.G. Austin; full map accessed at McClung Historical Collection, 601 S Gay St, Knoxville, TN 37902; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphnewsSentinelRdMap_1958.tif: urban renewal area map from 1958 Knox News Sentinel article; used as reference for street names in roadNetwork_preUrbanRenewal.shp; georeferenced by Chris DeRolphusgsImage_grayscale_1956.tif: May 18, 1956 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/ARA550590030582/usgsImage_colorinfrared_1972.tif: April 18, 1972 color infrared USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR6197002600096/usgsImage_grayscale_1976.tif: November 8, 1976 black-and-white USGS aerial photograph, georeferenced by Chris DeRolph; accessed here https://earthexplorer.usgs.gov/scene/metadata/full/5e83d8e4870f4473/AR1VDUT00390010/

Access API

Metadata Portal Metadata Information

Point locations for most current property titles issued in NZ (January 2010)

Titles from the LINZ BDE are not a spatial layer. A single point for each title has been geocoded from the relation tables to the first parcel centroid where a link exists.

Many parcels have more than one title reference, so there may be a stack of points for a title, typical in a crosslease.

There is only one point per title. Where a title spans multiple parcels, a relate would need to be built to identify all the parcels comprising a title. While this can be done for one title, it is impractical for a map. Internal parcel boundaries can be suppressed to show contiguous parcels with the same title. Parcel boundaries are coded for internal boundaries (featurecode = 'parcel_int').

A property (for rating purposes) may contain many titles, but there is no information in the titles or valuation system to display this. The valuation system does not have a complete record of titles for an assessment (amazing isn't it?). Because large properties are often in multiple titles and owners there is no information to amalgamate the parts into a single entity.

A large number (500,000) of titles cannot be automatically located because the parcel that the title refers to is no longer current and is not mapped in LandOnline. Other reasons are ambiguous appellation that prevents a reliable match so they are not linked by LINZ until they come up for a change of title, not just change of owner.

Titles can have multiple owners, so these have been added as an abbreviated list to each title. Owners can be companies or trusts.

Total number 1.78 million.

Warning: This set of titles is subject to recall if a protected title is issued in error.

Source LINZ BDE Crown Copyright Reserved

Libraries data contains name and location data for selected manmade facilities. These data are designed to be used in general mapping and analysis of structure related activities using a geographic information system (GIS) For mapping purposes, structures can be used with other GIS data themes to produce general reference maps as a base map dataset

URL: https://geoscience.data.qld.gov.au/dataset/mr009452

The QUEENSLAND 1, 2, 4 AND 12 MILE MAP INDEX Index map was published in 1897 at 50 Miles to an Inch as part of the INDEX series to administer permit and permit related spatial information. The map was maintained internally as a provisional office chart.
The map product is available to all government agencies, industry and the public for reference.
Title and Image reference number is QUEENSLAND 1, 2, 4 AND 12 MILE MAP INDEX_4745. (MR4745)

One Mile, Two Mile, Four Mile, Twelve Mile Run Maps.

URL: https://geoscience.data.qld.gov.au/dataset/mr010460

The OFFSHORE TITLES PACIFIC OCEAN SHEET 12 map was published to administer permit and permit related spatial information. The map was maintained internally as a provisional office chart.
The map product is available to all government agencies, industry and the public for reference.
Title and Image reference number is OFFSHORE TITLES PACIFIC OCEAN SHEET 12_001053. (MR10218)

Title: The reference elevation model of Antarctica (REMA) - Scale: 10000000 - Version 1,2

description: The USGS National Hydrography Dataset (NHD) service from The National Map (TNM) 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. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. For additional information on the NHD, go to https://nhd.usgs.gov/index.html. The Watershed Boundary Dataset (WBD) is a companion dataset to the NHD. It 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, will be 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 National Map 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 NHD and WBD data in either Esri File or Personal Geodatabase, or Shapefile formats.; abstract: The USGS National Hydrography Dataset (NHD) service from The National Map (TNM) 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. The NHD from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. For additional information on the NHD, go to https://nhd.usgs.gov/index.html. The Watershed Boundary Dataset (WBD) is a companion dataset to the NHD. It 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, will be 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 National Map 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 NHD and WBD data in either Esri File or Personal Geodatabase, or Shapefile formats.

description: The USGS Transportation service from The National Map (TNM) is based on TIGER/Line data provided through U.S. Census Bureau and road data from U.S. Forest Service. Some of the TIGER/Line data includes limited corrections done by USGS. Transportation data consists of roads, railroads, trails, airports, and other features associated with the transport of people or commerce. The data include the name or route designator, classification, and location. Transportation data support general mapping and geographic information system technology analysis for applications such as traffic safety, congestion mitigation, disaster planning, and emergency response. The National Map transportation data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and structures, to produce general reference base maps. The National Map Download Client allows free downloads of public domain transportation data in either Esri File Geodatabase or Shapefile formats. For additional information on the transportation data model, go to https://nationalmap.gov/transport.html.; abstract: The USGS Transportation service from The National Map (TNM) is based on TIGER/Line data provided through U.S. Census Bureau and road data from U.S. Forest Service. Some of the TIGER/Line data includes limited corrections done by USGS. Transportation data consists of roads, railroads, trails, airports, and other features associated with the transport of people or commerce. The data include the name or route designator, classification, and location. Transportation data support general mapping and geographic information system technology analysis for applications such as traffic safety, congestion mitigation, disaster planning, and emergency response. The National Map transportation data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and structures, to produce general reference base maps. The National Map Download Client allows free downloads of public domain transportation data in either Esri File Geodatabase or Shapefile formats. For additional information on the transportation data model, go to https://nationalmap.gov/transport.html.