Open vanwars opened 8 years ago
Looks like that point is roughly the geospatial center of Oakland, so if I had to guess, they just geocoded Oakland, CA
for all of those points.
I'll alert our support team to talk to our customer to see if that was intentional. Hopefully they can get some better geodata for that dataset.
Good news, @vanwars! We alerted the city and they were able to fix that dataset!
Thank you for alerting the city, but when I just went to verify the changes, it still appears that all of the lat/lngs are the same. You can see for yourself by clicking here: https://data.oaklandnet.com/resource/x452-eizt.csv. Maybe there's just a time delay?
On Thu, Nov 3, 2016 at 9:48 AM, Chris Metcalf notifications@github.com wrote:
Good news, @vanwars https://github.com/vanwars! We alerted the city and they were able to fix that dataset!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/socrata/discuss/issues/33#issuecomment-258202092, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKGwxqeuWhCq7PMAvXHdRLLXFoM6KaFks5q6hB5gaJpZM4KitYD .
Whoops, sorry @vanwars. I got this ticket confused with another one where the location
column was left empty. I'll re-open this one and follow-up.
API Docs: https://dev.socrata.com/foundry/data.oaklandnet.com/x452-eizt
Hello,
It appears that all of the lat/longs in this dataset are the same. Is this a DB issue or an error in the endpoint code?
https://data.oaklandnet.com/resource/x452-eizt.json