[georss] GeoRss Encoding

[Joshua Lieberman]

Chris,

GeoRSS says nothing in particular about what happens outside of the  
georss elements and both Atom and RSS explicity allow elements from  
other namespaces to be mixed into feeds/ channels and items /  
entries. If you want to add a vendor specific element, it is your  
choice and nothing to do with GeoRSS, but you should put it into its  
own namespace, e.g. <pyx:coord> and add that namespace to the XML,  
e.g. xmlns:pyx="http://schema.pyxisinnovation.com".

There is no guarantee, of course, that other feed aggregators won't  
strip off the element as extraneous, although they are generally not  
supposed to.

Cheers,

Josh Lieberman

On Oct 12, 2007, at 3:17 PM, Chris Howell wrote:

> Hi,
>
> I the company I work for is working on developing a Discrete Global  
> Grid System, that not only displays user provided data, but also  
> provides analysis capabilities and do data integration by  
> conflating numerous data sources on a hexagonal grid. One of our  
> aims is to eventually become a platform for our users to use and  
> interop between various other applications. One of the ways that  
> we're attempting to provide interop is by providing a common way to  
> describe our feature data. I've been looking at the differences  
> between GeoRSS and GML to describe this data in an interopable way.
>
> One of the problems I am having is we convert from a co-ordinate  
> system (WGS84) into our own hexagonal co-ordinate system that we  
> work with. What I would like to do is find a way to encode both the  
> lat/lon from a traditional coordinate reference system, as well as  
> our own coordinates to describe the same point.
>
> for example a lat/lon of 20, 48 in WGS84 might turn into a  
> coodinate like A-02030 in my system. Since our application is going  
> to be the only one reading our co-ordinate. What I'd like to do is  
> encode it just as an extra attribute within a GeoRss feed.  
> Essentially I'd like to have something that looks like this.
>
> </georss:where>
>   <entry>
>     <title>Setting off</title>
>     <link href="http://www.myisp.com/dbv/1"/>
>     <id>http://www.myisp.com/dbv/1</id>
>
>     <updated>2005-08-17T07:02:32Z</updated>
>     <content>getting ready to take the mountain!</content>
>     <georss:where>
>       <gml:Point>
>         <gml:pos>45.256 -110.45</gml:pos>
>
>       </gml:Point>
>     </georss:where>
>     <PyxisCoord>A-02030</PyxisCoord>
>   </entry>
>
> I like the idea of being able to use GML geometries in GeoRss.
>
> Where the PyxisCoord Attribute shows up in all the feeds that we  
> send out. What this would allow us to do I am hoping is allow  
> anyone who can receive GeoRss feeds to get data or things geo-coded  
> in Pyxis as just a normal lat/lon and bring them into their system.  
> And allow the Pyxis GeoRss reader to pay attention to the  
> PyxisCoord attribute. What I would like to know is.
>
> 1. Is encoding information like this valid GeoRSS ?
> 2. Am I going to break any GeoRSS readers/aggregaters  out there ?
> 3. Have I violated anything in the GeoRSS standard that says I  
> can't do this ?
>
> Not knowing to much about GeoRss from what I've read and talked to  
> people about I think this is possible but I figured ask the  
> experts. Any help would be greatly appreciated.
>
> Cheers
> Chris Howell
> Software Engineer
> the PYXIS innovation - Common Ground for Digital Earth
> Kingston, Ontario, Canada
> w: www.pyxisinnovation.com
> p: 613-389-6619
>
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.eogeo.org/pipermail/georss/attachments/20071012/d299b8a7/attachment.html