Latest Contributions by ShanaBritt

‎07-15-2016

If you upload the csv directly to the map in the ArcGIS Online map viewer you will not get the option to select the geocoder you'd like to use, the default one will be used. If you upload the csv for geocoding using the Add Item method you will have the ability to select the geocoder you would like to use. If you use the Add Item method of geocoding the csv you have the option to publish the resulting geocode results as a hosted feature layer at the same time as uploading it to your ArcGIS Online organization. The hosted layer can then be used in multiple maps. If you add the csv to the map a feature collection of the addresses is created and stored with the web map. Feature collections can be saved as a layer and then published as a hosted layer and this method requires more steps than just adding the csv as an item in My Content.

‎04-29-2016

Marc: Do you get the same behavior with the Reverse Geocode tool with Intersection in ArcMap 10.3 as well? Are you using ArcGIS Pro that was included with ArcGIS Desktop 10.3? If you look in the Control Panel, what is the actual version of ArcGIS Pro? What type/style of address locator are you using with the Reverse Geocode tool? Are you able to provide the points and locator for review to help determine what might be going on? -Shana

‎02-24-2016

Jeremy: You can now get the World Geocoder for ArcGIS. World Geocoder: Put Addresses and Places on a Map -Shana

‎02-16-2016

Joe: Since it's going to be a licenced product package, it is separate from ArcGIS Online and will have different pricing. The World Geocoder for ArcGIS is not limited to those who currently use the World Geocoding Service that is included with the ArcGIS Online Organization subscription. -Shana

‎02-16-2016

Jake: I would suggest going through the steps outlined in the following technical article, 40678 - Dual Ranges address locators created with ArcGIS for Desktop 10.1 and higher do not return matches. -Shana

‎02-16-2016

Sean: I would suggest going through the steps outlined in the following technical article to disable coordinate search when using the address locator. 44182 - Disable finding latitude and longitude coordinates when using an address locator -Shana

‎02-16-2016

Raffi- Does the behavior occur when using the out of the box General - Single Field locator style to create the address locator? What modifications were made to the style you used to create the locator that is exhibiting the unexpected behavior? -Shana

‎02-12-2016

Jeremy: The World Geocoder for ArcGIS is targeted to be available Q1 2016 and will be a licenced package with 3 different licence levels, so there will be a fixed cost, that consists of ArcGIS for Server, Data (locators) and Professional Services. The basic licence has a limit of geocoding 250M records per year. It will include a ready-to-use Geocoding API that you can use right away in ArcGIS apps or configure into custom apps. The key capabilities are Interactive Geocoding (GeoSearch), Batch Geocoding, Reverse Geocoding, and Suggestions (results as you type). For more details feel free to send your questions to [email protected]. -Shana

‎02-12-2016

Peter: Is the behavior only occurring at REST with the parcel based locator? What is the behavior when batch geocoding in ArcMap with the original unpublished address locator? If you are able to provide the parcel data and existing locator I can take a look at the behavior to try and provide some insight. -Shana

‎02-12-2016

Jeremy- What you've described is similar to suggestions that can be seen when using the World Geocoding Service in ArcGIS Online or via REST. It is possible to create an address locator at version 10.3+ with suggestions, but in order to use the suggestions the locator must be published to ArcGIS Server 10.3+ and the geocode service will allow you to use suggestions via REST. The geocode service could be used in ArcMap, but suggestions are not supported in the Find tool or Geocoding toolbar in ArcMap. Currently in ArcGIS Pro using the Locate pane you can see suggestions from the World Geocoding Service. At this time the only other offline options would be to use StreetMap Premium locators, which have suggestions built in for the 2015 Release 2 products, so if you were to publish them as geocode services to ArcGIS Server 10.3+, you would be able to make use of suggestions via REST. A local version of the World Geocoding Service called World Geocoder for ArcGIS will be available in the near future for organizations to use offline and behind their firewalls. -Shana

‎02-01-2016

Srijana, The following technical article provides a permanent solution. 40678 - Dual Ranges address locators created with ArcGIS for Desktop 10.1 and higher do not return matches You should also find my response in the following thread helpful as well. Re: Geocoding -- 10 vs 10.1 -Shana

‎01-25-2016

Carole: I have checked out the information you have provided and the responses in this thread and wanted to know what the name of the geocode result was and the data format, as well as, the version of ArcGIS Desktop you are using when the error was returned. I'm also curious to know if you receive the same or similar error when using the Geocode Addresses tool from ArcToolbox > Geocoding toolbox and use the World locator from the Ready-to-use-services > Geocoding in ArcCatalog when singed into ArcGIS Online. You may also want to try to save the spreadsheet as a csv file and geocode it in ArcMap. I did not getting errors geocoding the spreadsheet you uploaded in ArcMap either. -Shana

‎01-25-2016

Andrell: Are you able to provide the table that you are geocoding along with the address locator and data used to build the locator? This will help to troubleshoot the behavior you encountered. -Shana

‎01-07-2016

@David: These scenarios are addressed with the out of the box US Single House Subaddress style that was included with ArcGIS for Desktop 10.3+ and Pro. 2 out of 3 of the scenarios work at 10.3.1 and all 3 scenarios work at 10.4. The address 'A652 N Placer Way SW' is related to a bug that was submitted for 10.3 or 10.3.1, where the prefix direction is getting parsed as the address number suffix and times out and not candidate is returned or something with a score lower than 100. If the input address does not include the prefix direction a match is returned with a score less than 100. There are other threads that reference this bug and other bugs related to the Single House Subaddress style. Single House Subaddress Locator Issues - Possible Bug? Using Single House Subaddress Style Address Locator I've attached a locator package that includes the reference data if you would like to see the behavior and settings used. Use the Extract Package tool in ArcToolbox to extract the locator package and layer package. -Shana Brad Niemand Bruce Harold

‎01-07-2016

Vicky Are you able to provide a screen shot of the entire field mapping showing all of the primary and alternate table parameters, as well as the Geocoding Options? When I'm testing the alternate name to see why I may not be getting the expected results I add the reference data and the alternate name table to a Map and create a relate using the fields that you would map as the JoinIDs when building the locator. Then use the Identify button on a feature that has an alternate name and check the related info in the Identify Results Window to see if the information is correct. If you would like me to look at your locator and data you can send it to me at [email protected]. -Shana

Online Status	Offline
Date Last Visited	4 weeks ago

My Ideas

Latest Contributions by ShanaBritt

Re: How do I now get our geocoder and the Esri World Geocoder to show up as a choice of two geocoder for our users when they upload a csv to be geocoded?

Re: Reverse Geocoding Not working

Re: Query Address Locator using LIKE % Selection Statements

Re: Query Address Locator using LIKE % Selection Statements

Re: Address Locator Road Centerline US Dual Ranges

Re: Address Locator Returning Lat/Long Values as Candidates

Re: 11 hours trying to solve the Address Locator results mismatch with Additional Field

Re: Query Address Locator using LIKE % Selection Statements

Re: Strange locator behaviour using multiline input

Re: Query Address Locator using LIKE % Selection Statements

Re: Address Geocoding locator for 'US Dual Range Addresses' does not work in 10.2.1.

Re: geocoding error in ArcMAp

Re: Geocoding intersections problem

Re: Geocoding Address Prefix/Suffix elements

Re: 10.2.2 Alternate Names Geocoding Does Not Return Matches

Re: Geolocate addresses tool in arcpy

Re: Composite Locator added to AGOL is no longer G...

Re: Address locator takes 20x longer to rebuild in...

Re: Pro crash-out trying to rebuild address locato...

Re: ArcGIS Server Locator Fails To Geocode Full Ad...