ArcGIS Online now support single line geocoding

[BjornSvensson]

Last week tasks.arcgisonline.com was upgraded to ArcGIS Server 10 which adds two great capabilities: single-line geocoding and being able to set the outSpatialReference. In addition, two new services were added with support for single-line geocoding.

• TA_Address_NA_10


• TA_Streets_US_10.

Both of these support single-line geocoding  (i.e. one address field, instead of one street field, one city field etc).  The existing 2.2 Locator Widget already has support for single-line geocoding. Since the default is to use a single-line geocoder if it exist, simply point it to the new service(s) to start taking advantage of single-line geocoding in your locate widget. For example, for the new US locator:

<locator>http://tasks.arcgisonline.com/ArcGIS/rest/services/Locators/TA_Address_US_10/GeocodeServer</locator>

If you do not want the single-line geocoder, but still want the new Locator, add

<usesingleline>false</usesingleline>

Another enhancement with the updated tasks.arcgisonline.com is that now all its Locators support outSpatialReference.  This means that instead of receiving the location in latlong and having to project it, you can now ask for it to be returned directly in whatever projection you want (for example Web Mercator).
http://help.arcgis.com/en/webapi/flex/apiref/com/esri/ags/tasks/Locator.html#outSpatialReference

[AndyWright]

This is great news!  Thanks for the post Bjorn.  I noticed in the description of these new locators that they support batch geocoding of up to 10 addresses at once.  Can you post a little code snippet of how we would set that up within the AddressToLocationsParameters object?  I haven't been able to figure it out or find any examples of how to do it.  Thanks ...

[BjornSvensson]

...batch geocoding...

The REST API, and thus the Web APIs, do not support batch geocoding.  Instead you would send multiple requests - with one geocode per request.

[AndyWright]

Gotcha.  That's probably why I couldn't figure it out.  Any plans to support that in the future?  Thanks ...