Concern about EVDB’s latitude and longitude (Shoko's Blog)

Concern about EVDB’s latitude and longitude

Tags:

We can get not only address data of events by EVDB but also latitude and longitude data.
But sometimes the data is not exactly true.
Example of : U of M Football Games,
We can get

venue_name:       Michigan Stadium
venue_address:    1000 South State Street
city_name:             Ann Arbor
region_abbr:         MI
postal_code:         48109
latitude:                 42.2749481201172
longitude:             -83.7406845092773

But In google maps, the adress data and the latitude and longitude is not matched as the screen shot below indicates.

Based on latitude and longitude:(42.2749481201172, -83.7406845092773)

Based on the address "1000 South State Street Ann Arbor"

EVMapper, a mashup of EVDB and Google Maps, also indicates a wrong place as EventMaps.

Posted by Shoko on October 24, 2006 9:37 PM | Permalink

TrackBack

TrackBack URL for this entry:
http://learningremix.net/cgi-sys/cgiwrap/fpgibson/learningremix.net/mt-f2006integ/mt-tb.cgi/602

Listed below are links to weblogs that reference Concern about EVDB’s latitude and longitude:

» Concern about EVDB’s latitude and longitude from Usha's Blog
Shoko I checked out freshlogicstudios ...just take a look at the image below ...... [Read More]

» The Google Maps API from Bud's Blog
A number of groups are using the google maps API. The API documentation itself seems good, with examples and all, but it might be kind of dense. I have a series of simple examples that I downloaded as part of... [Read More]

» Concern about EVDB’s latitude and longitude from Shoko's Blog
Concern about EVDB’s latitude and longitude (Shoko's Blog) We can get not only address data of events by EVDB but also latitude and longitude data. But sometimes the data is not exactly true. using geocoder, I can get appropriate point... [Read More]

Sun	Mon	Tue	Wed	Thu	Fri	Sat
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30

Shoko's Blog