View In:   ArcGIS Online Map Viewer

Name: GREENWAY

Display Field: name

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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. &lt;b&gt;NOTICE&lt;/b&gt;: 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 &lt;a href="Metro_Regional_Parcel_Attributes.pdf" target=_blank&gt;Metro Regional Parcel Attributes&lt;/a&gt; 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 = http://www.hennepin.us/gisopendata 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</SPAN></P></DIV></DIV></DIV>

Service Item Id: 34aac870806d401fb7e3b374dc6e0bc7

Copyright Text: Carver County

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 0

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Extent:

XMin: 469564.69519999996
YMin: 4974825.077199999
XMax: 471451.2460000003
YMax: 4975579.4078
Spatial Reference: 26915  (26915)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [252, 224, 179, 0]
Outline:
Style: esriSLSSolid
Color: [250, 210, 63, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Feature Draw Order:

N/A

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: false
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: true
Supports Returning Geometry Centroid: true
Supports Binning LOD: true
Supports Query With LOD Spatial Reference: true
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: false
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

• objectid ( nullable: false, editable: false, defaultValue: null, alias: OBJECTID, type: esriFieldTypeOID )
• name ( nullable: true, editable: true, defaultValue: null, length: 10, alias: NAME, type: esriFieldTypeString )

Templates:

• Name: GREENWAY
  Description:
  Prototype:
  name: null
  
  Drawing Tool: esriFeatureEditToolPolygon

Capabilities: Query

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Query Attachments   Query Analytic   Query Top Features   Query Bins   Append   Validate SQL   Generate Renderer   Return Updates   Metadata   Update Metadata