[georss] Getting started with Georss & KML

[Joshua Lieberman]

Charles,

Georss has two optional properties for altitude: elev is meters above  
the WGS84 geoid aka mean sea level, while floor is the floor number  
(1st floor, 2nd floor, etc.)

For the truly ambitious, one can use a 3D coordinate reference system  
with GeoRSS GML (e.g. EPSG:4329) and 3-tuples in the poslist contents

--Josh

On Jun 21, 2007, at 10:51 AM, Holmes, Charles V. wrote:

> Thanks for all the responses.  The sample feed and schemas will be
> immensely useful.
>
> FeatureServer is very interesting too since part of the project  
> will be
> converting OpenLayers features from the EditingToolbar into KML too.
> However, it just doesn't seem to follow the approach of where we're
> going.  One question I did have though...when I click the KML button
> (http://featureserver.org/demo.html), the result in Google Earth
> contains 100's of features rather than those just shown on the map.
> Where are these coming from?
>
> I will take your advice about the loose approach.  The design we're
> going with is taking gml and w3c formats and converting them to the
> spec, so, internally, we only have a spec feed.  But I'm beginning to
> feel that we'll need to convert gml, simple and w3c to spec simple.
>
> One other question.  Georss doesn't support altitude.  I'm sure there
> are some small number of people who have altitude information they  
> want
> to encode (e.g. location of world's highest peaks).  How do they  
> handle
> such a case?  Do they use another format, or does another coordinate
> system in gml support altitude?
>
> Thanks,
> Charles
>
> -----Original Message-----
> From: ajturner at gmail.com [mailto:ajturner at gmail.com] On Behalf Of
> Andrew Turner
> Sent: Wednesday, June 20, 2007 5:16 PM
> To: Jason Birch
> Cc: Holmes, Charles V.; georss at lists.eogeo.org
> Subject: Re: [georss] Getting started with Georss & KML
>
> Mapufacture is back up - so you can use it for converting feeds/KML or
> grabbing some more examples. I've also put up a "full" example on the
> front-page of georss.org
>
> On 6/20/07, Jason Birch <Jason.Birch at nanaimo.ca> wrote:
>>
>> You also may want to consider a "loose" approach to parsing GeoRSS.
> Relying
>> on compliance may limit the applications of your tool.
>
> This is a very good point. There is a big difference between being
> "compliant" with the 'spec' and actually being able to consume the
> large number of feeds out there that are broken in some way. This is a
> general problem with RSS and user-created documents in general.
>
> It's also why people like Google, Mapufacture, and I assume
> FeatureServer don't want to be thought of as the "Validators". Too
> often people think "but it works in GoogleMaps - I must have it
> right". Gregor pointed out FeedValidator, and hopefully peopl start
> using that more now that it supports GeoRSS & KML.
>
> Perhaps all of our aggregators should ping (via SMS, phone calls,
> knocks on the door in the middle of the night) feed owners whenever we
> see their feed is invalid (but still loosely parse it)
>
>
>
>>
>> Jason
>>
>>  ________________________________
>>  From: Holmes, Charles V.
>> Subject: [georss] Getting started with Georss & KML
>>
>>
>>
>> I'm just getting started on a project to bring Georss support in.
> I'm
>> looking for a variety of things to get myself situated:
>>
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
>>
>>
>
>
> -- 
> Andrew Turner
> ajturner at highearthorbit.com      42.2774N x 83.7611W
> http://highearthorbit.com              Ann Arbor, Michigan, USA
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss