-----Original Message----- From: openguides-dev-bounces@openguides.org [mailto:openguides-dev-bounces@openguides.org]On Behalf Of jo walsh Sent: 11 March 2004 10:13 To: openguides-dev@openguides.org Subject: [OpenGuides-Dev] non-UK openguides
hi again,
as briefly mentioned on irc we'd like to set up an open guide to san francisco. i wonder what the oslo people did to de-UK-ify their openguides
- just delete the OSX and Y fields from their template?
the openguides we ran at etcon not really for geographic purposes i did fix up to accept UTM and convert back and forth between lat and long (and OS numbering is just a UTM coordinate with a digit missing i learned) also i was thinking of plugging in a geocoder to generate lat and long from street addresses - e.g. http://headmap.org/geocoder/geolookup.cgi - postcode boundaries being very large here.
is anyone else looking at that, i could try and assemble these changes into a patch but they were a bit messy and should be config options...
Sounds like I need to pull my finger out and write the Geography::Grid module I have been meaning to write. I think I've got the tuits to do this in non-work time at the moment. I should also write this up as a hack once I've done it.
Ivor.
On Thu, Mar 11, 2004 at 05:20:08AM -0500, IvorW wrote:
-----Original Message----- From: openguides-dev-bounces@openguides.org [mailto:openguides-dev-bounces@openguides.org]On Behalf Of jo walsh Sent: 11 March 2004 10:13 To: openguides-dev@openguides.org Subject: [OpenGuides-Dev] non-UK openguides
hi again,
as briefly mentioned on irc we'd like to set up an open guide to san francisco. i wonder what the oslo people did to de-UK-ify their openguides
- just delete the OSX and Y fields from their template?
the openguides we ran at etcon not really for geographic purposes i did fix up to accept UTM and convert back and forth between lat and long (and OS numbering is just a UTM coordinate with a digit missing i learned) also i was thinking of plugging in a geocoder to generate lat and long from street addresses - e.g. http://headmap.org/geocoder/geolookup.cgi - postcode boundaries being very large here.
is anyone else looking at that, i could try and assemble these changes into a patch but they were a bit messy and should be config options...
Sounds like I need to pull my finger out and write the Geography::Grid module I have been meaning to write. I think I've got the tuits to do this in non-work time at the moment. I should also write this up as a hack once I've done it.
I haven't done much to de-anglicanize the Orlando openguide. I keep meaning to get a tuit into either implimenting Geo::Distance for the time being (something better than nothing) or take a stab at the affor mentioned Geo::Grid hack (I'm not the best at maths).
If something were to appear, I'd be more than happy to work as a testbed.
-Chris
Sounds like I need to pull my finger out and write the Geography::Grid module I have been meaning to write. I think I've got the tuits to do this in non-work time at the moment. I should also write this up as a hack once I've done it.
cool, what will it do, that isn't covered by the crossection of Geography::NationalGrid and Geo::Coordinates::UTM ... be a nicer API?
I haven't done much to de-anglicanize the Orlando openguide. I keep meaning to get a tuit into either implimenting Geo::Distance for the time being (something better than nothing) or take a stab at the affor mentioned Geo::Grid hack (I'm not the best at maths).
there's a Geo::Distance for latlong on CPAN too. but it uses the wrong algorithm for calculating short distances on a sphere. i used it in mudlondon as a good-enough approximation... perhaps it could be patched. schuyler wrote up some of this stuff, cosines v haversines etc... for the san diego stuff we did i just converted everything to utm and did plain old cartesian distance, which is i guess all right for an openguide where everything is going to be in the same UTM zone...
jo -- "Common sense won't tell you. We have to tell each other." -DNA
openguides-dev@lists.openguides.org