project

Get Address Feature Geometry

Changed on

Drawable geometry + bbox for one resolved candidate, pre-project.

county_fips is the candidate's county; it bounds the read so a commons workspace plans against that county's partition alone.

404 covers a malformed/unknown feature_id, a row with null geometry, and a county the workspace may not read — either way there is nothing to draw. Read failures map to 503, mirroring /address/resolve.

get/api/v1/project/address/feature-geometry

Request

  • Base URL
    https://api.maia-analytics.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.maia-analytics.com/api/v1/project/address/feature-geometry
  • Auth
    HTTP bearer

Query parameters

source_table'parcel' | 'building' | 'place' | 'address' | 'school' required

The table a resolved feature lives in — what a caller pulls its data from, and the feature's kind. A text match in the address, place or school table resolves (point-in-feature) to a parcel/building; a parcel attribute match resolves to the parcel itself.

feature_idstring required
county_fipsstring required

Response

Successful Response

geometryobject required

Changes

  • bb508e935174Revision changes
    • breaking

      the query request parameter county_fips became required

    • breaking

      query request parameter county_fips list-of-types was narrowed by removing types null

    • breaking

      added the pattern ^\d{5}$ to the query request parameter county_fips

    • info

      for the query request parameter county_fips, the type was generalized from no type to string

  • 8beaac28e195Revision changes
    • info

      added the new optional query request parameter county_fips