ArcGIS REST Services Directory Login
JSON | SOAP

plan_regonal_parcels_2014 (MapServer)

View In:   ArcGIS JavaScript   Portal Map Viewer   ArcGIS Earth   ArcMap   ArcGIS Pro

View Footprint In:   Portal Map Viewer

Service Description:
Metadata - http://gis/datacatalog/metadata/Parcels2014.html



Map Name: plan_regonal_parcels_2014

Legend

All Layers and Tables

Dynamic Legend

Dynamic All Layers

Layers: Description: This dataset is a compilation of tax parcel polygon and point layers from the seven Twin Cities, Minnesota metropolitan area counties of Anoka, Carver, Dakota, Hennepin, Ramsey, Scott and Washington. The seven counties were assembled into a common coordinate system. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. (See section 5 of the metadata). The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties. 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. The 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. Polygon and point counts for each county are as follows (Updated annually, current as of 1/15/2015: polygons / points Anoka - 130633 / 130633 Carver - 40198 / 40198 Dakota - 139405 / 152816 Hennepin - 427762 / 427762 Ramsey - 152210 / 166612 Scott - 55927 / 55927 Washington - 106151 / 106151 This is a MetroGIS Regionally Endorsed dataset. Each of the seven Metro Area counties has entered into a multiparty agreement with the Metropolitan Council to assemble and distribute the parcel data for each county as a regional (seven county) parcel dataset. A standard set of attribute fields is included for each county. The attributes are identical for the point and polygon datasets. Not all attributes fields are populated by each county. Detailed information about the attributes can be found in the MetroGIS Regional Parcels Attributes 2014 document. Additional information may be available in the individual metadata for 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 listed in the individual county metadata. 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: http://www.hennepin.us/gisopendata Ramsey =https://www.ramseycounty.us/your-government/open-government/research-data Scott =http://www.scottcountymn.gov/1183/GIS-Data-and-Maps Washington = http://www.co.washington.mn.us/index.aspx?NID=1606

Service Item Id: 6ba2df3f2a754f7bb7ba2e81451a83a0

Copyright Text:

Spatial Reference: 26915  (26915)


Single Fused Map Cache: false

Initial Extent: Full Extent: Units: esriMeters

Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP

Document Info: Supports Dynamic Layers: true

MaxRecordCount: 2000

MaxImageHeight: 4096

MaxImageWidth: 4096

Supported Query Formats: JSON, geoJSON, PBF

Supports Query Data Elements: true

Min Scale: 0

Max Scale: 0

Supports Datum Transformation: true



Child Resources:   Info   Dynamic Layer

Supported Operations:   Export Map   Identify   QueryDomains   QueryLegends   Find   Return Updates