WorkForce showing wrong address

[BrianBulla1]

Hi,

In my Dispatcher webmap, I have a layer with proper addressing information which we use to create Assignments.  I have configured the Pop-Up for this address layer to show the properly formatted address when I click on the point.  For some reason when clicking on the point in WorkForce, it adds it's own address to the Pop-Up when viewing the webmap in WorkForce.  See screenshot below:

Where is this second address coming from?  Is there a way to disable it from showing??  It's causing a bit of confusion.

Thanks,

[JoeBorgione]

Does your web map have an underlying base map (like one from esri) that has building footprints with addresses?

[BrianBulla1]

Yes, it has an underlying base map, but not one of esri's.  It's a tiled raster service, so it should not be providing any information about addressing.  And if for some reason it was providing addressing, it should be the same as our address points.

Is this address coming from some sort of esri geocoder perhaps??  I know when I use the "Find an Address or place" button in WorkForce it never brings me to the right spot.

[JoeBorgione]

Is this address coming from some sort of esri geocoder perhaps??  That's a good thought.  Look at the find address or place pull down; it defaults to 'all'  My org has a couple of our own locators published to AGOL, so I like to point to ours only, and not ESRI's (all)....

[BrianBulla1]

I know what you mean by the 'pull-down' but in the WorkForce interface, there is no pull-down on the map:

It only allows for typing an address.  No choice of geocoder.

[JoeBorgione]

Rats! I was thinking  AGOL map.  Is there some sort of configuration file in WorkForce you can alter? (or at least examine to see if it's the culprit)

[BrianBulla1]

Hi Joe,

No, from what I can tell, in Workforce there isn't much that you can configure.  It just does stuff, but with few configuration options.

It must have something to do with geocoding, since other addresses I click on also come up with that same wrong address of 2351 as in the first screenshot above.

[JoeBorgione]

As painful as it might be, I suggest a call to Tech Support; it'll probably take some time as the 'first responder' won't know exactly how workforce geocodes, but eventually, some one higher up on the food chain will know...

Good Luck!

[JoeBorgione]

I just did a google search on 'arcgis workforce geocode' that took me here. It appears to be tutorial for Managing Workforce for ArcGIS Projects using the Arcgis API for Python. I'm not sure if you used the API and Jupyter Notebooks to put your project together, but this page uses the geocode() function which lead me to another page.

It goes through the parameters of the function and 'geocoder' is optional. This is how it describes it:

geocoder - Optional, the geocoder to be used. If not specified, the active GIS's first 
geocoder is used.

Which in my mind goes back to what I first alluded to.  What locator does your AGOL default to?

Hope this helps.....