Address String Geocoding is Very Inaccurate (20 km)

Originator:joe
Number:rdar://11861418 Date Originated:12-Jul-2012 03:54 PM
Status:Open Resolved:
Product:iPhone SDK Product Version:5.1
Classification:Serious Bug Reproducible:Always
 
Summary:

Strings do not always geocode properly. The placemarks returned can be off by as much as 20km.

Steps to Reproduce:

Initialize a CLGeocoder object, then call -geocodeAddressString:completionHandler: with "Primm, NV".

Behind the scenes, this appears to be sent to Apple's secure geocoding server (using a very basic app of my own, but all you really need is to make the alloc and geocode method calls):

en_US com.thisexitllc.roger 10.7.4.11E53 + Z Primm, NVH

Expected Results:

I would expect a result such as "Primm, NV, United States", this time with a coordinate and perhaps a region.

Actual Results:

This is the sole placemark returned by Apple's SSL server:

(
    "Jean, Jean, NV, United States @ <+35.78121050,-115.43841783> +/- 100.00m, region (identifier <+35.78247050,-115.45806900> radius 30660.48) <+35.78247050,-115.45806900> radius 30660.48m"
)

This is Jean, NV, about 20km away from Primm.

Regression:

None.

Notes:

N/A

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!