--- title: "ArcGIS Guide: Finding Your Address Point Service URL" slug: "arcgis-guide-finding-your-address-point-service-url" description: "Learn how the ArcGIS residency-check integration uses address point layers and service URLs to verify residents, not Web Maps, boundaries, or shapefiles." updated: 2026-10-20T14:03:07Z published: 2026-10-20T14:03:07Z canonical: "www.civicplus.help/arcgis-guide-finding-your-address-point-service-url" --- > ## Documentation Index > Fetch the complete documentation index at: https://www.civicplus.help/llms.txt > Use this file to discover all available pages before exploring further. # ArcGIS Guide: Finding Your Address Point Service URL This article provides a quick guide on to how the residency-check integration connects to your ArcGIS data. ## What the ArcGIS Integration Does Our tool checks an address against your ArcGIS **address point layer:** - **Address found in the layer → Resident** - **Address not found → Non-resident** To do this, our system talks **directly** to the layer's data service using a web address (URL) that points straight at your address points. It **does not** open or read a Web Map. This guide explains the difference and shows you exactly where to find the URL we need. --- ## Server Types We Can Use We can query any service that exposes your address point data. In order of preference: - **FeatureServer** (preferred): the most common type for hosted address point layers. - **MapServer**: also supported. - **GeocodeServer**: also supported. The only real requirement is that it's an **address point layer published through one of these services.** What we **cannot** use is a **live Web Map** or a **shapefile**, because neither is a queryable address service. --- ## Why We Don’t Just Use a Web Map Here's a helpful way to think about it. A **Web Map** is like a custom Google Map you've built with pins dropped on it. It's a **view**: a nicely arranged picture assembled for people to look at. But those pins come from a **data layer** stored separately behind the scenes (think of it like the spreadsheet or database the pins are pulled from). The Web Map just **displays** that data; it isn't the data itself. Our integration needs to **look up addresses in the underlying data layer directly** (the same way you'd search a list for a name) rather than opening the map and reading pins off the screen. So instead of a Web Map, we need the direct web address of the **address point service layer.** --- ## Why a Boundary Polygon Won't Work Many organizations have a **boundary polygon** on hand (city limits, a district outline, or a service-area shape), and it's natural to assume that's what we'd use to check residency. Unfortunately, it won't work for this integration, and here's why. The integration verifies residency by **matching the pieces of an address** (street number, street name, ZIP code, and so on) against those same fields stored on each record in the layer. In other words, it looks the address up in a list. That only works if the layer actually contains a list of addresses to match against. - An **address point layer** is exactly that: a list of individual addresses, where each point carries fields like **street number**, **street name**, and **ZIP code**. There's something for every part of the address to match against. - A **boundary polygon** is a single **shape** that outlines an area. It stores information **about the area as a whole** (a district name or ID, for example), but it does **not** contain a list of the addresses inside it, and it has no street-number or street-name fields to search. There is simply nothing for the integration to match an address to. Here's the analogy: an address point layer is like a **guest list** you can look a name up on. A boundary polygon is like a **fence drawn around a neighborhood**: it shows you where the neighborhood is, but it doesn't tell you who lives there. Answering "is this address inside the boundary?" is a different kind of question entirely. It would require first converting the address into an exact map location and then testing whether that point falls inside the shape, a geographic step this integration doesn't perform. Our tool does a straightforward field match against address records, so it needs a layer made of **address points**, not boundaries. --- ## The Three Pieces and How They Relate Inside your ArcGIS organization, these are different things: ```plaintext Your ArcGIS Organization | |── Feature Layer  ← the actual address point DATA (this is what we query) |     └── Service URL  ← the direct web address of that data (this is what you send us) ) | | └── Web Map  ← a VIEW that may display the feature layer (NOT what we need) ``` The key takeaway: **a Web Map is a view; a Feature Layer is the data.** We need the data layer's Service URL. --- ## Find the Service URL (ArcGIS Online) 1. Sign in to **ArcGIS Online** and open **Content**. 2. Find the item for your address points and confirm its **type is "Feature Layer"** (it will say “Feature Layer” or “Feature Layer (hosted),” not “Web Map”). This is the single most important check: if the type says Web Map, it's the wrong item. 3. Click the item to open its **Overview** page. 1. Look at the right-hand side of the page for the **URL** section, and click **Copy**. It will be similar to: ```plaintext https://services1.arcgis.com/AbCdEf123456/arcgis/rest/services/Address_Points/FeatureServer ``` 2. Add the **layer number** to the end. A single service can contain several layers (for example: address points, parcels, roads), each with its own number starting at 0. For the address points, that's usually: ```plaintext .../FeatureServer/0 ``` If you're not sure which number is for the address points, see the [Confirm You Have the Right URL section](/recreation-management/docs/arcgis-guide-finding-your-address-point-service-url#confirm-you-have-the-right-url). The final URL you send us should resemble: ```plaintext https://services1.arcgis.com/AbCdEf123456/arcgis/rest/services/Address_Points/FeatureServer/0 ``` --- ## Using ArcGIS Enterprise or Portal If you use ArcGIS Enterprise or Portal, the steps are the same (open the Feature Layer item and copy its URL), but the address will point to your own organization's server rather than arcgis.com. It will be similar to: ```plaintext https://gis.yourorg.gov/server/rest/services/Hosted/Address_Points/FeatureServer/0 ``` --- ## Confirm You Have the Right URL Paste the URL into a web browser (leaving off any extra text after the layer number). You should land on a plain, text-heavy page called the **ArcGIS REST Services Directory**. On that page: - The title/breadcrumb should show a `FeatureServer`, `MapServer`, or `GeocodeServer`. For a FeatureServer or MapServer, this is followed by a layer number (for example, `FeatureServer/0`). If instead the link opens a Web Map or an item page, it's not a queryable service, and we can't use it. - You'll see the layer's **name** (confirm it's your address points) and its list of **fields**. - At the very bottom, there's a **Query** link. Clicking it lets you run a quick test lookup, which is exactly the kind of request our integration makes. If the page loads and shows your address point fields, you've got the right URL. --- ## What to Send Us Please send: 1. **The full Service URL.** For a FeatureServer or MapServer, include the layer number at the end (such as `.../FeatureServer/0`). A GeocodeServer URL won't have a layer number. 2. **Confirmation of who can access it.** The integration can only query the layer if it's allowed to reach it. Either the layer needs to be shared so it's reachable, or you'll need to provide credentials or a token so we can connect securely. If you're unsure how the layer is currently shared, let us know, and we'll walk you through it. --- ## Common Mix-Ups to Avoid - **Sending a Web Map link instead of the data layer.** A URL containing `item.html?id=...` or `webmap=...` is a Web Map or item page, not a service. We can't query those. The one we need is a service URL (for example, one ending in `/FeatureServer/<number>`), not an item or webmap link. - **The wrong layer number.** If a service holds multiple layers, `/0` might be roads and `/2` might be address points. Confirm the layer name in the REST Services Directory before sending. - **A private layer with no way in.** If the layer isn't shared and no credentials are provided, the lookup will fail even with a correct URL. See the [What to Send us section](/recreation-management/docs/arcgis-guide-finding-your-address-point-service-url#what-to-send-us). - **Sending a shapefile or a live Web Map instead of a service.** A shapefile (a `.shp` file) and a live Web Map aren't queryable address services, so neither will work. We need an address point layer published as a `FeatureServer`, `MapServer`, or `GeocodeServer`. --- ## ArcGIS Endpoint Submission Form > [!WARNING] > Note: > > Only submit this form if you have paid for the [ArcGIS Integration](/recreation-management/docs/arcgis-integration). Please complete and submit the [ArcGIS form](https://implementation-civicrec-customer-forms-implementation-internal.app.transform.civicplus.com/forms/27907) to set up your ArcGIS Integration. Once the form is submitted, you or your GIS representative will work with our Analyst to finalize the integration and test confirmed addresses. --- ## Questions? [Reach out to CivicPlus Support](/recreation-management/docs/contact-civicplus-support), and we'll help you locate the correct URL. ArcGIS is a comprehensive, cloud-integrated geographic information system (GIS) platform. Uniform Resource Locator Identification or Identifier. Geographic Information Systems. A computer system for capturing, storing, checking, and displaying data related to positions on Earth's surface ## Related - [ArcGIS Integration](/arcgis-integration.md)