The "Map Imager Layer - Administrative Boundaries" is a Map Image Layer of Administrative Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Administrative Boundaries Data Group contains the following layers: Populated Places (USGS)US Census Urbanized Areas and Urban Clusters (USCB)US Census Minor Civil Divisions (USCB)PLSS Townships (MnDNR, MnGeo)Counties (USCB)American Indian, Alaska Native, Native Hawaiian (AIANNH) Areas (USCB)States (USCB)Countries (MPCA)These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Administrative Boundary Dataset please see:United States Census Bureau TIGER/Line Shapefiles and TIGER/Line Files Technical Documentation: https://www.census.gov/programs-surveys/geography/technical-documentation/complete-technical-documentation/tiger-geo-line.htmlUnited States Census Bureau Census Mapping Files: https://www.census.gov/geographies/mapping-files.htmlUnited States Census Bureau TIGER/Line Shapefiles: https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html and https://www.census.gov/cgi-bin/geo/shapefiles/index.php

In order to use the Romanian color standard for soil type map legends, a dataset of ESRI ArcMap-10 files, consisting of a shapefile set (.dbf, .shp, .shx, .sbn, and .sbx files), four different .lyr files, and three different .style files (https://desktop.arcgis.com/en/arcmap/10.3/map/ : saving-layers-and-layer-packages, about-creating-new-symbols, what-are-symbols-and-styles-), have been prepared. The shapefile set is not a “real” georeferenced layer/coverage; it is designed only to handle all the instants of soil types from the standard legend.

This legend contains 67 standard items: 63 proper colors (different color hues, each of them having, generally, 2 - 4 degrees of lightness and/or chroma, four shades of grey, and white color), and four hatching patterns on white background. The “color difference DE*ab” between any two legend colors, calculated with the color perceptually-uniform model CIELAB, is greater than 10 units, thus ensuring acceptably-distinguishable colors in the legend. The 67 standard items are assigned to 60 main soils existing in Romania, four main nonsoils, and three special cases of unsurveyed land. The soils are specified in terms of the current Romanian system of soil taxonomy, SRTS-2012+, and of the international system WRB-2014.

The four different .lyr files presented here are: legend_soilcode_srts_wrb.lyr, legend_soilcode_wrb.lyr, legend_colorcode_srts_wrb.lyr, and legend_colorcode_wrb.lyr. The first two of them are built using as value field the “Soil_codes” field, and as labels (explanation texts) the “Soil_name” field (storing the soil types according to SRTS/WRB classification), respectively, the “WRB” field (the soil type according to WRB classification), while the last two .lyr files are built using as value field the “color_code” field (storing the color codes) and as labels the soil name in SRTS and WRB, respectively, in WRB classification.

In order to exemplify how the legend is displayed, two .jpg files are also presented: legend_soil_srts_wrb.jpg and legend_color_wrb.jpg. The first displays the legend (symbols and labels) according to the SRTS classification order, the second according to the WRB classification.

The three different .style files presented here are: soil_symbols.style, wrb_codes.style, and color_codes.style. They use as name the soil acronym in SRTS classification, soil acronym in WRB classification, and, respectively, the color code.

The presented file set may be used to directly implement the Romanian color standard in digital soil type map legends, or may be adjusted/modified to other specific requirements.

Notice: this is not the latest Heat Island Severity image service.This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. Heat Severity is a reclassified version of Heat Anomalies raster which is also published on this site. This data is generated from 30-meter Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2023.To explore previous versions of the data, visit the links below:Heat Severity - USA 2022Heat Severity - USA 2021Heat Severity - USA 2020Heat Severity - USA 2019Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

NOTICE TO PROVISIONAL 2023 LAND USE DATA USERS: Please note that on December 6, 2024 the Department of Water Resources (DWR) published the Provisional 2023 Statewide Crop Mapping dataset. The link for the shapefile format of the data mistakenly linked to the wrong dataset. The link was updated with the appropriate data on January 27, 2025. If you downloaded the Provisional 2023 Statewide Crop Mapping dataset in shapefile format between December 6, 2024 and January 27, we encourage you to redownload the data. The Map Service and Geodatabase formats were correct as posted on December 06, 2024.

Thank you for your interest in DWR land use datasets.

The California Department of Water Resources (DWR) has been collecting land use data throughout the state and using it to develop agricultural water use estimates for statewide and regional planning purposes, including water use projections, water use efficiency evaluations, groundwater model developments, climate change mitigation and adaptations, and water transfers. These data are essential for regional analysis and decision making, which has become increasingly important as DWR and other state agencies seek to address resource management issues, regulatory compliances, environmental impacts, ecosystem services, urban and economic development, and other issues. Increased availability of digital satellite imagery, aerial photography, and new analytical tools make remote sensing-based land use surveys possible at a field scale that is comparable to that of DWR’s historical on the ground field surveys. Current technologies allow accurate large-scale crop and land use identifications to be performed at desired time increments and make possible more frequent and comprehensive statewide land use information. Responding to this need, DWR sought expertise and support for identifying crop types and other land uses and quantifying crop acreages statewide using remotely sensed imagery and associated analytical techniques. Currently, Statewide Crop Maps are available for the Water Years 2014, 2016, 2018- 2022 and PROVISIONALLY for 2023.

Historic County Land Use Surveys spanning 1986 - 2015 may also be accessed using the CADWR Land Use Data Viewer: https://gis.water.ca.gov/app/CADWRLandUseViewer.

For Regional Land Use Surveys follow: https://data.cnra.ca.gov/dataset/region-land-use-surveys.

For County Land Use Surveys follow: https://data.cnra.ca.gov/dataset/county-land-use-surveys.

For a collection of ArcGIS Web Applications that provide information on the DWR Land Use Program and our data products in various formats, visit the DWR Land Use Gallery: https://storymaps.arcgis.com/collections/dd14ceff7d754e85ab9c7ec84fb8790a.

Recommended citation for DWR land use data: California Department of Water Resources. (Water Year for the data). Statewide Crop Mapping—California Natural Resources Agency Open Data. Retrieved “Month Day, YEAR,” from https://data.cnra.ca.gov/dataset/statewide-crop-mapping.

This dataset collection contains GIS layers for creating the AIMS eReefs visualisation maps (https://ereefs.aims.gov.au/). These datasets are useful for creating A4 printed maps of the Great Barrier Reef and the Coral Sea. It contains the following datasets:
- Countries - Australia plus surrounding countries at 1:10M scale. Crop of Natural Earth Data 1:10 Admin 0 - Countries dataset. Allows filtering out of surrounding countries.
- Cities - 21 Cities along the Queensland coastline.
- Basins - Drainage basins adjacent to the Great Barrier Reef along the eastern Queensland coastline. Derived from Geoscience Australia River Basins 1997 dataset. It is a subset and reprojection.
- Land and Basins - This layer contains both Queensland and PNG land areas, along with the river basins along the eastern Queensland coastline. This is an integrated layer that represents both the background land area and the river basins all in one layer. This layer saves having to map the land area, then overlay the river basins. In this way each polygon only needs to be rendered once. The goal of this layer is to optmise the rendering time of the eReefs base map. This dataset is made up from the Geoscience Australia Australia's River Basins 1997 dataset for the Queensland coastline and the eastern Queensland basins. PNG is copied from Natural Earth Data 10 m countries dataset.
- Rivers - Rivers that drain along the Queensland eastern coast. This is a subset of the Geoscience Australia Geodata Topo 1:5M 2004.
- Reefs - Boundaries of reefs in GBR, Torres Strait and Coral Sea. In the Coral Sea it contains the atoll platform boundaries rather than the individual reefs. This is derived from the GBRMPA GBR features dataset, AIMS Torres Strait features dataset and the AIMS Coral Sea features dataset. These were combined and simplified to a scale of 1:1M. Note that this simplification resulted in multiple neighbouring reefs being grouped together. This dataset is intended for visual rendering of maps.
- Clip regions - Polygons for clipping eReefs data to the GBR. Also contains approximate polygons for Coral Sea, Torres Strait, PNG and New Caledonia. This was created principally for setting the region attribute for the Reefs dataset, but was made available as it is useful for clipping eReefs data to the GBR for plotting purposes.

Methods:
Most of the base map layers are derived from a variety of data sources. The full workflow used to transform these source datasets is documented on GitHub (https://github.com/eatlas/GBR_AIMS_eReefs-basemap).

Limitations of the data:
The datasets in this collection have been cropped and simplified for the purposes of creating low detail printed maps of the GBR. They are not intended for creating a high resolution base map.

Format of the data:
Shapefile and GeoJSON files. The Cities dataset is provided as a CSV file.

Location of the data:
This dataset is filed in the eAtlas enduring data repository at: data\custodian\2018-2024-eReefs\GBR_AIMS_eReefs-basemap

Abstract

This dataset was created within the Bioregional Assessment Programme for cartographic purposes. Data has not been derived from any source datasets. Metadata has been compiled by the Bioregional Assessment Programme.

The dataset was created by the Bioregional Assessment Programme for use in cartographic outputs in Gippsland Basin bioregion product 1.1.7. The processes undertaken to produce this dataset are described in the History field in this metadata statement.

This layer has been superseded by Cartographic masks for map products GIP 120 v02

Purpose

Cartographic masks for map products GIP_120, used for clear annotation and masking unwanted features from report maps.

Dataset History

A shapefile was created for the use of masking data to highlight text.

Method:

\* A new polygon shapefile was created with no content

\* The shapefile was then populated in an ArcMap editing session by digitizing polygons which surround text.

\* ArcMAP's Advanced Drawing Option was then used to mask data behind text.

Dataset Citation

Bioregional Assessment Programme (2014) Cartographic masks for map products GIP 120. Bioregional Assessment Source Dataset. Viewed 05 October 2018, http://data.bioregionalassessments.gov.au/dataset/0abc7b84-84be-4d50-9e1f-433747534646.

Parcels and property data maintained and provided by Lee County Property Appraiser. This dataset includes condominium units. Property attribute data joined to parcel GIS layer by Lee County Government GIS.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue property classification code


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 LEGAL
 String
 255
 Full Legal Description (On Deed)


 GARBDIST
 String
 3
 County Garbage Hauling Area


 GARBTYPE
 String
 1
 County Garbage Pick-up Type


 GARBCOMCAT
 String
 1
 County Garbage Commercial Category


 GARBHEADER
 String
 1
 Garbage Header Code


 GARBUNITS
 Double
 8
 Number of Garbage Units


 CREATEYEAR

This feature class (shapefile) consists of point locations of public, private, and charter schools including pre-schools, day care facilities, adult and vocational schools in New Jersey, with minimal attributes. Most of the public schools were initially located in 2003 by the New Jersey Department of Environmental Protection, and were checked in 2007-2016 by the NJ Office of Geographic Information Systems (OGIS), other organizations and volunteers. Charter schools were located in 2011 and checked through 2016 by OGIS against the 2016 NJ Department of Education table of public schools that also lists charter schools.Private schools were located initially in 2010, and updated later in 2014 only for Somerset County using the spatial data provided by Somerset County GIS team. The present data set is the result of checking and updating the previous locations by processing the tabular data that were acquired from NJDOE in August, 2016.

© Most of the public school records were derived from 2003 data sets created by the New Jersey Department of Environmental Protection. Special acknowledgements are to people of the following organizations who made a significant contribution to school location verification process: Seth Hackman (NJDEP), Salem county GIS; Morris County GIS; Atlantic County GIS; Cape May County GIS; DVRPC; Hunterdon County GIS; Somerset County GIS; Warren County Prosecutor's Office; Westfield Engineering; WFS (for Mercer, Middlesex, Burlington and Camden Co.) ; Monmouth GIS; voluneers and state employees who made site visits on their own time: Charles Colvard, Dominic Juliano, Matt Lawson, Richard Rabinowitz, Amy J. Ferdinand, Rebecca French-Mesch.

This layer is a component of Sites and Facilities.

Building structures include parking garages, ruins, monuments, and buildings under construction along with residential, commercial, industrial, apartment, townhouses, duplexes, etc. Buildings equal to or larger than 9.29 square meters (100 square feet) are captured. Buildings are delineated around the roof line showing the building "footprint." Roof breaks and rooflines, such as between individual residences in row houses or separate spaces in office structures, are captured to partition building footprints. This includes capturing all sheds, garages, or other non-addressable buildings over 100 square feet throughout the city. Atriums, courtyards, and other “holes” in buildings created as part of demarcating the building outline are not part of the building capture. This includes construction trailers greater than 100 square feet. Memorials are delineated around a roof line showing the building "footprint."Bleachers are delineated around the base of connected sets of bleachers. Parking Garages are delineated at the perimeter of the parking garage including ramps. Parking garages sharing a common boundary with linear features must have the common segment captured once. A parking garage is only attributed as such if there is rooftop parking. Not all rooftop parking is a parking garage, however. There are structures that only have rooftop parking but serve as a business. Those are captured as buildings. Fountains are delineated around the base of fountain structures.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606

Abstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are 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 cartographic mask polygon shapefiles for maps created in COO product 1.5. These polygons are used for clear annotation and to mask-out unwanted features in report maps. ## Purpose For cartographic use only ## Dataset History Polygon mask features were created using the 'Features Outline Masks (Cartography)' tool (ArcMap) on annotation layers in maps for product CLM 1.2. For this dataset, masks were created from the annotations created from the following layer (dataset): 1. PopulatedPlaces Feature Class from the "GEODATA TOPO 250K Series 3" dataset (GUID: a0650f18-518a-4b99-a553-44f82f28bb5f). Masks polygons were also created for clear visualisation of graticules and state annotation graphics in the same maps. ## Dataset Citation Bioregional Assessment Programme (XXXX) Cartographic masks for map products COO 150. Bioregional Assessment Derived Dataset. Viewed 11 April 2016, http://data.bioregionalassessments.gov.au/dataset/43131c46-d0d8-44de-a272-9487c1cd5f2b. ## Dataset Ancestors * Derived From GEODATA TOPO 250K Series 3

This provides a polygon coastline and islands layer which is based on the Topo50 products. It is a combination of the following layers:

• NZ Coastlines (Topo 1:50k)
• NZ Island Polygons (Topo 1:50k)
• NZ Auckland Is Island Polygons (Topo, 1:50k)
• NZ Campbell Is / Motu Ihupuku Island Polygons (Topo, 1:50k)
• NZ Antipodes Is Island Polygons (Topo, 1:25k)
• NZ Kermadec Is Island Polygons (Topo, 1:25k)
• NZ Bounty Is Island Polygons (Topo, 1:25k)
• NZ Snares Is / Tini Heke Island Polygons (Topo, 1:25k)
• NZ Chatham Is island polygons (Topo, 1:50k)

This topographic coastline is the line forming the boundary between the land and sea, defined by mean high water.

Islands from the NZ Island Polygons layer that lie within the NZ Coastline and Chatham Islands areas (i.e. islands in lakes, rivers and estuaries) have been removed.

The GIS workflow to create the layer is:

1. NZ Coastlines were converted from a polyline to a polygon using a polyline to polygon tool.
2. The resulting coastal polygon was then used as an input into an erase tool and run against the NZ Island Polygon layer to remove all islands lying within the NZ Mainland and Stewart Island.
3. This was then merged with the NZ Chatham Is island polygons (Topo, 1:50k) that have had the islands within the main island polygon removed, NZ Auckland Is Island Polygons (Topo, 1:50k), NZ Campbell Is / Motu Ihupuku Island, NZ Antipodes Is Island Polygons (Topo, 1:25k), NZ Kermadec Is Island Polygons (Topo, 1:25k), NZ Bounty Is Island Polygons (Topo, 1:25k) and NZ Snares Is / Tini Heke Island Polygons (Topo, 1:25k) layers using a merge tool.

For more detailed description of each layer refer to the layer urls above.

APIs and web services This dataset is available via ArcGIS Online and ArcGIS REST services, as well as our standard APIs. LDS APIs and OGC web services ArcGIS Online map services ArcGIS REST API

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. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

Note: This is a large dataset. To download, go to ArcGIS Open Data Set and click the download button, and under additional resources select the shapefile or geodatabase option. The Knutson-Vandenberg Act (K-V) of June 9, 1930 (16 U.S.C. 576-576b; 46 Stat. 527), as amended by the National Forest Management Act of October 22, 1976 (16 U.S.C. 1600 et seq.) authorized collection of deposits from federal timber purchasers for prompt and efficient use of funds to reestablish, protect, and improve the production of renewable resources on timber sale areas. This includes performing soil improvement and watershed restoration, wildlife habitat improvement, control of insects, disease, and noxious weeds, tree planting, seeding and other cultural treatments necessary to maintain and improve land productivity. Since its creation millions of acres of National Forest System lands (NFS) have been treated and restored to resilient conditions and terrestrial and aquatic habitat improved. Public Law 109-54 of August 2, 2005, Title IV General Provisions, Sec 412 further amended the K-V Act to allow the collection and use of CWKV funds for watershed restoration, wildlife habitat improvement, to prepare timber sales, control of insects, disease, and noxious weeds, fire community protection activities, and the maintenance of forest roads within the Forest Service region in which the timber sale occurred. Provided that such activities may be performed through the use of contracts, forest product sales, and cooperative agreements. Note that these activities are to be performed by contract and not Forest Service personnel. The Forest Service used this amendment to administratively create two K-V programs within the K-V fund; CWKV (Cooperative Work, Knutson-Vandenberg, Sale Area Projects) and CWK2 (Cooperative Work, Knutson-Vandenberg, Regional Projects). This layer shows the spatial representation where activities accomplished and funded with CWKV and CWK2 funds and reported through the Forest Service Activity Tracking System (FACTS) database. It is important to note that this layer may not contain all CWKV or CWK2 accomplished activities; the spatial portion of the activity description is not currently enforced by FACTS and at this time some are optionally reported by Forest Service units. As spatial data reporting is enforced by the application and acceptant of reporting both tabular and spatial we hope to improve the quality and comprehensiveness of the data used for this layer in coming years. Metadata

The seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. This layer is a partial view of the Information Sales System (ISS) extract, a report of property characteristics taken from the County’s Megabyte Property Tax System (MPTS). This layer may be missing some attributes (e.g., Owner Name) which may not be published to the Internet due to privacy conditions under the California Public Records Act (CPRA). Please contact the Clerk-Recorder-Assessor (CRA) office at (707) 565-1888 for information on availability, associated fees, and access to other versions of Sonoma County parcels containing additional property characteristics.The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.

This dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

© MarineCadastre.gov This layer is a component of BOEMRE Layers.

This Map Service contains many of the primary data types created by both the Bureau of Ocean Energy Management (BOEM) and the Bureau of Safety and Environmental Enforcement (BSEE) within the Department of Interior (DOI) for the purpose of managing offshore federal real estate leases for oil, gas, minerals, renewable energy, sand and gravel. These data layers are being made available as REST mapping services for the purpose of web viewing and map overlay viewing in GIS systems. Due to re-projection issues which occur when converting multiple UTM zone data to a single national or regional projected space, and line type changes that occur when converting from UTM to geographic projections, these data layers should not be used for official or legal purposes. Only the original data found within BOEM/BSEE’s official internal database, federal register notices or official paper or pdf map products may be considered as the official information or mapping products used by BOEM or BSEE. A variety of data layers are represented within this REST service are described further below. These and other cadastre information the BOEM and BSEE produces are generated in accordance with 30 Code of Federal Regulations (CFR) 256.8 to support Federal land ownership and mineral resource management.

For more information – Contact: Branch Chief, Mapping and Boundary Branch, BOEM, 381 Elden Street, Herndon, VA 20170. Telephone (703) 787-1312; Email: mapping.boundary.branch@boem.gov

The REST services for National Level Data can be found here: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE/MMC_Layers/MapServer

REST services for regional level data can be found by clicking on the region of interest from the following URL: http://gis.boemre.gov/arcgis/rest/services/BOEM_BSEE

Individual Regional Data or in depth metadata for download can be obtained in ESRI Shape file format by clicking on the region of interest from the following URL: http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx

Currently the following layers are available from this REST location:

OCS Drilling Platforms -Locations of structures at and beneath the water surface used for the purpose of exploration and resource extraction. Only platforms in federal Outer Continental Shelf (OCS) waters are included. A database of platforms and rigs is maintained by BSEE.

OCS Oil and Natural Gas Wells -Existing wells drilled for exploration or extraction of oil and/or gas products. Additional information includes the lease number, well name, spud date, the well class, surface area/block number, and statistics on well status summary. Only wells found in federal Outer Continental Shelf (OCS) waters are included. Wells information is updated daily. Additional files are available on well completions and well tests. A database of wells is maintained by BSEE.

OCS Oil & Gas Pipelines -This dataset is a compilation of available oil and gas pipeline data and is maintained by BSEE. Pipelines are used to transport and monitor oil and/or gas from wells within the outer continental shelf (OCS) to resource collection locations. Currently, pipelines managed by BSEE are found in Gulf of Mexico and southern California waters.

Unofficial State Lateral Boundaries - The approximate location of the boundary between two states seaward of the coastline and terminating at the Submerged Lands Act Boundary. Because most State boundary locations have not been officially described beyond the coast, are disputed between states or in some cases the coastal land boundary description is not available, these lines serve as an approximation that was used to determine a starting point for creation of BOEM’s OCS Administrative Boundaries. GIS files are not available for this layer due to its unofficial status.

BOEM OCS Administrative Boundaries - Outer Continental Shelf (OCS) Administrative Boundaries Extending from the Submerged Lands Act Boundary seaward to the Limit of the United States OCS (The U.S. 200 nautical mile Limit, or other marine boundary)For additional details please see the January 3, 2006 Federal Register Notice.

BOEM Limit of OCSLA ‘8(g)’ zone - The Outer Continental Shelf Lands Act '8(g) Zone' lies between the Submerged Lands Act (SLA) boundary line and a line projected 3 nautical miles seaward of the SLA boundary line. Within this zone, oil and gas revenues are shared with the coastal state(s). The official version of the ‘8(g)’ Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction described below.

Submerged Lands Act Boundary - The SLA boundary defines the seaward limit of a state's submerged lands and the landward boundary of federally managed OCS lands. The official version of the SLA Boundaries can only be found on the BOEM Official Protraction Diagrams (OPDs) or Supplemental Official Protraction Diagrams described below.

Atlantic Wildlife Survey Tracklines(2005-2012) - These data depict tracklines of wildlife surveys conducted in the Mid-Atlantic region since 2005. The tracklines are comprised of aerial and shipboard surveys. These data are intended to be used as a working compendium to inform the diverse number of groups that conduct surveys in the Mid-Atlantic region.The tracklines as depicted in this dataset have been derived from source tracklines and transects. The tracklines have been simplified (modified from their original form) due to the large size of the Mid-Atlantic region and the limited ability to map all areas simultaneously.The tracklines are to be used as a general reference and should not be considered definitive or authoritative. This data can be downloaded from http://www.boem.gov/uploadedFiles/BOEM/Renewable_Energy_Program/Mapping_and_Data/ATL_WILDLIFE_SURVEYS.zip

BOEM OCS Protraction Diagrams & Leasing Maps - This data set contains a national scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). It is updated as needed. OPDs and LMs are mapping products produced and used by the BOEM to delimit areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered for leasing offshore waters. This dataset shows only the outline of the maps that are available from BOEM.Only the most recently published paper or pdf versions of the OPDs or LMs should be used for official or legal purposes. The pdf maps can be found by going to the following link and selecting the appropriate region of interest. http://www.boem.gov/Oil-and-Gas-Energy-Program/Mapping-and-Data/Index.aspx Both OPDs and LMs are further subdivided into individual Outer Continental Shelf(OCS) blocks which are available as a separate layer. Some OCS blocks that also contain other boundary information are known as Supplemental Official Block Diagrams (SOBDs.) Further information on the historic development of OPD's can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf: http://www.boemre.gov/itd/pubs/1999/99-0006.PDF Also see the metadata for each of the individual GIS data layers available for download. The Official Protraction Diagrams (OPDs) and Supplemental Official Block Diagrams (SOBDs), serve as the legal definition for BOEM offshore boundary coordinates and area descriptions.

BOEM OCS Lease Blocks - Outer Continental Shelf (OCS) lease blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) for leasing and administrative purposes. OCS blocks relate back to individual Official Protraction Diagrams and are not uniquely numbered. Only the most recently published paper or pdf

Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

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.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

This feature service is derived from the Esri "United States Zip Code Boundaries" layer, queried to only CA data.For the original data see: https://esri.maps.arcgis.com/home/item.html?id=5f31109b46d541da86119bd4cf213848Published by the California Department of Technology Geographic Information Services Team.The GIS Team can be reached at ODSdataservices@state.ca.gov.U.S. ZIP Code Boundaries represents five-digit ZIP Code areas used by the U.S. Postal Service to deliver mail more effectively. The first digit of a five-digit ZIP Code divides the United States into 10 large groups of states (or equivalent areas) numbered from 0 in the Northeast to 9 in the far West. Within these areas, each state is divided into an average of 10 smaller geographical areas, identified by the second and third digits. These digits, in conjunction with the first digit, represent a Sectional Center Facility (SCF) or a mail processing facility area. The fourth and fifth digits identify a post office, station, branch or local delivery area.As of the time this layer was published, in January 2025, Esri's boundaries are sourced from TomTom (June 2024) and the 2023 population estimates are from Esri Demographics. Esri updates its layer annually and those changes will immediately be reflected in this layer. Note that, because this layer passes through Esri's data, if you want to know the true date of the underlying data, click through to Esri's original source data and look at their metadata for more information on updates.Cautions about using Zip Code boundary dataZip code boundaries have three characteristics you should be aware of before using them:Zip code boundaries change, in ways small and large - these are not a stable analysis unit. Data you received keyed to zip codes may have used an earlier and very different boundary for your zip codes of interest.Historically, the United States Postal Service has not published zip code boundaries, and instead, boundary datasets are compiled by third party vendors from address data. That means that the boundary data are not authoritative, and any data you have keyed to zip codes may use a different, vendor-specific method for generating boundaries from the data here.Zip codes are designed to optimize mail delivery, not social, environmental, or demographic characteristics. Analysis using zip codes is subject to create issues with the Modifiable Areal Unit Problem that will bias any results because your units of analysis aren't designed for the data being studied.As of early 2025, USPS appears to be in the process of releasing boundaries, which will at least provide an authoritative source, but because of the other factors above, we do not recommend these boundaries for many use cases. If you are using these for anything other than mailing purposes, we recommend reconsideration. We provide the boundaries as a convenience, knowing people are looking for them, in order to ensure that up-to-date boundaries are available.