[Geowanking] Re: [georss] Musings about GeoRSS
geowanking at highearthorbit.com
Sat Oct 29 09:20:39 PDT 2005
Sorry to bring this up - since I just recently read up on the
postings.The formulation of the geo-tags looks great.
However, is there any support for formal encoding of a textual
description of the location (city, state, region, country, name,
neighborhood, building, floor). Sometimes the geographic location
context is more important based on, say, a town or neighborhood that
may or may not have a defined geographic boundary, or for boundaries
that change with respect to time. (is a lat/lon point placed in
southern USSR in 1984 in now independent country of Georgia or USSR?)
Geo searches for a town would have to do some fairly complex boundary
searching rather than saying "Springfield" "Missouri" "US".
I'm not sure if this is in the scope of the GeoRSS definition, but
seems like if you are trying lay out a 'standard' by which
geo-encoding will conform, there should be defined support for more
than pure lat/lon/alt.
> From: Mikel Maron <mikel_maron at yahoo.com>
> Subject: Re: [georss] Musings about GeoRSS
> To: georss at lists.eogeo.org
> Message-ID: <20051026105001.41421.qmail at web52608.mail.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
> This looks like an excellent approach. I think presenting this properly
> will require three facets: the content model definition sketched by
> Allan; a list of specific implementations (w3c GeoRSS w/ worldKit
> extensions, GMLRSS, flickr/delicious geotags, geo microformat), with
> examples and rationales behind each; and a short guide for developers
> and users to quickly get an idea what it's all about.
> What are the next steps?
http://highearthorbit.com 42.4266N x 83.4931W
More information about the Geowanking