On Mon, Jun 28, 2004 at 12:03:37AM +0100, Kate L Pugh wrote:
The state of this is that I released a plugin in the form of CGI::Wiki::Plugin::Locator::UTM
How does this mesh with zool's work? Are your plugins complementary or should we pick one or the other?
an additional piece of data by way of the ellipsoid. This needs to be prompted for in the setup, and held in the config file.
i kind of assume it will always be wgs84 - 23 for Geo::Coordinates::UTM - or nad83 which is centimetres of difference. this is what gps, the big mapping sites, etc use - this could be a default config option without a prompt?
In terms of metadata, the module needs (and relies on) latitude and longitude. The pythagorean distance finder needs zone, easting and northing. The plugin will provide these via the location method. The distance finder needs zone, easting and northing to be stored in the database.
i never needed to use the zone, but things will blow up if a guide spans more than one and gets different spatial references? as 'easting' and 'northing' rather than os_x / os_y?
then i think the 2 plugins should be totally compatible, and i just change mine to use base CGI::Wiki::Plugin::Locator::UTM, and add the geocoding method. nice one ivor.
a further thought! Schuyler objects that distances in metres and kilometres meant little to people not used to seeing them / converting between them and yards/miles, e.g. pesky merkins. i could do metre/mile conversion and change the distances - or keep it like it is - but it's definitely a question.
zx