On Sun 04 Mar 2007, Nick Burch openguides@gagravarr.org wrote:
You might just need to tweak the templates, so that when displaying lat and long, they always use the WGS ones (which ought to exported to the page).
Thanks - that'll work as a hack around the data-on-page problem; and a similar hack could be put into OpenGuides::RDF to sort out the RDF thing.
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.
(Also, the main reason the conversion isn't in there already is that when we wrote that part I didn't really understand about ellipsoids, and so didn't realise it was necessary.)
The other thing, which I only just realised, is that the "advanced search" page lets you search for things within a certain distance of a given lat/long. Nobody's going to put OSGB lat/long in here - WGS84 is much more likely. I realise that the error in the results is only going to be at most 20m, but it still niggles.
Basically, I think it would be better to store data that _doesn't_ need munging, rather than try to catch every place where it might be output, and munge it there before we output it.
But I might be being too fussy, and if people think I am then please do say so.
Kake