URBANKIT/STUDIO
    Sign inFREE TOOLS · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY · OPEN SOURCE
    ATLAS · COUNTY·IN·FIPS 18057·gis1.hamiltoncounty.in.gov

    Hamilton County, IN
    parcel REST API.

    Public ArcGIS FeatureServer endpoint for Hamilton County parcel data. URL, supported fields, and a working sample query, copy it, or open it directly in the UrbanKit parcel lookup tool.

    Primary ArcGIS REST endpoint
    https://gis1.hamiltoncounty.in.gov/arcgis/rest/services/HamCoParcelsPublic/FeatureServer/0
    FeatureServer · LAYER 0 · PARCELS
    https://gis1.hamiltoncounty.in.gov/arcgis/rest/services/HamCoParcelsPublic/FeatureServer/0

    Searchable fields

    • FMTPRCLNOFormatted Parcel Number
    • DEEDEDOWNRDeeded Owner Name
    • OWNNAMEOwner Name
    • OWNADDRESSOwner Address
    • OWNCITYOwner City
    • LOCADDRESSProperty Address
    • LOCCITYProperty City

    Sample query (paste into terminal or browser)

    curl -s 'https://gis1.hamiltoncounty.in.gov/arcgis/rest/services/HamCoParcelsPublic/FeatureServer/0/query?where=UPPER(DEEDEDOWNR)%20LIKE%20UPPER('%25SMITH%25')&outFields=FMTPRCLNO,DEEDEDOWNR,LOCADDRESS,LOCCITY&returnGeometry=false&f=json&resultRecordCount=10'
    License
    Public records (terms)
    Listed on
    2026-05-15
    Registry listing
    Listed live
    Sample query
    https://gis1.hamiltoncounty.in.gov/arcgis/rest/services/HamCoParcelsPublic/FeatureServer/0/query?where=UPPER(DEEDEDOWNR) LIKE UPPER('%SMITH%')&outFields=FMTPRCLNO,DEEDEDOWNR,LOCADDRESS,LOCCITY&returnGeometry=false&f=json&resultRecordCount=10

    Open this URL in a browser tab to see the raw ArcGIS JSON response.

    Searchable fields
    Searchable fields for Parcels
    Field nameLabelSearchable
    FMTPRCLNOFormatted Parcel Number YES
    DEEDEDOWNRDeeded Owner Name YES
    OWNNAMEOwner Name YES
    OWNADDRESSOwner Address YES
    OWNCITYOwner City YES
    LOCADDRESSProperty Address YES
    LOCCITYProperty City YES
    PROPCLASSProperty Class NO
    Notes

    Hamilton County IN (Indianapolis north suburbs, Noblesville, Carmel, Fishers, Westfield) is one of the fastest-growing counties in Indiana. HamCoParcelsPublic/FeatureServer/0 exposes 25+ fields including FMTPRCLNO (formatted parcel number, e.g., '10-11-04-00-00-019.000'), DEEDEDOWNR (full deeded owner), OWNNAME, OWNADDRESS, OWNCITY, OWNSTATE, OWNZIP, OWNCOUNTRY, LOCADDRESS, LOCHSENUMR, LOCSTRDIR, LOCSTRNAME, LOCSTRSUF, LOCCITY, LOCZIP, LEGALDESC, SECTIONNO, TOWNSHIP, RANGE, SUBDIVCODE, SUBDIVNAME, DEEDACRES, PROPCLASS, PROPUSE. Query confirmed live: UPPER(DEEDEDOWNR) LIKE '%SMITH%' returns real results (e.g., 'Smith, Terrance & Alyssa Smith h&w' in Noblesville). Hamilton County IN (FIPS 18057) must not be confused with Hamilton County OH (39061, Cincinnati) or Hamilton County TN (47065, Chattanooga). GeoHub portal at geohub.hamiltoncounty.in.gov. EXPORTDATE field tracks data currency.

    Source

    Hamilton County GIS, https://www.hamiltoncounty.in.gov/442/GIS-and-Maps

    Using this endpoint

    What Hamilton County publishes

    Hamilton County's Parcels layer exposes a parcel identifier (Formatted Parcel Number), owner names (Deeded Owner Name, Owner Name, Owner Address, Owner City), and address fields (Property Address). Use it for owner-name lookups and address-based parcel searches. 7 of 8 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS FeatureServer layer, so edits and applyEdits operations are technically exposed (read access only is published here); last verified 2026-05-15.

    Two paths from URL to result

    1. Open in Parcel Lookup: click the button on the endpoint card. The lookup tool loads the layer, auto-detects fields, and gives you a search box. No code, no API keys, just a browser.
    2. Query directly: append /query?where=…&outFields=*&f=jsonto the URL. The sample query above is a working example you can paste into a browser tab to see the raw JSON response.

    Why field names vary by county

    Counties publish parcel data through their own ArcGIS Server installations, each with its own schema. One county uses APN, another uses PIN, a third uses PARCEL_ID. Some expose owner names; others keep them on a separate assessor's portal. The searchable fields list above reflects what Hamilton County actually publishes, not what you might expect from a national standard (there isn't one).

    For background, see What is an APN?

    What to do with the results

    • Generate a public-notice mailing list: pipe the parcel layer URL into Radius Notice to buffer around an address and select neighboring owners.
    • Print Avery 5160 labels: export the result CSV and drop it into CSV → Labels.
    • Pull individual parcel records: use Parcel Lookup directly to grab zoning, assessed value, and ownership for one property at a time.

    Quick FAQs

    Can I query Hamilton County's parcel layer from my own web app?

    gis1.hamiltoncounty.in.gov serves Hamilton County, Indiana parcels over public ArcGIS REST, but, like most county servers, it may not send the CORS headers a browser needs for a cross-origin fetch. If a direct browser call fails, the layer still works from curl, Postman, or a server-side script; the UrbanKit parcel lookup tool proxies the request, so a search that succeeds there confirms the layer is genuinely public.

    Is the Hamilton County endpoint still current?

    We last verified Hamilton County's FeatureServer layer on 2026-05-15. County GIS teams move services without notice, so if you hit a fresh 404, tell us and we'll re-check. Atlas entries are re-verified on a rolling basis.

    Is there a rate limit on Hamilton County parcel queries?

    Hamilton County's layer is hosted by the county on gis1.hamiltoncounty.in.gov. Public ArcGIS endpoints rarely rate-limit individual reads, but gis1.hamiltoncounty.in.gov can throttle heavy automated traffic at the host level. Page through results with resultOffset / resultRecordCount and request only the fields you need. There's no API key and no charge from the county.

    View all FAQs →

    Continue