How to Find an ArcGIS Parcel Layer URL (FeatureServer & MapServer Guide)

Published: March 2026 · Updated: March 24, 2026 · 10 min read

Many county GIS departments publish parcel data through ArcGIS REST services. Whether you need a layer URL for UrbanKit Studio's Parcel Lookup Tool, the Radius Notice Mailing List Generator, or your own GIS analysis, this guide shows you exactly how to find, verify, and troubleshoot ArcGIS parcel layer endpoints.

What Is an ArcGIS REST Service URL?

ArcGIS Server exposes geographic data through REST endpoints—web addresses you can query programmatically. A typical parcel layer URL looks like this:

https://gis.countyname.gov/arcgis/rest/services/Parcels/MapServer/0

The key parts are:

  • Host — The county's GIS server domain (e.g., gis.countyname.gov)
  • /arcgis/rest/services/ — The standard ArcGIS REST path
  • Service name — Often "Parcels," "AssessorParcels," or "CadastralData"
  • Server typeMapServer or FeatureServer
  • Layer index — Usually /0, but could be any number in a multi-layer service

FeatureServer vs MapServer — When to Use Each

You'll encounter two main service types when working with ArcGIS parcel layers. Understanding the difference helps you pick the right endpoint for your workflow.

Feature FeatureServer MapServer
Query individual features ✅ Full support ✅ Supported
Return GeoJSON ✅ Native ⚠️ JSON only (needs conversion)
Edit data ✅ If enabled ❌ Read-only
Spatial queries ✅ Full support ✅ Full support
Best for parcel lookups ✅ Preferred ✅ Works fine
Availability Less common More common
Recommendation: Use FeatureServer when available — it returns cleaner data and supports GeoJSON natively. MapServer works perfectly well for parcel lookups and radius queries, though, so use whichever your county provides.

Method 1: Search for Your County's GIS Portal

The fastest approach is a targeted web search:

  1. Search Google for: [Your County] [Your State] ArcGIS REST services
  2. Look for results containing /arcgis/rest/services in the URL
  3. Click through to the REST services directory page
  4. Browse the folder list for services named "Parcels," "Assessor," "Cadastral," or "Property"
  5. Click the service name, then click the layer (usually layer 0) that contains parcel polygons

Alternative search queries that often work:

  • [County Name] GIS parcel layer REST
  • site:arcgis.com [County Name] parcels
  • [County Name] GIS open data parcels
  • [County Name] FeatureServer parcels
  • [County Name] MapServer parcel layer

Method 2: Use the County's GIS Web Map

Most counties have an interactive web map (often called a "GIS Viewer" or "Property Search"). You can reverse-engineer the layer URL from there:

  1. Open your county's GIS web map (search: [County Name] GIS map viewer)
  2. Open your browser's Developer Tools (F12 or right-click → Inspect)
  3. Go to the Network tab and filter by "query" or "MapServer"
  4. Click on a parcel in the map and watch the network requests
  5. Look for requests to URLs containing /arcgis/rest/services/
  6. Copy the base URL up to and including the layer number
Pro tip: In the Network tab, filter requests by typing MapServer or FeatureServer. This quickly isolates the ArcGIS service calls from all other network traffic.

Method 3: Check ArcGIS Hub or Open Data Sites

Many counties publish data on ArcGIS Hub. To find parcel layers:

  1. Go to hub.arcgis.com
  2. Search for [County Name] parcels
  3. Find a result that's a "Feature Layer" or "Map Service"
  4. On the dataset page, look for a "View Full Details" or "URL" link
  5. The REST endpoint URL will be displayed, often under "Service URL" or in the metadata

How to Identify Owner, Address, and APN Fields in a Layer

Once you find a parcel layer, you need to know which fields contain the data you care about. County GIS departments use inconsistent naming, so here's how to decode common patterns:

Finding the fields list

  1. Open your layer URL in a browser (e.g., https://gis.county.gov/arcgis/rest/services/Parcels/MapServer/0)
  2. Scroll down to the "Fields" section
  3. Each field shows a name, alias, and data type

Common field name patterns

Data You Need Common Field Names
APN / Parcel Number APN, PARCELID, PIN, PARCEL_NUM, APN_FULL, ASSESSOR_ID
Owner Name OWNER, OWNERNAME, OWNER1, OWN_NAME, GRANTOR
Situs (Property) Address SITUS, SITUS_ADDR, SITE_ADDR, PROP_ADDR, ADDRESS
Mailing Address MAIL_ADDR, MAILING, OWN_ADDR, MAIL_LINE1
Zoning ZONING, ZONE_CODE, ZONE_CLASS, LAND_USE
Quick test: On the layer page, scroll to the bottom and click "Query". Set Where: 1=1, Out Fields: *, Return Geometry: false, Result Record Count: 5, Format: JSON. Click "Query (GET)" to see sample records with all field values. This instantly shows you what data is available.

Verifying Your Layer URL

Once you have a URL, verify it's the right layer:

  1. Paste the URL into your browser
  2. You should see a page showing the layer details: name, geometry type, fields, etc.
  3. Confirm the Geometry Type is esriGeometryPolygon (not Point)
  4. Check the Fields list for attributes like APN, owner name, and mailing address
  5. Scroll down and click "Query" to test: set Where: 1=1, Return Geometry: true, Format: JSON, and click "Query (GET)"

Common Reasons a Parcel Layer Won't Work

If you've found a URL but it's not returning data, here are the most common causes and fixes:

1. Authentication required (403 Forbidden)

Some services are restricted to internal networks or require login credentials. Check if the county has a separate public-facing service — many publish both internal and external endpoints.

2. Layer returns points instead of polygons

Some parcel services include both centroid points and polygon layers. Check the Geometry Type on the layer info page. You want esriGeometryPolygon. If you see esriGeometryPoint, look at other layers in the same service (try /1, /2, etc.).

3. CORS errors in the browser

If the service works when you visit the URL directly but fails in a web app, it's a CORS (Cross-Origin Resource Sharing) issue. The county's server doesn't allow requests from other websites. Workarounds include using a proxy server or downloading the data as a file instead.

4. Query returns empty results

  • Check if the service has a max record count — some limit results to 1,000 or even 100 features per query
  • Try a simpler query: Where: 1=1 with Result Record Count: 1
  • The layer may be visible but have no queryable data (check "Supports Query" on the layer info page)

5. Service is deprecated or moved

Counties occasionally reorganize their GIS services. If a URL that used to work returns a 404, go back to the REST services directory (/arcgis/rest/services) and look for a renamed or relocated service.

Important: Some services require authentication or are restricted to internal networks. If you get a 403 error or empty results, the service may not be publicly accessible. Check if the county has a separate public-facing service.

Common URL Patterns by Platform

Different counties use slightly different URL structures:

  • Standard ArcGIS Server: https://gis.county.gov/arcgis/rest/services/[ServiceName]/MapServer/0
  • ArcGIS Online: https://services.arcgis.com/[orgId]/arcgis/rest/services/[ServiceName]/FeatureServer/0
  • ArcGIS Enterprise: https://gis.county.gov/server/rest/services/[Folder]/[ServiceName]/MapServer/0

What to Do If You Can't Find It

If web searches come up empty:

  • Call the county GIS department — Ask if they have a public ArcGIS REST endpoint for parcels
  • Check for alternative formats — The county may offer downloadable GeoJSON or Shapefiles instead. See our guide on getting parcel GeoJSON data
  • Try neighboring counties — Regional GIS consortiums sometimes host data for multiple counties
  • Use a data aggregator — Services like Regrid provide standardized parcel APIs across jurisdictions

Have your parcel layer URL ready?

Try the Parcel Lookup Tool →

Or use it with the Radius Mailing List Generator to find nearby property owners.

Related Resources