I am seeing consistently incorrect values for city and county being returned by reverse geo-code. I am a bit surprised since all of the locations I'm working with right now are in the Dallas, TX, US area so I would think the data should be accurate. The errors are not a matter of adjoining borders. In many cases, the returned city is 10s of miles away from the location. In some cases the city is correct but the county is wrong even on citys that do not cross county lines. The errors almost appear random at times.

I'd pursue correcting the data but the number of invalid data elements is running at about 25% so manually fixing them is out of the question and I currently have no desire to automate the correction.

Any suggestions?

Thanks.

asked 25 Jan '12, 14:58

1OldGeek's gravatar image

1OldGeek
10112
accept rate: 0%

2

@1OldGeek Which Geocoding tool are you using for OSM? OpenNames? Nomination?

(25 Jan '12, 17:23) jwernerny

@1OldGeek And in addition, would you provide links or references about the data being reverse geo-coded badly, so the community can look into the error?

(25 Jan '12, 17:27) prabhasp
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×113
×83
×31
×21
×19

question asked: 25 Jan '12, 14:58

question was seen: 2,510 times

last updated: 25 Jan '12, 17:27

powered by OSQA