I agree that that feature would make it a lot easier for people to use
the map view. But I didn't implemented it for a few reasons, some of
which over time no longer apply:
1. It's a lot trickier to program that due to the asynchronous nature of
the geocoding calls. But I have successfully implemented this in another
project (Potluck
http://simile.mit.edu/potluck/
) that I can now port it over to Exhibit.
2. It causes Exhibit to call Google Maps' geocoder for every map marker
every time an exhibit is viewed.
- This is slow, compared to having the lat/lng pairs all ready.
- In the past, there was a limit that Google Maps imposes to how many
geocoding calls a web page could make. However, since this quota has
recently been changed to IP-based, this reason is outdated.
http://googlemapsapi.blogspot.com/2007/09/coming-soon-ip-based-geocode-limiting.html
David
Ivan Zhidov wrote:
> I suggest adding 'ex:address' as a input parameter to Map view which
> will make Exhibit more readily available to display map data without
> worrying about maintaining lat/lng values for ex:latlng.
>
> Ivan
>
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
>
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
