Latest Contributions by ShanaBritt

Kathleen: The results were the same using all three methods and spelling out the subaddress element types returned the expected results. Entering a different unit type from the reference data returned matches as well. If you’d like to see the locators I built I can send them to you off the thread. -Shana ... View more

Kathleen: Changes were made to improve performance and match rate. The address prefix and suffix elements should be combined with the address number to be represented as the house number. In the data you provided you would use the CompAddNum field for house number when creating the address locator. The subaddress elements for building and unit has been consolidated into one set of subaddress elements that supports multiple combinations. In the data you provided you could use the CompSubAddress field for SubAddr Unit when creating the address locator. The reference data can be formatted in the 3 ways in the screenshot below for subaddress elements. When I compared a subset of the data you provided approx 70k records and compared the results of 10.4.1 to 10.5/10.5.1 and there was a 19% improvement in the number matched The following link is to the Single House Subaddress style in the documentation. Commonly used address locator styles—Help | ArcGIS Desktop<http://desktop.arcgis.com/en/arcmap/latest/manage-data/geocoding/commonly-used-address-locator-styles.htm#ESRI_SECTION1_7FC7CD744FDA4D379399C92D109FA67A> You can continue to use the 10.4 style in 10.5, but will be missing out on the improvements to the style that were made. We are still in the planning stages for future releases so I cannot say at this time what Subadress will look like in future releases. ... View more

Is this still an issue if using ArcGIS Desktop version 10.3+ and the US Address - Single House Subaddress style to build the address locator? ... View more

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