Skip to content
MAIA LogoDocs

Capabilities/Data

Core data

MAIA's core data takes a question about a county and returns rows from the datasets MAIA already holds: parcels, buildings, businesses, environmental records, census data, and more, joined on one spatial model.

What it answers#

Any question the loaded datasets answer on their own. MAIA filters and joins them into a layer, and no research runs. Use it at Define, to decide whether the records can answer your objective before you write it.

You ask

Find parcels between two and seven acres within a quarter mile of a substation, zoned industrial.

What you get#

MAIA holds the records that describe a place and what is around it: parcels and their ownership, buildings and businesses, flood and environmental records, census demographics, boundaries, land use, schools, roads and the electric grid, permits, and incentive zones. Every dataset is included in every plan.

The full catalog lives inside the product, on the data catalog, where each dataset is listed with its source, its coverage, and its date. It is always expanding, and it is kept in one place so that it stays current. The website does not repeat it.

The data catalog, under your account menu. Each dataset shows its source, its coverage in your counties, and what you can ask of it.

A parcel record carries ownership and mailing address, land use and the zoning code as the county publishes it, assessed and market values, tax amount and delinquency, lot size and dimensions, last sale, and structure details.

Note

Depth varies by county. Some counties publish a boundary and a parcel number and nothing more. Check what your county holds in the catalog before you define an objective that depends on a field.

How the data fits together#

  • Everything joins on the parcel. Buildings, businesses, permits, listings, and census geography all attach to the parcels they sit on, so one question can reach across all of them.
  • Distance is straight-line unless you ask for travel. "Within a mile" is measured as the crow flies. "Within a ten-minute drive", walk, or bike ride is routed over the road network, with both ends in the project's county. Times assume free-flowing roads.
  • The agent queries the data. It never changes it. Source data is read-only, and the agent writes only to the layers it creates.

Freshness#

Each dataset carries a date. Read it before you rely on a value. A listing is a snapshot with a date, not current availability. Census data belongs to a release. A traffic count belongs to a year.

Recorded and modeled values#

Sale price from the public recordKindRecordedHow to read itThe price as recorded
Sale price marked as an estimateKindModeledHow to read itAn estimate. MAIA says so when it quotes one
Elevation, slope, corner lotKindCalculated by MAIAHow to read itComputed from terrain and road data
ZoningKindRecordedHow to read itThe zoning on record. It is not a ruling on what you may build
VacantKindRecordedHow to read itMail vacancy as reported. It does not mean vacant land

Limits#

  • One county per project. For a second county, start a second project.
  • A query has a time limit. One that runs too long is stopped, and MAIA narrows it.
  • 250,000 features per layer. Above that, MAIA asks you to narrow the objective.
  • Parcels are not always polygons. In a county with no parcel boundaries, a parcel is an address point. Adjacency and containment cannot be computed there, and area is blank. A parcel with no building footprint is not therefore vacant.
  • Sparse datasets are not complete. For permits and listings, an empty result means the data is not loaded there. It does not mean zero.

In the app and over MCP#

The web appHowState the objective in chat. The layer lands on the map and in the table
MCPHowPut the objective in the request of create_project. get_project lists the layers, columns, and row counts. To read rows, open the project link

Related#