LocateIQ LocateIQ Privacy & Security Sign In

Resources › Getting started with ArcGIS Enterprise

Getting started — ArcGIS Enterprise

Enterprise needs one thing ArcGIS Online does not: an administrator registers LocateIQ on your portal once. After that the layer setup is the same — with one caveat worth reading before you start.

Read this first. Many Enterprise portals restrict who may publish hosted feature services. Where those rules apply, the app's Create New Map and add-a-layer tools will fail — not because of LocateIQ, but because the account is not permitted to publish. Publishing a geodatabase from ArcGIS Pro is the reliable route on Enterprise, and it is route 3 below.

1 Register LocateIQ on your portal — administrator, once

  1. Sign in to your portal as an administrator.
  2. Content › My content › New item › Developer credentials.
  3. Choose OAuth 2.0 credentials, then Next.
  4. Redirect URL — exactly this, no trailing slash:
locateiq://oauth/callback
  1. Application environment: Native.
  2. Privileges / item access: skip — not used for user sign-in.
  3. Title: anything recognisable, e.g. LocateIQ.
  4. Copy the Client ID and give it to whoever sets up the devices.

The redirect URL must match character for character. A mistyped one fails at the very end of sign-in, after the password has been accepted — which looks like a password problem and is not one.

2 Account privileges — administrator

Creator user type with the Publisher role covers everything. For a custom role:

Content

  • Create, update, delete
  • Publish hosted feature layers
  • View content shared with organisation

Features

  • Edit

Sharing

  • Share with groups
  • Share with portal

General

  • View members
  • View groups shared with portal

Publish hosted feature layers is the one that decides whether the in-app map tools work at all. If your portal does not grant it, use route 3.

3 Point the app at your portal — each device

  1. On the sign-in screen, tap Change ArcGIS Configuration.
  2. Client ID — paste the one from step 1.
  3. Portal URL — your portal's base address, e.g. https://gis.yourcompany.com/portal.
  4. Save, then Sign in with ArcGIS.

Signed in but your organisation's maps are missing? The Portal URL is almost always the cause — usually an incomplete portal path.

1 The layers LocateIQ needs

Only one layer is required. The rest are optional and can be added later.

Locate Points

Required

Every locate the app captures. Without it there is nowhere to collect to.

AGM Points

Optional

Above-ground markers and transformation points.

Photo Points

Optional

Geotagged photos captured alongside a locate.

Utility Layers

Optional

Gas, electric, water, sewer, telecom mains and services, plus a dig-area polygon.

Three ways to get the layers in place

On Enterprise, start at route 3 if your portal restricts publishing.

In the app · needs publish rights

Create New Map

LocateIQ builds a web feature service with Locate Points, AGM, Photo Points and the utility layers, then creates a web map and assigns them.

Blocked by portals that do not allow hosted-service publishing.

In the app · needs publish rights

Import an existing map

Import a web map from your portal, then add Locate Points (and optionally AGM and Photo Points) as a separate new service added to the map, or as new layers in the service the map already uses.

In ArcGIS Pro · most reliable

Publish a geodatabase

Publish the ready-made file geodatabase from ArcGIS Pro to your portal, then import the resulting map in the app. This path needs no in-app service creation, so portal publishing rules do not get in the way.

Full bundle — GDB + README + symbology (.lyrx for Pro).

Locate Points only + AGM & Photo Points + utility layers

Uploading through the portal browser instead? Use the GDB-only builds:

Locate Points only + AGM & Photo Points + utility layers

The layer must allow editing — Create, Update and Delete. A read-only layer imports and draws perfectly, then silently never receives a locate.

4 Test sign-in from outside the building

Crews sign in over cellular. An internal-only portal, a VPN requirement, or a certificate your devices do not trust will all block sign-in in the field. Test on a phone with Wi-Fi off before a crew finds out for you.

5 Collect one locate and check it arrived

Capture a point, then open the layer in your portal. One successful round trip proves the whole chain — OAuth, portal URL, privileges and layer editability.

On ArcGIS Online instead? → Schema reference & downloads → Training guide → Something not working? →