Latest Contributions by EricAnderson17

Right, the documentation I sent above makes a pretty good use case - "This will ensure that you don't miss a potential match because the data isn't 100 percent up to date." However, if you are good about keeping your reference data up to date, then keeping the "Match out of range" option set to False/No should continue to work well for you.  ... View more

That's correct. Most of the locator properties exposed in the UI can be modified from the *.loc file. ... View more

Got it! Yes you are correct, these properties can only be modified once the locator has been created, there is no option to do it within the Create Locator tool. You should be able to change them from the *.loc file as well using a text editor: ... View more

Hi Joe, The "Match out of Range" option allows you to still get a successful match even if the address is out of the designated house number range but still falls within a reasonable threshold.  Tips for improving geocoding quality—ArcGIS Pro | ArcGIS Desktop  This would most likely require a little investigation. I tested this out on my end and can confirm that a house number which falls out of range is successfully returned as a candidate from both the Locate pane and Rematch Addresses pane.  Have you tested this with other addresses within the same locator? What about with a different locator all together?  Best regards, Eric ... View more

Hey Joe, (will always sing that in Hendrix's voice) Can you clarify what you mean? You should have the ability to modify the Minimum Match Score and Minimum Candidate Score from the locator properties like you always have: I do like your idea about having different minimum match/candidate scores for different roles within a single multi-role locator. Is this something you've put on our ArcGIS Ideas page? -Eric ... View more

Interesting find Joe! Is this a project you've been using for a long time? Out of curiosity, if you remove the locators using a different workflow (removing them from the Locators folder in the Catalog pane), does that cause the same issue?  ... View more

Hi Joe, Certainly not expected behavior. Can you please confirm your exact version (2.4.1, 2.4.2)? I tested this with ArcGIS Pro 2.4.2 and it seems to behave as expected for me - 11.15.2019-10.03.33  Are all the locators you are removing built with the Create Locator tool, or is it a mix of locators and address locators?  Can you reproduce this with any mix of locators added to your project? Any particular order needed to reproduce?  Thanks! Eric ... View more

Hi Jamal, If you go to Project > Open, it should list all your recent projects with their full pathway. The project you have open will be listed at the top: Hope this helps! Eric ... View more

Hi Marc, Can you provide a screenshot to better illustrate the issue you are having?  There's a handful of fields that get created in the output of the Reverse Geocode tool, including "REV_Street", "REV_City", etc. (if you turn off option to display field aliases). Are you saying the only field that gets returned with meaningful values is "REV_Match_addr" and every other field created by the Reverse Geocode tool (REV_*) has null values in it?  You state the locator was created in ArcGIS Pro, but based on the fact that you're using it in ArcMap as well, I assume you built it with the Create Address Locator tool, and not the newer Create Locator tool. Would you be willing to test building a new locator with the Create Locator tool and see if the behavior is better?  Create Locator—Help | ArcGIS Desktop  -Eric ... View more

Hi Robert, To help clarify, the StreetMap Premium new locators are already designed to work "offline". They are local, file-based locators, and do not require any sort of internet connection to access or use them (like the World Geocoding Service). However, as you stated, they do require an ArcGIS Pro StreetMap Premium extension, which is noted here: StreetMap Premium licensing requirements—StreetMap Premium for ArcGIS | ArcGIS Enterprise  It sounds like you are using a Named User license, have you looked into options of taking your ArcGIS Pro license offline or switching to another licensing model like Single Use? I think this question could really be rephrased to ask what's the best approach for using an ArcGIS Pro extension offline.  -Eric ... View more

Hi Phil, By "if you build the locator without zones", I meant if you run the Create Locator tool without specifying any zonal fields (city, state, postal, etc.) in the field mapping (only house number + street name).  If you build the locator without specifying any zonal fields in the field mapping, that's when the supportsOptionalZone parameter gets automatically applied to the *.loc file. If you did build the locator with a zonal field (which it sounds like you did with the city field), this setting is not applied and must be manually added if you attempt to search for an address without one of those three things I mentioned earlier (admin zone, location parameter, or extent).  Again, we are definitely working on getting an enhancement logged so these settings will be exposed through the UI. Manually adding that "supportsOptionalZone = true" line to the *.loc file is just a solution for now until that gets reviewed and hopefully implemented. Best regards, Eric ... View more

Thanks for following up and closing the loop on this one Phil. From what we found, by default you need either an admin zone (city, state, postal code), a location parameter, or an extent to return a successful match. For the new locators (those built with the Create Locator tool), if you build the locator without zones, a property will automatically get added to your locator and set to true (supportsOptionalZone = true). This property is not exposed in the properties UI currently but can be manually added to the locator *.loc file as you stated above (simply edit with Notepad and add that "supportsOptionalZone = true" line to the bottom).  We're going to work on making sure we get an enhancement logged so this setting will be exposed through the UI so the manual change to the *.loc file would not be necessary. Having this property exposed through Python is also a great suggestion. I'll follow up about the Snickers bars 🙂 Thanks for the discussions on this and helping us improve the product! -Eric ... View more

Hi Phil, To expand on my previous message, looking at more information about the "location" parameter (documentation is for the World Gecoding Service, but the principles are the same), I see this following note: The location parameter can be used in place of administrative zone (city) or postal code in an address search, as long as a matching address exists within 50 kilometers of the input location. Consider the following example. 251 Vesey St, New York, 10282 is an address in Manhattan, New York City. Coordinates -74.006,40.71437 represent a point within central Manhattan, less than one kilometer away from the address. If you search for "251 Vesey St"(no city or postal) with location=-74.006,40.71437included in the request, a match to 251 Vesey St, New York, 10282 is returned. However, if instead you search for"251 Vesey St" with a location value in Washington, DC (350 kilometers away) an address match is not returned. findAddressCandidates—ArcGIS REST API: World Geocoding Service | ArcGIS for Developers  So because ArcGIS Pro is including this location parameter, the city name is not required. Therefore, this may be expected behavior but it may be good to still log that Support case so we can confirm fully and document this for future users who may have this same question/issue.  Best regards, Eric ... View more

Got it, thank you for the clarification Phil! I'm seeing the same thing on my end with a Point Address locator I created in Pro 2.4 and published to Enterprise 10.7.1.    What's odd is if you bring that geocode service into ArcGIS Pro (Catalog pane > Portal tab), it behaves the same way as the local locator and allows you to search for the address without a city. So it seems like only when submitting a request directly from the REST end-point of the service is the city name required.    From what I can tell from Fiddler, the difference is that the request from ArcGIS Pro includes a "location" parameter, while the request from REST does not (unless of course you specifically include one). If I take the "location" parameter and simply include that onto the REST request, it is successful.    I'd say we have enough here to investigate this a little more thoroughly and I would definitely recommend following up with that Support case. If you want to reference this GeoNet post, I'd be happy to link up with the analyst who takes ownership and pass on my testing notes.   Best regards, Eric ... View more

Hi Phil, Can you expand on what you mean by "When using geocoders on 10.7". Are you using ArcGIS Desktop 10.7? ArcGIS Enterprise 10.7? You stated you used the Create Locator tool in ArcGIS Pro 2.4 and when used in ArcGIS Pro 2.4 you "get good returns". So where exactly are you seeing the issue with no matches being returned without a city? Can you provide any relevant screenshots? Thank you, Eric ... View more