Latest Contributions by BradNiemand

Theodore, Suggestions for intersections is supported for locators created with your own data if the locator is built using the Create Locator tool in ArcGIS Pro. Brad ... View more

Liz, Unfortunately I am not of much help here.  You are working in an area where I have no experience. Maybe this thread will help though? https://community.esri.com/thread/114287  Brad ... View more

Robert, You would need to make pure REST calls via Python if you want to go that route.  Victor Bhattacharyya‌ could potentially help you with that because he has done this quite a bit. Brad ... View more

Kyle, Your statement that "Reverse geocoding does not work at all when mixing new locators and composite locators" is not correct.  The composite locators function and return results correctly but you will have less output than you would when using the new locator by itself.  This is how the classic locators worked and how the classic locators inside of composite locators worked.  With the composite locator that contains the newer locators created with the Create Locator tool, you will only get back the parsed out address for the reverse geocoded location instead of additional geocoding metadata that the mutlirole new locators return. Brad ... View more

Robert, Let me answer some of you questions. 1. Documentation for the output fields when using the ArcGIS World Geocoding Service are documented at the service like you mentioned.  The ARC_ fields contain the values that were mapped when you originally geocoded the table and the ArcMap documentation for that can be found here: About geocoding a table of addresses—Help | ArcGIS Desktop  ResultID is a field that is returned using the REST API but not when geocoding in Desktop.  It is used to "stitch" the original table onto the results from geocoding. As for your following statement    "Oh, and BTW, the documentation has a comment to the effect that the user cannot rely on the number and names." This is referring to the values in the fields that can change.  Data changes all the time so you can't base application logic on it.  The field names won't change but the values might. 2. We return a consistent set of all fields when geocoding so even empty fields will be returned.  When using the REST API directly, you can choose which fields will be returned by specifying the outFields parameter but we return all of them when geocoding using Desktop.  Information about the arc_ fields can be found in 1 above. 3. The length of the fields that are returned are based on the data we have.  In some cases, in some countries, the values can be quite long so we need to take that into account.  ArcGIS Pro sets the default width to something smaller than the max so I would encourage you to try it out. 4. The fields in the output are a copy from the original table that are appended to the geocoding result which is why their name is changed.  If you geocoding in ArcGIS Pro that will be named USER_<fieldName> with a field alias that has the same field name from the original table. 5.  What field was it that caused this issue? ... View more

Kevin, Adding support for suggestions for Subaddresses is on our list of work that we will be doing but it will not be in 2.4.4 nor will it be in 2.5 which is already dev-complete and will be release in early 2020. I would like to provide some detail and background about the two operations, suggest and findAddressCandidates. FindAddressCandidates is intended to be used with full addresses, not partial addresses.  It does support partial addresses if the entire address portion is entered but the zones (city, state, zip) are excluded ONLY when you pass in either a location or an extent as a parameter to the API.  Using either the location parameter or the extent parameter allows users to search without providing a zone.  Another way to allow for no zones to be entered is to set the property I mentioned to you above, supportsOptionalZone = true, although this property was not implemented prior to 10.7 Enterprise so it would require that version or newer. Suggest allows for not only partial address input but partial word input as well.  You can enter "110 East St" (to use your example above) and get suggestions back that match that text input.  The two operations are performing completely different functions but do work together hand in hand.  The result returned from the suggest operation is passed in as input to the findAddressCandidates operation to give the user the address they asked for so if you were to pass in the text that you got back from the suggest call of which is "110 E STATE ST, SAVANNAH, 31401" you will actually get back the correct result. The workaround that you are using to get suggestions back by using the Gazetteer will have limitations that you have mentioned above because that is not the intended use of that locator. As mentioned above, we recognize that suggestions for Subaddresses is a feature that is important to your workflow and we are working hard to get that feature to you in a future release of Pro and Enterprise. Brad ... View more

Kevin, This issue is not specific to the locator actually, it was something in the Enterprise framework code so the type of locator or where you publish it from doesn't matter. Brad ... View more

Kevin, This issue was already fixed in 10.7 Enterprise. Brad ... View more

Joe, There is not a really good answer for this.  It depends on a lot of factors but the best way to think of it is that it is random. Brad ... View more

Joe, The center of the map is only used when performing interactive geocoding, not batch geocoding.  What you are seeing is just a coincidence because when batch geocoding it will just choose the first candidate if there is a tie. Brad ... View more

Michael, If the addresses have the same attributes and are from the same role then all of them will be returned.  The first one will just be the closest to the center of the map.  Even if the addresses have the same attributes but are from differnt roles and are not spatially near each other, all the candidates will be returned. The logic for deduplication of identical candidates happens when you have identical attributes across different roles where the locations are very close to each other.  Essentially we want to remove the StreetAddress match if we have a PointAddress match that represents the same address but with a more spatially precise location. Brad ... View more

Joe, Likely the limitations you are seeing are because of the older version of the software.  Please let me know once you have tried it against 10.7.1. Brad ... View more

Joe, Does your locator have any zones (city, state, postal) built into it and if you do, are you trying to search with no zones?  If not I think this might be what you are running into with 10.6.1.  10.6.1 was released prior to the Create Locator tool so the only locators that could be used with it at the time were the World locator and locators from StreetMap Premium.  The functionality to support locators with no zones was not added until after 10.6.1. The only way around this is to ensure that you are zoomed in past 1:500,000 so that location is passed in. Brad ... View more

Joe, Do you have the patch installed? ArcGIS Server 10.6.1 General Geocoding Patch  There is nothing specific to the behavior you mentioned above in this patch but it would be good to install anyway. Brad ... View more