Fwd: RE: [Geowanking] intro
dls2003 at ThereAndThen.org
Wed Apr 2 13:49:12 PST 2003
Whoops, I meant for my reply to go to the list, not
just one person. Sorry, my bad.
>Date: Wed, 2 Apr 2003 12:52:05 -0800
>To: "VTP" <ben at vterrain.org>
>From: Daniel Smith <dls at daniel.org>
>Subject: RE: [Geowanking] intro
>Will check it out.
>>ThereThen says "Implementation of this does not require any change to
>>existing web documents." Well.... that's literally true, but it does
>>require producing a whole new site layout and filing each document into it
>>own directory. That's potentially more work than just changing the
>Actually, you don't need to produce any new documents, nor
>would you need to change any site layout.
>If you have store a mapping of ThereThen-> real addresses
>into a DB, and then have mod_rewrite take incoming
>requests (via CGI or mod_*) and resolve them back to real
>addresses, you're done. All that matters to the outside
>world is that you can submit an address, and that it
>resolves to something.
>Producing addresses in the first place can be as easy
>as stat()'ing for create/last mod dates on web resources
>(html files, etc.), and pairing with a fixed location for
>the site. A hunch would be that most folks would
>simply obtain lat/long from their postal code (US, UK, etc.)
>Not real precise, but good enough for many. Others
>may take the step of hitting mapquest/mapblast etc
>to get their coordinates, or, like me, ask their
>car in the driveway (navigation system gives GPS)
>> If it's to find all points
>>that a "close" to a given point, why not just use geodetic distance?
>>Background references: http://vterrain.org/Misc/distance.html
>Because I'm new to this :-) I'll check it out. I'm still
>keen on figuring out the lat/lon corners prob though.
>>P.S. miles? Eeeeek! km please!
>Yep! And for the optional altitude part of the location
>component, feet or meters...
>Daniel L. Smith - Sonoma County, CA - AIM: SonomaDaniel
More information about the Geowanking