Sign in
project

Get Address Feature Geometry

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

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

Changed in 2 of the 30 revisions of this API.32

  • bb508e93517431See the full diff
    • ▲

      the query request parameter county_fips became required

      request-parameter-became-required

    • ▲

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

      request-parameter-list-of-types-narrowed

    • ▲

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

      request-parameter-pattern-added

    • ○

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

      request-parameter-type-generalized

  • 8beaac28e1951See the full diff
    • ○

      added the new optional query request parameter county_fips

      new-optional-request-parameter