[georss] Can GeoRSS and KML converge on a geometry encoding?

[Sean Gillies]

I'm not thinking about arcs and hemispherical patches, or 3D
visualization, but about dimensionality of positions. 3D position lists
are not allowed in GeoRSS GML, are allowed in KML 2.2, and I imagine
that they will be an option in KML 3. Some of you have the inside track
on KML, right? I'm just suggesting we could steer GeoRSS to where KML is
headed.

#geo-web-rest on freenode

http://groups.google.com/group/geo-web-rest/web/atom-geo-interop-the-2nd

Sean

Joshua Lieberman wrote:
> GeoRSS GML already uses GML 3 geometries, just not all possibilities.  
> KML, if/when it supports GML 3, is unlikely as well to support all  
> possible GML 3 geometries. There are specific options in KML for 3D  
> handling, though, which are not in GML at all. I was just suggesting  
> earlier that providing a place for them to be expressed in GeoRSS  
> might make it more straightforward for GE to handle feeds and KML  
> together.
> 
> Sean, are you and Charlie going to make some sort of a conference  
> line / IRC channel available tomorrow, or should we try to do  
> something more inclusive at another time (e.g. next week).
> 
> -Josh
> 
> On Apr 10, 2008, at 10:14 AM, Sean Gillies wrote:
> 
>> Andrew, you reported in your blog last fall that KML may switch over  
>> to
>> GML 3 geometries. If that were true, wouldn't it make sense for the  
>> next
>> iteration of GeoRSS to recommend the same practice? Seems to me this
>> could simplify the situation for feed and KML processors.
>>
>> Sean
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
> 
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss
>