URBANKIT/STUDIO
    Sign inFREE TOOLS · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY · OPEN SOURCE
    ATLAS · STATE·OR

    Oregon county
    parcel REST APIs.

    3 counties indexed. ArcGIS FeatureServer and MapServer URLs, with supported search fields per layer.

    Counties indexed in this state, with endpoint counts, supported fields, and status.
    CountyEndpointsSearchable fieldsStatusAction
    Lane County1RLID (Regional Land Information Database ID) · Map-Taxlot Number · Owner Name +3 LIVEOPEN
    Marion County1Tax Lot Number · Tax Account Number · Owner Name +1 LIVEOPEN
    Multnomah County1Tax Lot ID · Account ID · Mailing Name (Owner) +3 LIVEOPEN

    About Oregon county parcel data

    State overview

    Oregon property records are maintained by county Assessment and Taxation departments, which are distinct from county planning or GIS offices. Each county publishes parcel data independently; there is no statewide cadastral aggregation service. The atlas covers three counties: Multnomah (Portland), Lane (Eugene), and Marion (Salem). These three together span the northern Willamette Valley and represent Oregon's three largest cities outside of the Portland metro suburbs. Multnomah is the most populous county in the state. Oregon parcel layers consistently expose Real Market Value fields (RMVLND, RMVIMP, RMVTOTAL) derived from the state's mass appraisal system, which is a field set rarely available on public layers in other states.

    Regional coordination

    Oregon has no statewide parcel clearinghouse comparable to NC OneMap. Oregon Spatial Data Library (OSGL) hosts some statewide layers but not a unified parcel REST endpoint. DOGAMI (Department of Geology and Mineral Industries) covers hazard and geology data, not parcels. Each county Assessment and Taxation office is the authoritative source; GIS is typically a function of the county's information services department working alongside the Assessor. Lane County uses the Regional Land Information Database (RLID) identifier — RLID was historically a shared Lane-Douglas-Coos regional database, though Lane County now maintains it. Multnomah and Lane have both shown endpoint instability in atlas liveness checks, meaning occasional timeout or HTTP error responses; Marion has been the most consistently available of the three.

    Common data quirks

    Lane County's endpoint uses HTTP, not HTTPS

    The Lane County parcel endpoint at lcmaps.lanecounty.org uses HTTP as its base URL. The server redirects HTTPS requests down to HTTP, which creates a mixed-content situation if you are embedding the query in a browser-based HTTPS application. Queries from server-side scripts or GIS tools that follow redirects will generally succeed, but browser fetch() calls from HTTPS origins will be blocked by the browser's mixed-content policy. Additionally, Lane County's endpoint has shown intermittent timeouts in the atlas liveness checks; retry logic is advisable. The RLID field is Lane County's primary parcel identifier, distinct from MAPTAXLOT (the map-taxlot number).

    Multnomah uses MAILING_NA for owner name, not a standard owner field

    Multnomah County's Tax Lots layer uses MAILING_NA as the owner name field — short for 'mailing name,' which in Oregon assessment records is the name used for tax billing. This is not the same as a deed-instrument owner name in other states' schemas. The field is searchable and returns real owner results (e.g., 'SMITH TIMOTHY BLAIR & KAREN KAY'). Multnomah also exposes IN_CARE_OF and AGENT as separate fields, which is useful when properties are held in trusts or LLCs where the mailing name differs from the beneficial owner. The SITUS address is split across SITUS_HOUS (house number), SITUS_STRE (street name), and SITUS_CITY — there is no combined situs string in the Multnomah layer.

    Oregon Real Market Value fields are publicly available

    All three Oregon atlas counties expose Real Market Value on the public parcel layer: RMV_PROPER (Multnomah), RMVTOTAL (Lane and Marion). This is notably more than most US states expose publicly; in states like Georgia or Indiana, assessed values and market values are often held in the CAMA system and not published on the REST layer. Oregon's property tax system ties assessed value to Measure 50 limits, creating a potential gap between RMVTOTAL (what the county thinks the property is worth) and ASSDVAL (the Measure 50-capped assessed value used for tax calculation). Marion County exposes both RMVTOTAL and ASSDVAL; Lane exposes only RMV fields.

    Key counties

    Multnomah County

    Contains Portland (pop. 830,000 county). Owner name is MAILING_NA; site address is split across SITUS_HOUS, SITUS_STRE, SITUS_CITY. Hosted on ArcGIS Online (services3.arcgis.com). Exposes RMV_PROPER. Endpoint has shown intermittent instability in liveness checks; include error handling in automated scripts.

    Lane County

    Contains Eugene (pop. 380,000 county). Base URL is HTTP; HTTPS redirects down. Owner field is OWNNAME; parcel identifier is RLID (Regional Land Information Database ID) and MAPTAXLOT. Exposes RMVLND, RMVIMP, RMVTOTAL. maxRecordCount=1000. Intermittent timeout history.

    Marion County

    Contains Salem (Oregon state capital; pop. 340,000 county). This is Oregon's Marion County (FIPS 41047), distinct from Indiana's Marion County (FIPS 18097, Indianapolis). Hosted at gis.co.marion.or.us. Exposes OWNERNAME, SITUS, SITUSCSZ (combined city-state-ZIP), RMVTOTAL, ASSDVAL, ZONECODE, YEARBUILT.

    Common search patterns

    Multnomah owner query (MAILING_NA): ?where=UPPER(MAILING_NA)+LIKE+UPPER('%25SMITH%25')&outFields=TLID,MAILING_NA,M_ADDRESS,M_CITY,SITUS_STRE,SITUS_CITY,RMV_PROPER&f=json. Lane County (OWNNAME, note HTTP base URL): http://lcmaps.lanecounty.org/arcgis/rest/services/AT/AddressParcelSales/MapServer/2/query?where=UPPER(OWNNAME)+LIKE+UPPER('%25SMITH%25')&outFields=RLID,MAPTAXLOT,OWNNAME,SITUS,GEOCITY,RMVTOTAL&f=json. Marion County OR (OWNERNAME): ?where=UPPER(OWNERNAME)+LIKE+UPPER('%25SMITH%25')&outFields=TAXLOT,OWNERNAME,SITUS,RMVTOTAL,ASSDVAL,ZONECODE&f=json. Append returnGeometry=false&resultRecordCount=10.

    Related articles

    Last updated 2026-05-24.

    Questions, with answers

    Oregon parcel REST API — common questions

    Which Oregon counties publish a public parcel ArcGIS REST API?

    3 Oregon counties are indexed in the UrbanKit atlas with verified public REST endpoints: Multnomah, Lane, and Marion. Each exposes an owner-name field you can search directly on the public layer.

    How do I search Oregon parcels by owner name?

    Multnomah, Lane, and Marion expose an owner-name field on the public REST layer. Multnomah, for example, uses the MAILING_NA field — a case-insensitive search is ?where=UPPER(MAILING_NA)%20LIKE%20UPPER('%25SMITH%25')&outFields=*&f=json. Open a county's page here for its full field list and a ready-to-run sample query.

    What is the ArcGIS REST URL for parcels in Multnomah, Oregon?

    Multnomah publishes parcels at https://services3.arcgis.com/tNPgIZWOB0Efvm0g/ArcGIS/rest/services/Tax_Lots/FeatureServer/0 — a FeatureServer (layer 0). It indexes by Tax Lot ID, Account ID, Mailing Name (Owner), and Mailing Address. Owner-name search: UPPER(MAILING_NA) LIKE UPPER('%25SMITH%25').

    Do Oregon parcel layers use ArcGIS FeatureServer or MapServer?

    Both. Oregon uses a mix: Multnomah publish ArcGIS FeatureServer layers, while Lane and Marion use MapServer. Both support /query, so the same owner, parcel-ID, and address lookups work against either.

    Listing missing or moved? Tell us — we verify and update weekly.