01 / SHARE CONTEXT
Introduce your data
Tell us what your organization maintains, the area it covers and the public access methods already available.
FOR COUNTIES, AGENCIES & ASSOCIATIONS
Local knowledge.
Statewide possibility.
You maintain information that helps people understand their communities. We want to make that work easier to discover, with its source and limitations intact.
02 / KEEP IT RELIABLE
Plan for updates
Help us understand stable identifiers, publication schedules, corrections and how parcels change over time.
03 / MAKE IT USEFUL
Reach the community
Explore a geographic presentation that gives residents and local organizations another way to find and understand the information.
OUR NEXT MAJOR DATA PRIORITY
Parcel boundaries.
Built from reliable sources.
We plan to assemble and standardize county datasets behind the scenes, validate their coverage and establish an update process before making a statewide parcel layer public.
Standardization should preserve the original county identifier and source. The goal is a consistent experience that can still accept new county releases, corrections and parcel changes.
A useful starting point
- Parcel polygon geometry and county parcel identifiers.
- Available property attributes and field definitions.
- Coverage gaps, source dates and coordinate reference system.
- A public download, GIS service or other update method.
- Attribution, display conditions and applicable fees.
- Whether any fees could be waived for this community-oriented project.
A conversation before a commitment.
An initial discussion helps us understand what is possible. Sending an inquiry does not grant access, establish an endorsement or create a data-sharing agreement.
We welcome county GIS and equalization teams, public agencies, local organizations and real-estate associations. We can demonstrate the local development project and discuss the information your organization maintains.
Discuss a data partnershipTHE FOUNDATIONS OF THE MAP
Technology & data
behind MittenScope.
Mapping technology, public datasets and community contributions used in our development project.
Explore the sources
- EsriSatellite basemaps
- DDOTDetroit transit routes & stops
- Google MapsPhotorealistic 3D Tiles
- CATALansing-area transit data
- Cesium3D globe technology
- The RapidGrand Rapids transit data
- NOAAGreat Lakes reference data
- Michigan EGLEEnvironmental facility data
- NASASatellite imagery & models
- Lansing BWLLocal water facility references
- U.S. Census BureauBoundaries & community data
- City of Grand RapidsLocal water facility references
- OpenStreetMapCommunity mapping data
- Great Lakes Water AuthorityLocal water facility references
- CelesTrakSatellite orbital elements
- GLAHFGreat Lakes shoreline geometry
- OpenSky NetworkAircraft position data
- USGSEarthquake observations
- adsb.lolAircraft position fallback
- U.S. EPAWater & wastewater references
- U.S. EIAEnergy facility data
- AISStreamVessel position data
- adsbdbAircraft reference information
- The Space DevsSpace mission reference data
- U.S. Coast GuardLighthouse signal references
- FRA / BTSRail network geometry
- AmtrakerTrain reports & station data
- FAA / BTSAirport reference data
- AmtrakMichigan passenger rail services · reports via Amtraker
- U.S. Army Corps of EngineersNational Inventory of Dams references
- Michigan DOTMichigan bridge references
OpenStreetMap logo: Ken Vermette, CC BY-SA 3.0. Resized for display.
LET'S CONNECT