Latest Contributions by ShanaBritt

What version of ArcMap or ArcGIS Pro are you using? What version is the USAddress.lot.xml that you are referencing? It should say at the top of the XML file. ... View more

Larisa: It is possible to search for the intersection using a spatial offset, but the input address needs to be in the following format: [distance] [units] [direction] from [address] for example 25 meters N from  juniper st ne & 6th St ne, atlanta You would need to use the Field Calculator to populate a new field in your table with the spatial offset and intersection addresses using the above format. Then the new field could be used for batch geocoding. About finding an address—Help | ArcGIS Desktop  About finding an address—ArcGIS Pro | ArcGIS Desktop  ... View more

What version is your ArcGIS Server? Can you see the geocode service that you added to your ArcGIS Online as a utility service in the MapViewer as an option to search for locations? Are you able to insert a new ArcGIS Server connection in Pro to your ArcGIS Server and add the service to the Project in ArcGIS Pro? Add locators to a project—ArcGIS Pro | ArcGIS Desktop  Which version of ArcGIS Pro are you using? -Shana ... View more

In ArcGIS Pro 1.4, if the map units of the map view is set to meter and you enter the coordinates into the search box of the Locate pane you will get candidates returned from the XY Provider. Below is an example of the results from version 1.4. ... View more

Erika: This behavior is not reproducible in ArcGIS Pro 1.4 with an address locator created in ArcGIS Pro 1.4. Are you still encountering this behavior if you have upgraded to ArcGIS Pro 1.4? ... View more

Alex: Does the geocode service work as expected in the ArcGIS Online map viewer if it is added as a utility service in your ArcGIS Online Organization? ... View more

Alessandro: Is it not possible for customers to use the address locators included with StreetMap Premium Europe? ... View more

Husham, did the article resolve the use case you described in your original post? Did you use the gridid as a zip or city when building the address locator? ... View more

Joe: The ‘Match with no zones’ parameter in the Geocode Options properties is still set to ‘No’ by default at versions 10.4 and 10.5. The default design of the locator is to not return match results when you build the locator without zones and do not include zones with the input address because of the performance cost when having to search through the entire index of the reference data to return multiple candidates, which would take longer to do. Of the multiple candidates returned, there may be many that are correct. You wouldn't know which is the correct candidate to be matched if you didn't have a zone. The performance hit would be really significant for larger geographies, but I know a lot of customers create local locators for their city or county and create them without referencing a zone cause it's all the same. But, just about every city has a Main St… how do you know which Main St is correct if the county has multiple cities and they all have a Main St? Or like in Chicago, IL, the street Lake Shore Drive spans 15 differen t zip codes. ... View more

Joe: I haven’t heard too much yet and what I have heard was about the output fields and wanting to know what they mean. -Shana ... View more

Mikkel: Do you also encounter the same behavior in runtime if using the Single Field style with the intersection points? Just to clarify when you tested the composite and individual Gazetteer locator in ArcMap was that with the local locator or the geocode service via an ArcGIS Server connection? Do you encounter the same behavior when using the composite or solo Gazetteer in ArcGIS Pro? -Shana ... View more

Have you tried using a Dual Range locator based on street lines for the intersections rather than a Gazetteer for the intersections and use the Dual Range in runtime? The Gazetteer style was not intended to address intersection searches and the geocoding rules associated with the Gazetteer style expect an exact match. Do you encounter the same behavior when the Gazetteer is the only locator used in runtime?  ... View more

Courtney: In order to determine what is causing the problem with the alternate name matches I would need to see the address locator properties that show the field mapping in the Reference data section of the locator properties dialog. One technique that I use to determine if the JoinID is working correctly with the primary feature class and alternate name table is in ArcMap create a relate between the feature class and the alternate name table based on the JoinID used when doing the field mapping when creating the address locator. Then search for the primary address with the Find Tool (locations tab) and use the Identify tool to click on the feature the address was matched to. The Identify Results window will show the related records to that feature so that you can see the associated alternate street name. ... View more

George, Is this still an issue with a more current version of ArcMap like 10.3 or higher? ... View more