Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.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. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 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

King County GIS data is at: https://gis-kingcounty.opendata.arcgis.com/ (new KCGIS Open Data site) OR http://www5.kingcounty.gov/gisdataportal/ (legacy KCGIS data FTP download portal)

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

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.

DNRGPS is an update to the popular DNRGarmin application. DNRGPS and its predecessor were built to transfer data between Garmin handheld GPS receivers and GIS software.

DNRGPS was released as Open Source software with the intention that the GPS user community will become stewards of the application, initiating future modifications and enhancements.

DNRGPS does not require installation. Simply run the application .exe

See the DNRGPS application documentation for more details.

Compatible with: Windows (XP, 7, 8, 10, and 11), ArcGIS shapefiles and file geodatabases, Google Earth, most hand-held Garmin GPSs, and other NMEA output GPSs

Limited Compatibility: Interactions with ArcMap layer files and ArcMap graphics are no longer supported. Instead use shapefile or geodatabase.

Prerequisite: .NET 4 Framework

DNR Data and Software License Agreement

Subscribe to the DNRGPS announcement list to be notified of upgrades or updates.

ArcGIS is a platform, and the platform is extending to the web. ArcGIS Online offers shared content, and has become a living atlas of the world. Ready-to-use curated content is published by Esri, Partners, and Users, and Esri is getting the ball rolling by offering authoritative data layers and tools.Specifically for Natural Resources data, Esri is offering foundational data useful for biogeographic analysis, natural resource management, land use planning and conservation. Some of the layers available are Land Cover, Wilderness Areas, Soils Range Production, Soils Frost Free Days, Watershed Delineation, Slope. The layers are available as Image Services that are analysis-ready and Geoprocessing Services that extract data for download and perform analysis.We've made large strides with online analysis. The latest release of ArcGIS Online's map viewer allows you to perform analysis on ArcGIS Online. Some of the currently available analysis tools are Find Hot Spots, Create Buffers, Summarize Within, Summarize Nearby. In addition, we've created Ready-to-use Esri hosted analysis tools that run on Esri hosted data. These are in Beta, and they include Watershed Delineation, Viewshed, Profile, and Summarize Elevation.

Last Updated October 29, 2024WALK IN ACCESS PROGRAM - LATEThe fields depicted are intended for general reference and do not necessarily depict property boundaries. Field conditions can change often. Hunters should pay attention to the signs posted in the field. They are the deciding factor that determines access as enrolled properties. If a field is posted with a closed sign, there is no hunting allowed in that field, despite what the data depicts.Information depicted hereon is for reference purposes only and is compiled from best available sources. Reasonable efforts have been made to ensure the accuracy of this data. Colorado Parks and Wildlife expressly disclaims responsibility for damages or liability that may arise from the use of this data.Colorado Parks and Wildlife Public GIS Data Update ScheduleAdministrative Boundary GIS Data1) First Week in February – to match any changes in Sheep, Goat, or Big Game GMU boundaries published in the Big Game Brochure.2) First Week in March – to update changes in administrative boundaries Regions, Areas, and Districts.3) First Week in August – to update Public Access Properties at the beginning of Big Game hunting seasons.4) First Week in September – to update Walk In Access program property boundaries.5) First Week in November – to update Walk In Access program property boundaries (late season).Wildlife Species GIS Data1) Mid December – at the completion of regional species activity mapping updates

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

File Geodatabase - Click hereShapefile - Click hereThis dataset contains current parcel boundaries and related attributes for approximately 2.4 million parcels maintained by the Los Angeles County Assessor (updated monthly on the second of every month). Due to the size of the data, it is only available for download as a zipped file geodatabase or shapefile at this time. For additional annual assessment roll history and attribute metadata descriptions, please visit the L.A. County Open Data Portal and search for Assessor. To better understand individual data elements, or to interactively view individual parcel information, please visit the Assessor’s Portal. A public-facing parcel map cache can be accessed here (updated weekly): https://public.gis.lacounty.gov/public/rest/services/LACounty_Cache/LACounty_Parcel/MapServer/0All inquiries should be directed to the Mapping & GIS Services Section, LA County Office of the Assessor at gisinfo@assessor.lacounty.gov

The Minnesota DNR Toolbox and Hydro Tools provide a number of convenience geoprocessing tools used regularly by MNDNR staff. Many of these may be useful to the wider public. However, some tools may rely on data that is not available outside of the DNR. All tools require at least ArcGIS 10+.

If you create a GDRS using GDRS Manager and include this toolbox resource and MNDNR Quick Layers, the DNR toolboxes will automatically be added to the ArcToolbox window whenever Quick Layers GDRS Location is set to the GDRS location that has the toolboxes.

Toolsets included in MNDNR Tools V10:
- Analysis Tools
- Conversion Tools
- Division Tools
- General Tools
- Hydrology Tools
- LiDAR and DEM Tools
- Raster Tools
- Sampling Tools

These toolboxes are provided free of charge and are not warrantied for any specific use. We do not provide support or assistance in downloading or using these tools. We do, however, strive to produce high-quality tools and appreciate comments you have about them.

ArcGIS and QGIS map packages, with ESRI shapefiles for the DSM2 Model Grid. These are not finalized products. Locations in these shapefiles are approximate.

Monitoring Stations - shapefile with approximate locations of monitoring stations.

DSM2 Grid 2025-05-28 Historical

FC_2023.01

DSM2 v8.2.0, calibrated version:

• dsm2_8_2_grid_map_calibrated.mpkx - ArcGIS Pro map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_grid_map_calibrated.mpk - ArcGIS Desktop map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_0_calibrated_grid_map_qgis.zip - QGIS map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_0_calibrated_gridmap_shapefiles.zip - A zip file containing all the shapefiles used in the above map packages:
• dsm2_8_2_0_calibrated_channels_centerlines - channel centerlines, follwing the path of CSDP centerlines
• dsm2_8_2_0_calibrated_network_channels - channels represented by straight line segments which are connected the upstream and downstream nodes
• dsm2_8_2_0_calibrated_nodes - DSM2 nodes
• dsm2_8_2_0_calibrated_dcd_only_nodes - Nodes that are only used by DCD
• dsm2_8_2_0_calibrated_and_dcd_nodes - Nodes that are shared by DSM2 and DCD
• dsm2_8_2_0_calibrated_and_smcd_nodes - Nodes that are shared by DSM2 and SMCD
• dsm2_8_2_0_calibrated_gates_actual_loc - The approximate actual locations of each gate in DSM2
• dsm2_8_2_0_calibrated_gates_grid_loc - The locations of each gate in the DSM2 model grid
• dsm2_8_2_0_calibrated_reservoirs - The approximate locations of the reservoirs in DSM2
• dsm2_8_2_0_calibrated_reservoir_connections - Lines showing connections from reservoirs to nodes in DSM2

DSM2 v8.2.1, historical version:

• DSM2 v8.2.1, historical version grid map release notes (PDF), updated 7/12/2022
• DSM2 v8.2.1, historical version grid map, single zoom level (PDF)
• DSM2 v8.2.1, historical version grid map, multiple zoom levels (PDF) - PDF grid map designed to be printed on 3 foot wide plotter paper.
• DSM2 v8.2.1, historical version map package for ArcGIS Desktop: A map package for ArcGIS Desktop containing the grid map layers with symbology.
• DSM2 v8.2.1, historical version grid map shapefiles (zip): A zip file containing the shapefiles used in the grid map.

Change Log

7/12/2022: The document "DSM2 v8.2.1, historical version grid map release notes (PDF)" was corrected by removing section 4.4, which incorrectly stated that the grid included channels 710-714, representing the Toe Drain, and that the Yolo Flyway restoration area was included.

This data set consists of a detailed digital map of individual irrigated fields and a summary of the irrigated acreage for the 2017 growing season developed for Okeechobee County, Florida. Selected attribute data that include crop type, irrigation system, and primary water source were collected for each irrigated field.

Please note this dataset is the most recent version of the Administrative Boundaries (AB). For previous versions of the AB please go to this url: https://data.gov.au/dataset/ds-dga-b4ad5702-ea2b-4f04-833c-d0229bfd689e/details?q=previous

Geoscape Administrative Boundaries is Australia’s most comprehensive national collection of boundaries, including government, statistical and electoral boundaries. It is built and maintained by Geoscape Australia using authoritative government data. Further information about contributors to Administrative Boundaries is available here.

This dataset comprises seven Geoscape products:

• Localities
• Local Government Areas (LGAs)
• Wards
• Australian Bureau of Statistics (ABS) Boundaries
• Electoral Boundaries
• State Boundaries and
• Town Points

Updated versions of Administrative Boundaries are published on a quarterly basis.

Users have the option to download datasets with feature coordinates referencing either GDA94 or GDA2020 datums.

Notable changes in the May 2025 release

• Victorian Wards have seen almost half of the dataset change now reflecting the boundaries from the 2024 subdivision review. https://www.vec.vic.gov.au/electoral-boundaries/council-reviews/ subdivision-reviews.

  • There have been spatial changes (area) greater than 1 km2 to 66 wards in Victoria.

• One new locality ‘Kenwick Island’ has been added to the local Government area ‘Mackay Regional’ in Queensland.

  • There have been spatial changes(area) greater than 1 km2 to the local government areas 'Burke Shire' and 'Mount Isa City' in Queensland.

• There have been spatial changes(area) greater than 1 km2 to the localities ‘Nicholson’, ‘Lawn Hill’ and ‘Coral Sea’ in Queensland and ‘Calguna’, ‘Israelite Bay’ and ‘Balladonia’ in Western Australia.

• An update to the NT Commonwealth Electoral Boundaries has been applied to reflect the redistribution of the boundaries gazetted on 4 March 2025.

• Geoscape has become aware that the DATE_CREATED and DATE_RETIRED attributes in the commonwealth_electoral_polygon MapInfo TAB tables were incorrectly ordered and did not match the product data model. These attributes have been re-ordered to match the data model for the May 2025 release.

IMPORTANT NOTE: correction of issues with the 22 November 2022 release

• On 28 November 2022, the Administrative Boundaries dataset originally released on 22 November 2022 was amended and re-uploaded after Geoscape identified some issues with the original data for 'Electoral Boundaries'.
• As a result of the error, some shapefiles were published in 3D rather than 2D, which may affect some users when importing data into GIS applications.
• The error affected the Electoral Boundaries dataset, specifically the Commonwealth boundary data for Victoria and Western Australia, including 'All States'.
• Only the ESRI Shapefile formats were affected (both GDA94 and GDA2020). The MapInfo TAB format was not affected.
• Because the datasets are zipped into a single file, once the error was fixed by Geoscape all of Administrative Boundaries shapefiles had to be re-uploaded, rather than only the affected files.
• If you downloaded either of the two Administrative Boundary ESRI Shapefiles between 22 November and 28 November 2022 and plan to use the Electoral Boundary component, you are advised to download the revised version dated 28 November 2022. Apologies for any inconvenience.

Further information on Administrative Boundaries, including FAQs on the data, is available here or through Geoscape Australia’s network of partners. They provide a range of commercial products based on Administrative Boundaries, including software solutions, consultancy and support.

Note: On 1 October 2020, PSMA Australia Limited began trading as Geoscape Australia.

The Australian Government has negotiated the release of Administrative Boundaries to the whole economy under an open CCBY 4.0 licence.

Users must only use the data in ways that are consistent with the Australian Privacy Principles issued under the Privacy Act 1988 (Cth).

Users must also note the following attribution requirements:

Preferred attribution for the Licensed Material:

Administrative Boundaries © Geoscape Australia licensed by the Commonwealth of Australia under Creative Commons Attribution 4.0 International license (CC BY 4.0).

Preferred attribution for Adapted Material:

Incorporates or developed using Administrative Boundaries © Geoscape Australia licensed by the Commonwealth of Australia under Creative Commons Attribution 4.0 International licence (CC BY 4.0).

What to Expect When You Download Administrative Boundaries

Administrative Boundaries is large dataset (around 1.5GB unpacked), made up of seven themes each containing multiple layers.

Users are advised to read the technical documentation including the product change notices and the individual product descriptions before downloading and using the product.

Please note this dataset is the most recent version of the Administrative Boundaries (AB). For previous versions of the AB please go to this url: https://data.gov.au/dataset/ds-dga-b4ad5702-ea2b-4f04-833c-d0229bfd689e/details?q=previous

License Information

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

Forest Preserve District of Cook County boundaries. To view or use these shapefiles, compression software and special GIS software, such as ESRI ArcGIS, is required.

[Metadata] Description: C&C of Honolulu Land Use Zoning Designations as of September 2023.

Crowther_Nature_Files.zip This description pertains to the original download. Details on revised (newer) versions of the datasets are listed below. When more than one version of a file exists in Figshare, the original DOI will take users to the latest version, though each version technically has its own DOI. -- Two global maps (raster files) of tree density. These maps highlight how the number of trees varies across the world. One map was generated using biome-level models of tree density, and applied at the biome scale. The other map was generated using ecoregion-level models of tree density, and applied at the ecoregion scale. For this reason, transitions between biomes or between ecoregions may be unrealistically harsh, but large-scale estimates are robust (see Crowther et al 2015 and Glick et al 2016). At the outset, this study was intended to generate reliable estimates at broad spatial scales, which inherently comes at the cost of fine-scale precision. For this reason, country-scale (or larger) estimates are generally more robust than individual pixel-level estimates. Additionally, due to data limitations, estimates for Mangroves and Tropical coniferous forest (as identified by WWF and TNC) were generated using models constructed from Topical moist broadleaf forest data and Temperate coniferous forest data, respectively. Because we used ecological analogy, the estimates for these two biomes should be considered less reliable than those of other biomes . These two maps initially appeared in Crowther et al (2015), with the biome map being featured more prominently. Explicit publication of the data is associated with Glick et al (2016). As they are produced, updated versions of these datasets, as well as alternative formats, will be made available under Additional Versions (see below).

Methods: We collected over 420,000 ground-sources estimates of tree density from around the world. We then constructed linear regression models using vegetative, climatic, topographic, and anthropogenic variables to produce forest tree density estimates for all locations globally. All modeling was done in R. Mapping was done using R and ArcGIS 10.1.

Viewing Instructions: Load the files into an appropriate geographic information system (GIS). For the original download (ArcGIS geodatabase files), load the files into ArcGIS to view or export the data to other formats. Because these datasets are large and have a unique coordinate system that is not read by many GIS, we suggest loading them into an ArcGIS dataframe whose coordinate system matches that of the data (see File Format). For GeoTiff files (see Additional Versions), load them into any compatible GIS or image management program.

Comments: The original download provides a zipped folder that contains (1) an ArcGIS File Geodatabase (.gdb) containing one raster file for each of the two global models of tree density – one based on biomes and one based on ecoregions; (2) a layer file (.lyr) for each of the global models with the symbology used for each respective model in Crowther et al (2015); and an ArcGIS Map Document (.mxd) that contains the layers and symbology for each map in the paper. The data is delivered in the Goode homolosine interrupted projected coordinate system that was used to compute biome, ecoregion, and global estimates of the number and density of trees presented in Crowther et al (2015). To obtain maps like those presented in the official publication, raster files will need to be reprojected to the Eckert III projected coordinate system. Details on subsequent revisions and alternative file formats are list below under Additional Versions.----------

Additional Versions: Crowther_Nature_Files_Revision_01.zip contains tree density predictions for small islands that are not included in the data available in the original dataset. These predictions were not taken into consideration in production of maps and figures presented in Crowther et al (2015), with the exception of the values presented in Supplemental Table 2. The file structure follows that of the original data and includes both biome- and ecoregion-level models.

Crowther_Nature_Files_Revision_01_WGS84_GeoTiff.zip contains Revision_01 of the biome-level model, but stored in WGS84 and GeoTiff format. This file was produced by reprojecting the original Goode homolosine files to WGS84 using nearest neighbor resampling in ArcMap. All areal computations presented in the manuscript were computed using the Goode homolosine projection. This means that comparable computations made with projected versions of this WGS84 data are likely to differ (substantially at greater latitudes) as a product of the resampling. Included in this .zip file are the primary .tif and its visualization support files.

References:

Crowther, T. W., Glick, H. B., Covey, K. R., Bettigole, C., Maynard, D. S., Thomas, S. M., Smith, J. R., Hintler, G., Duguid, M. C., Amatulli, G., Tuanmu, M. N., Jetz, W., Salas, C., Stam, C., Piotto, D., Tavani, R., Green, S., Bruce, G., Williams, S. J., Wiser, S. K., Huber, M. O., Hengeveld, G. M., Nabuurs, G. J., Tikhonova, E., Borchardt, P., Li, C. F., Powrie, L. W., Fischer, M., Hemp, A., Homeier, J., Cho, P., Vibrans, A. C., Umunay, P. M., Piao, S. L., Rowe, C. W., Ashton, M. S., Crane, P. R., and Bradford, M. A. 2015. Mapping tree density at a global scale. Nature, 525(7568): 201-205. DOI: http://doi.org/10.1038/nature14967Glick, H. B., Bettigole, C. B., Maynard, D. S., Covey, K. R., Smith, J. R., and Crowther, T. W. 2016. Spatially explicit models of global tree density. Scientific Data, 3(160069), doi:10.1038/sdata.2016.69.

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

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

The Australian Antarctic Data Centre's Davis Station GIS data were originally mapped from aerial photography (February 11, 12 1997). Refer to the metadata record 'Davis Station GIS Dataset'.
Since then various features have been added to these data as structures have been removed, moved or established. Some of these features have been surveyed. These surveys have metadata records from which the report describing the survey can be downloaded.
However, the locations of other features have been obtained from a variety of sources.
The data are included in the data available for download from a provided URL.
The data conforms to the SCAR Feature Catalogue which includes data quality information. See a Related URL below.
Data described by this metadata record has Dataset_id = 104.
Each feature has a Qinfo number which, when entered at the 'Search datasets & quality' tab, provides data quality information for the feature.