----- Original Message -----
From: "Stephen Stewart" <beowulf(a)carisenda.com>
To: <ivorw-openguides(a)xemaps.com>
Sent: 30 April 2004 22:34
Subject: CGI::Wiki::Plugin::Locator::UTM OpenGuides
>
> Hi,
>
> What do I need to change in OpenGuides to use
> CGI::Wiki::Plugin::Locator::UTM
Excellent! Someone wants to use my module :). I designed it with OpenGuides in
mind, but I have not integrated it yet. But, you are in luck. I have the time to work on
this at the moment. I will update the dev CVS on un.earth.li, and also make patches
available through this list.
> (I want to use the modified airy ellipsoid to get better results)?
I don't know if "Modified Airy" is the right one to use, but it is certainly supported by
Geo::Coordinates::UTM. My researches have shown "GRS 1980" as recommended
as a generic ellipsoid for Europe.
>
> Also I changed Template.pm to use Geography::NationalGrid::IE but we
> don't have access to ox x/y coords, so what do I need to change to use
> long/lat coords?
Ah, Geography::NationalGrid is designed to only work with OS coordinates.
I also think that lat/long is the way to go with OpenGuides as a whole, as
everyone uses GPS, the world over.
What is equally important though, is that the metadata stores an X and Y
reference somehow. CGI::Wiki::Plugin::Locator::UTM uses metadata fields
called zone, easting and northing. It is important that these fields are
populated in the database, otherwise "find by distance" will never work.
C::W::P::L::U has been designed with this in mind. The current OpenGuides
version uses CGI::Wiki::Plugin::Locator::UK, which relies on metadata fields
called os-x and os-y being populated. I have deliberately used different field
names, so that we can incorporate both sets of data in the same wiki. This is
possibly a requirement for the UK.
> Sorry, but my questions can't be very smart and I can't write patches,
> I'm just a designer trying to bodge this together.
Don't worry. If you can test the changes I am making to the modules, this
would be brilliant.
Ivor.