Traverse County, Minnesota
countyTraverse County — hub for local data and maps.
Coverage: County publisher; individual layer coverage varies. County GIS resources; individual layer extents not checked.
- Publisher
- Traverse County
- Platform
- ArcGIS Hub
- Last checked
- 2026-11-08 (ET)
The staples
Always visible. Absence is scoped to the inspected publications; “not established” is not absence.
| Layer / official page | Format | Updated | Licence / use |
|---|---|---|---|
| Parcels / ownershipTax Parcel leaf 0 exposes OWNER_NAME, taxpayer/property address and valuation fields. Legacy Parcels rendering is also published; no assumption of survey accuracy or ownership completeness. | |||
| ✓Tax Parcel (official page, opens in new tab) | ArcGIS service layer | Not recorded | Terms not specified; check publisher |
| ✓Tax Parcels (official page, opens in new tab) | Feature Service | Not recorded | Publisher terms / disclaimer; check official page |
| Zoning / overlay districtsNot published by the county in the inspected scope | No named zoning publication in Traverse starting/related catalog collections and the linked item/service inventory. All readable layer/table leaves, domains and renderer labels checked; M is limited to this publication scope, not jurisdiction-wide absence. No zoning/overlay family, shoreland/airport/PUD/historic regulatory layer or adopted flood overlay identified in the one configured item, five-item official gallery and nested cadastral/land-record schemas. Unreadable legacy app configuration is separately logged. | ||
| Address pointsPublication not established — not a missing-data claim | U: PROPERTY_ADDRESS and owner/taxpayer address attributes belong to parcel polygons. Gallery Cadastral Reference points are survey corners, not dedicated E911/address points. No separate address-point product verified. | ||
| Building footprintsNot published by the county in the inspected scope | ESTIMATED_BUILDING_VALUE is a parcel valuation attribute, not building geometry. The LiDAR Layer I/II feature metadata concerns lidar products, not verified structure footprints; no raster/file data opened. | ||
| Municipal / county boundaryP is boundaries branch: gallery County Boundary plus LandRecords county/municipality/township leaves. No standalone street-centerline network established. This additional gallery is why the one-item configured catalog is not the full publication inventory. | |||
| ✓Municipality (official page, opens in new tab) | ArcGIS service layer | Not recorded | Terms not specified; check publisher |
| ✓Township (official page, opens in new tab) | ArcGIS service layer | Not recorded | Terms not specified; check publisher |
Also published by this county
Selected inventoried holdings, not an exhaustive catalog. Publisher pages remain authoritative.
Site and development
| Layer / official page | Format | Updated | Licence / use |
|---|---|---|---|
| Other inventoried holdingsPublished catalog entries; service aliases and vintages are not counts of unique datasets. | |||
| ✓Tax Parcels (official page, opens in new tab) | Feature Service | Not recorded | Publisher terms / disclaimer; check official page |
Inventory scope
County GIS resources; individual layer extents not checked.
One configured Tax Parcels item, plus a separately linked organization gallery with five public items. That gallery exposes Cadastral Reference and County Boundary, so the site is not described as parcel-only.
LandRecords contains eight county/municipality/PLSS/block/lot polygons; Cadastral Reference contains five leaves. Dedicated address/building/street-centerline products were not established by these cadastral products.
The landing background 2009_Pictometry_Traverse service returns not found. Mobile Mapping HTML loads but its ArcGIS item configuration is empty/non-JSON, and displays a browser-support message; no browser-UA spoofing, guessed config or alternate authentication used.
FindGiS links to official pages. It does not host these local files. Blank update dates mean the source did not establish a dataset update date, not that the data are current.