Scrapers should warn about coordinates out of bounds

[slinkp]

Three common problems I've seen:

1. long,lat are in reversed order.
2. long,lat = 0, 0. The Globe has (according to Joel) a CMS bug causing this.
3. long,lat = otherwise out of city bounds (eg. article mentions Sydney so some upstream geocoder tagged it for Sydney, AU).

These are all easy to detect; the scraper infrastructure should do so, and should warn accordingly.

In fact 1 is easy to auto-correct - if (x,y) is not in the city bounds, try (y,x) and if that's good, give the warning and just make the correction.

For 2, and 3, I started a thread with some thoughts: http://groups.google.com/group/ebcode/browse_thread/thread/6c5b62aab7d21228

[slinkp]

Milestone Beta Release 1 deleted

[slinkp]

Ticket imported from Trac:
http://developer.openblockproject.org/ticket/54
Reported by: slinkp