URBANKIT/STUDIO
    Sign inFREE TOOLS · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE TOOLS · NO SIGNUP
    ATLAS · COUNTY·LA·FIPS 22071·gis.nola.gov

    Orleans Parish, LA
    parcel GIS REST API.

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

    Look up a parcel

    This page is the endpoint reference. If you came here to find a specific property, the Orleans Parish parcel search runs this same layer in your browser, no account and no API key.

    Search Orleans Parish parcels

    Have a street address but not the parcel number? Find the parcel number by address.

    Free property report

    Beyond the parcel record, Orleans Parish has a free New Orleans property report: code violations and building permits for an address, read straight from the city's open data.

    Free New Orleans property report: code violations + building permits
    Primary ArcGIS REST endpoint
    https://gis.nola.gov/arcgis/rest/services/apps/property3/MapServer/15

    What these endpoints answer

    Field by field, whether any endpoint we index for Orleans Parish answers it, and the evidence for each. We only call a field restricted when there is a stated reason we can cite. Everything else here is a fact about the services we index, not a claim about the law.

    Which parcel fields Orleans Parish’s endpoint answers, and the evidence for each
    FieldStatusBasis
    APN AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Owner name AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Owner mailing address AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Site address AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Geometry AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Land use AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Zoning Not publishedNo endpoint we index for this county documents this field, so a query cannot ask for it. That is a fact about the services we index, not a legal restriction, and not a statement that the county holds no such record. Where to request it.
    MapServer · LAYER 15 · PROPERTY INFORMATION [PARCELS]
    https://gis.nola.gov/arcgis/rest/services/apps/property3/MapServer/15

    Searchable fields

    • PARIDParcel ID (PARID, per unit)
    • PARCELIDGeoPIN (lot id, shared by condo units)
    • TAXBILLIDTax Bill ID

    Sample query (paste into terminal or browser)

    curl -s 'https://gis.nola.gov/arcgis/rest/services/apps/property3/MapServer/15/query?where=PARCELID%3D%2741033176%27&outFields=*&returnGeometry=false&f=json&resultRecordCount=1'
    License
    Public records (terms)
    Listed on
    2026-10-03
    Registry listing
    Listed live
    Sample query
    https://gis.nola.gov/arcgis/rest/services/apps/property3/MapServer/15/query?where=PARCELID='41033176'&outFields=*&returnGeometry=false&f=json&resultRecordCount=1

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

    Searchable fields
    Searchable fields for Property Information [Parcels]
    Field nameLabelSearchable
    PARIDParcel ID (PARID, per unit) YES
    PARCELIDGeoPIN (lot id, shared by condo units) YES
    TAXBILLIDTax Bill ID YES
    OWNERNME1Owner Name 1 NO
    OWNERNME2Owner Name 2 NO
    SITEADDRESSSite Address NO
    BUILDINGBuilding Number NO
    UNITUnit NO
    PSTLADDRESSPostal (Mailing) Address NO
    PSTLCITYPostal City NO
    PSTLSTATEPostal State NO
    PSTLZIP5Postal ZIP NO
    USECDUse Code NO
    LOTLot NO
    SQUARESquare NO
    Notes

    LIVE 2026-10-03 for lookup by location in clients that complete the TLS chain (see TLS below); no attribute search. Layer 15 refuses any query that NAMES its outFields except an exact PARCELID equality: measured 2026-10-03 on the paid shapes (point + 30 m buffer; 800 m envelope with geometry) and on a scan (OBJECTID>0, resultRecordCount=1), every named column list answers HTTP 200 carrying ArcGIS error 400 "Failed to execute query." in about 0.2 s, while the identical request with outFields=* answers 40 features in 0.28 s and 501 features (957 KB) in 0.65 s. UrbanKit sends outFields=* to this layer (api/_lib/arcgis-quirks.ts, WILDCARD_OUT_FIELDS) and keeps only the role columns. Any predicate that scans the table (1=1, OBJECTID>0, PARCELID IS NOT NULL, an owner LIKE) runs past 40 s even for a single row, so no where-clause search is offered (attributeSearch: unsupported) and owner-name lookup is not available here; the owner columns (OWNERNME1, OWNERNME2) and the mailing address (PSTLADDRESS, PSTLCITY, PSTLSTATE, PSTLZIP5) are returned on every spatial hit (a UrbanKit row keeps PSTLADDRESS, the street line). IDS: PARID is the assessor's per-unit parcel id (e.g. 622-SALEXANDERST) and is listed first so rows key by unit; PARCELID is the GeoPIN, a lot id shared by every condo unit on the lot (a 30 m buffer in the CBD: 40 units, 3 lots, 39 owners), so keying on it would collapse a notice list to one row per lot; TAXBILLID is the tax bill number. Exact PARCELID equality answers in 0.2 s and is the sample query, which is also the predicate the liveness probe falls back to when its first shape (1=1) times out. CORS reflects the request origin. TLS: the server sends an INCOMPLETE certificate chain (leaf without its Sectigo intermediate). Clients that fetch the missing intermediate themselves (curl on Windows, Chromium and Safari through the OS store) connect; Node's fetch fails the handshake with UNABLE_TO_VERIFY_LEAF_SIGNATURE (measured 2026-10-04). UrbanKit's billed bulk-enrichment and radius paths run on Vercel's Edge runtime, which cannot be given a certificate authority and whose handling of an incomplete chain is undocumented and not yet measured, so assume they cannot serve this parish until a keyed test on the deployed function shows otherwise; today an Orleans row ends county-unavailable and is refunded, unchanged from before. The liveness probe pins the intermediate, so its ok reflects the layer, not the paid paths. An agent that fetches this URL from Node must trust the Sectigo intermediate or the request fails before any query runs. Tracked in GitHub issue #906. HISTORY: marked unreachable 2026-08-29 after 463 consecutive failed probes whose predicate (PARCELID IS NOT NULL) is a table scan; the layer was answering spatial queries the whole time. Ownership data looked dated during the 2026-08 checks; the 2026-10-03 rows carry current-looking owner names.

    Source

    City of New Orleans GIS (NOLA GIS), https://gis.nola.gov/

    Using this endpoint

    What Orleans Parish publishes

    Orleans Parish's Property Information [Parcels] layer exposes parcel identifiers (Parcel ID (PARID, per unit), GeoPIN (lot id, shared by condo units)). Use it for PIN-keyed record pulls (owner-name search lives on a separate assessor system). 3 of 15 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS MapServer layer, which supports query operations but not write operations; last verified 2026-10-03.

    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 Orleans Parish 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 Orleans Parish's parcel layer from my own web app?

    gis.nola.gov serves Orleans Parish, Louisiana 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 Orleans Parish endpoint still current?

    We last verified Orleans Parish's MapServer layer on 2026-10-03. 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 Orleans Parish parcel queries?

    Orleans Parish's layer is hosted by the county on gis.nola.gov. Public ArcGIS endpoints rarely rate-limit individual reads, but gis.nola.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