Latest Contributions by ShanaBritt

Jessiecar: Do you have examples of the addresses that are matched to the wrong location when compared to Google? Which StreetMap Premium product and version/year are you using? TomTom or HERE/Navteq? Is the setting of 80 for the minimum match score? Are you using the address locator in ArcMap? As a geocode service? -Shana ... View more

Jessiecar: Is the USAZip4 locator that you are using one that was included in the StreetMap Premium for ArcGIS product? I’m still not understanding what you mean about “accurately coordinates of an address to reference data”. Are you looking to get the XY coordinate of the matched address when you geocode addresses with the USAZip4 locator? Are you looking for the reference data that was used to create the USAZip4 locator ? Are you able to provide an example of what you are trying to get? ... View more

Jessiecar: Could you elaborate more on what you are trying to accomplish? Are you searching for house addresses? What type of address locator are you using? Are you looking for spatial data that can be  used to build an address locator in the US? -Shana ... View more

Could we maybe get a new locator that does default to no zones?  I just have no reason to use them as my addresses are only with my city and don't cross county or state lines.  I do use Left/Right City though.  Also the zones, does this only work for Zip codes?  Could we just use the Left/Right City as the zone by mapping the zipcode fields to these? Josh: The default setting of the address locator for the 'Match with no zones' property is 'No', which means that if no zone (zip, city, community..) is not included when you build the locator or part of the input address, no matches will be returned. The article "Dual Ranges address locators created with ArcGIS for Desktop 10.1 do not return matches" provides a permanent solution that modifies the USAddress locator template to make 'Yes' the default setting so you don�??t have the change the properties of every locator after you create it. Making the permanent change as described in the article would not require that a new locator template be provided and you could create the address locator with just the house number ranges and street components without a zone. In this case the input address for the locator the house number and the street, for example,  "380 New York St". If you used the default option and used Left/Right City as part of the field mapping to the city zone when building the locator, you would need to include the city as part of the input address when using the address locator. You could map community name to the city zone component instead of city and that would meet the zone requirement for the locator when using the default setting of 'No' for the 'Match with no zones' property. I hope this clarifies things for you. -Shana ... View more

The behavior you described does fit NIM081790, which has also been discussed in the thread titled Geocoding-10-vs-10.1. I recently posted a response to a question about whether this bug will be fixed or not. Please see my response at http://forums.arcgis.com/threads/61960-Geocoding-10-vs-10.1?p=284440&viewfull=1#post284440. -Shana ... View more

I have SP-1 with 10.1 and I still have the problem with address locators and having to tweak the Geocoding options.  Will there be a fix? Thanks jj There are no plans to change this default setting, as this is by design. 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 different zip codes. The article "Dual Ranges address locators created with ArcGIS for Desktop 10.1 do not return matches" provides a more permanent solution that modifies the USAddress locator template to make 'Yes' the default setting so you don�??t have the change the properties of every locator after you create it. The match with no zone setting was also discussed in the Geocoding -Advanced Techniques technical workshop at the 2012 International User Conference, which can be viewed in the demo  between time frame 20:49 -  20:06. The corresponding slides for the time frame in the demo can be found at http://proceedings.esri.com/library/userconf/proc12/tech-workshops/tw_2022.pdf starting at Managing Performance. I hope the above information helps and if it does not, please submit a request to Technical Support. -Shana ... View more

This IS NOT fixing my basic dual range geocoder that works in 10...  Big Bummer.  I guess I better alert my co-workers! I would suggest contacting Support to have a look at your address locator created at version 10 to see why it is not working in 10.1. Doesthe problem persist if the address locator is recreated at version 10.1 and changing the 'Match with no zones' property? -Shana B ... View more

Starting at ArcGIS Desktop 10.1 SP1, the default locator options for geocoding have changed. The only locators that will appear in the default address locators (populated from the DefaultLocators.xml file) after the install of SP1 will be the ArcGIS Online World Geocoding Service, which points to http://geocode.arcgis.com/arcgis/services, and the MGRS Military Grid Reference System locator. The locators pointing to the geocoding services at http://tasks.arcgisonline.com/arcgis/services will no longer be included in the DefaultLocators.xml file after installing ArcGIS Desktop 10.1 SP1. The DefaultLocators.xml file is responsible for populating the list of locators seen in the Geocoding toolbar and the Locations tab of the Find tool. This is expected behavior after installing ArcGIS Desktop 10.1 SP1. A detailed announcement explaining the reasons behind this change in the geocoding process is expected in December. Included with this change is the eventual deprecation of the locators housed at http://tasks.arcgisonline.com/arcgis/services. The goal will be to use the ArcGIS Online World Geocoding Service as a complete solution for batch geocoding and geosearch capabilities. Eventually, the ArcGIS Online World Geocoding Service will be the only option available for online batch geocoding and will require a fee; however, the World Geocoding Service can be used for free in order to perform geosearches using the Find tool and the Geocoding toolbar. In order to batch geocode using the new World Geocoding Service in ArcGIS Desktop 10.1 SP1, an ArcGIS Online Organization subscription is required. For a limited time prior to deprecation, connections can continue to be made to http://tasks.arcgisonline.com/arcgis/services through ArcCatalog or the Catalog window in ArcMap. Below are the steps to make the connection: 1. Start ArcCatalog or open the Catalog window in ArcMap and expand GIS Servers 2. Double-click 'Add ArcGIS Server' 3. Select the default 'Use GIS Services' on the first screen of the Add ArcGIS Server wizard and click Next 4. Copy and paste the following in the Server URL box: http://tasks.arcgisonline.com/arcgis/services 5. Click Finish 6. Once connected you will see two folders, one of them called Locators, where you will find the locators available from this service Once the geolocators at http://tasks.arcgisonline.com/arcgis/services are deprecated, the options for batch geocoding will be reduced to using the fee-based World Geocoding Service, using the locators included with StreetMap Premium data for TomTom or Navteq that are available for purchase, using the StreetMap North America locators on the Data & Maps media that is included with the ArcGIS Desktop 10.1 software, or building a custom locator. Below are links to additional information concerning some of the topics discussed above: Setting default locators in ArcMap http://resources.arcgis.com/en/help/main/10.1/#/Setting_default_locators_in_ArcMap/002500000040000000/. World Geocoding Service. http://geocode.arcgis.com/arcgis/index.html#/Overview_of_the_World_Geocoding_Service/02q000000008000000/ Batch geocoding with the World Geocoding Service. http://geocode.arcgis.com/arcgis/index.html#/Batch_geocoding/02q000000004000000/ ArcGIS Online pricing http://www.arcgis.com/about/pricing.html ArcGIS Online Geocoding Services http://www.esri.com/software/arcgis/arcgisonline/credits/geocoding ArcGIS Online Service Credits Overview http://www.esri.com/software/arcgis/arcgisonline/credits Key Features of StreetMap Premium for ArcGIS http://www.esri.com/data/streetmap/key-features ... View more

The ArcGIS Online address locators that are available in ArcMap are not based on parcel data, so the returned point will get matched to the street segment with a side offset for the side of the street the address is matched to or to where the driveway meets the street if the address is matched using the US_RoofTop locator of the composite online 10.0 North America Geocode Service. The 10.0 North America Geocode Service is a composite address locator and when addresses are matched using the US_RoofTop locator the Disp_Lon and Disp_Lat fields will be populated in the geocode result and represent the centroid of either the building or parcel to which a given address is associated and will not be directly located on a street segment. North American Address Locator (ArcGIS 10 style) If you want to get the addresses to match to the centroid of the parcel, you would have to create an address locator using the Single House style with the parcels as the reference data. I�??d suggest you log something with Tech Support to have someone take a look at your data and assist with increasing your match rate. -Shana ... View more

A colleague of mine in Support and I worked on a Semantics Checker Add-In that can be used in ArcCatalog 10.0, which will give you the capability to check the integrity of the exported XMI or Microsoft Repository with the Semantics Checker. The Add-In can be found at the following link. http://www.arcgis.com/home/item.html?id=e486bc0352a3419687dc660ec9fc58e5 -Shana ... View more

Tom, yes it is possible to add several individual address locators to a composite address locator, regardless of the type (online geocoding service, StreetMap address locator provided with the software, or your own address locator you created with your own reference data). The TA_Address_NA geocoding services that are available when you make the GIS Server connection to http://tasks.arcgisonline.com/ArcGIS/services is itself a composite address locator. http://www.arcgis.com/home/item.html?id=919dd045918c42458f30d2c85d566d68 -Shana ... View more

The problem that you are encountering is a bug, NIM055232, at the final version of ArcGIS 10, which is resolved by installing service pack 1. http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=17&MetaID=1685 ... View more

Dennis: I would suggest using the running the following registry file to resolve the conflict between the Visio 2003 template and the ArcGIS 10 dll files in order to get the Semantic Checker to work in verion 10. http://resources.arcgis.com/gallery/file/geodatabase/details?entryID=446C6FCE-1422-2418-34D3-EB09E971EEFF Shana B. ESRI Support Services ... View more