On Sun, 4 Mar 2007, Kake L Pugh wrote:
There's still the problem of the lat/long being wrong in the database though, and I think this is important. Part of the reason I based CGI::Wiki on a database backend in the first place was that I always had in mind that people would be able to use SQL to get data out in unforeseen ways. Historical reasons aren't really justifications for doing anything, of course, but I think I've showed recently (e.g. the search thingy I posted to the list) that direct database access is a real possibility, and really useful.
Maybe we should do the conversion to wgs84 at page save time, put the un-converted lat/long into a new field (eg local_lat, local_long), and make the (current) lat/long fields hold the wgs84 one?
That way, most things that want lat/long will get the wgs84 one (which they probably expect), we have the local one to hand if needed, and we only need to do the conversion on page save, not each page view.
Nick