[georss] Transport of Toponyms with GeoRSS

[Carl Reed OGC Account]

Marc -

If the georss group does decide to enable encoding of civil address 
information, why re-invent the wheel? OASIS has a standard called xAL 
(eXtensible Address Language). xAL resulted from a collaborative effort in 
which addressing (civic location) from dozens of countries was researched. 
So, xAL is semantically rich enough to handle civic/civil addresses anywhere 
in the world. As a matter of fact, the latest version of KML (2.1) uses xAL 
for expressing the types of information you are suggesting. FYI, I am 
working with the xAL folks to enhance xAL to use GML for expressing location 
geometry as well as to define a GML xAL application schema.

>From the KML 2.1 tag index page:
<address>

This tag can contain an unstructured address written as a standard Street, 
City, State address, and/or as a postal code. You can use the <address> tag 
to specify the location of a point instead of using latitude and longitude 
coordinates. For example, Google Earth can compute the position of:

<address>1600 Amphitheater Pkwy, Mountain View, CA</address>Note: This 
feature currently works only for U.S., Canada, and United Kingdom addresses.

Values
A string value representing the street address or postal code of the desired 
placemark. For example:

<address>1600 Amphitheater Pkwy, Mountain View, CA</address>Parents

  a.. <Placemark>
<AddressDetails>
A structured address, formatted as xAL, or eXtensible Address Language, an 
international standard for address formatting. <AddressDetails> is used by 
KML in the Google Maps API. For details, see the Google Maps API 
documentation.



<?xml version="1.0" encoding="UTF-8"?><kml 
xmlns="http://earth.google.com/kml/2.1">  <Response>    <name>95008</name> 
<Status>      <code>200</code>      <request>geocode</request>    </Status> 
<Placemark>      <address>Campbell, CA 95008, USA</address> 
<AddressDetails>        <Country> 
<CountryNameCode>US</CountryNameCode>          <AdministrativeArea> 
<AdministrativeAreaName>CA</AdministrativeAreaName>
            <Locality>              <LocalityName>Campbell</LocalityName> 
<PostalCode>                <PostalCodeNumber>95008</PostalCodeNumber> 
</PostalCode>            </Locality>          </AdministrativeArea> 
</Country>      </AddressDetails>      <Point> 
<coordinates>-121.955390,37.280007,0</coordinates>      </Point> 
</Placemark>  </Response></kml>Values
A structured address, formatted as xAL, or eXtensible Address Language.

----- Original Message ----- 
From: "Marc" <marc at geonames.org>
To: <georss at lists.eogeo.org>
Sent: Thursday, August 17, 2006 9:02 AM
Subject: Re: [georss] Transport of Toponyms with GeoRSS


>I think this problem is due to the lack for encodings of semantic
> geographic information in GeoRSS such as country, administrative
> division or placename. We have discussed this before and the discussion
> has been compiled in a draft :
> http://georss.geonames.org/georss-draft.html
>
> Not only could semantic geographic information in GeoRSS be used to
> display labels but also for fundamental use cases in automatic
> processing like filtering, grouping, prioritizing of feed items
> according to geographic criteria. We shouldn't discard this issue as
> 'human readable' versus 'not human readable'. It is simply an important
> and missing feature in GeoRSS.
>
> Cheers
>
> Marc
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss