[georss] GeoRSS GML used at triptracker.net

[Mikel Maron]

I guess it's not clear in our docs. TripTracker has a GeoRSS Line as a child of the root element, "feed". 
Some places in the docs specify that GeoRSS elements only apply to Items/Elements, such as the UML graphic, and others show it as acceptable, like the GeoRSS GML examples. 

I think this should be acceptable usage, we just need to make sure its clear and consistent in the docs.

Best,
Mikel

----- Original Message ----
From: Carl Reed OGC Account <creed at opengeospatial.org>
To: Mikel Maron <mikel_maron at yahoo.com>; Ziga Mahkovec <ziga.mahkovec at klika.si>; georss at lists.eogeo.org
Sent: Wednesday, June 21, 2006 12:06:37 PM
Subject: Re: [georss] GeoRSS GML used at triptracker.net

Mikel -

Why is the GeoRSS GML Line not allowed? Am I missing something?

Thanks for providing clarity.

Regards

Carl

----- Original Message ----- 
From: "Mikel Maron" <mikel_maron at yahoo.com>
To: "Ziga Mahkovec" <ziga.mahkovec at klika.si>; <georss at lists.eogeo.org>
Sent: Wednesday, June 21, 2006 12:01 PM
Subject: Re: [georss] GeoRSS GML used at triptracker.net


> Hi Ziga,
>
> This is pretty cool -- to me, travel journals seems like a big opportunity 
> in mapping/georss.
>
> A couple issues on the use of GeoRSS in the feed.
>
> GeoRSS geometries are used in your feed multiple times per entry, and as a 
> child of "tt:photo".
> The GeoRSS model allows for only one Geometry object in each Atom Entry 
> (or RSS item)  and
> only as a child of the entry.
>
> Also, there are many existing namespaces for specifying photos in feeds. 
> For instance, MediaRSS
> [ http://search.yahoo.com/mrss ] is becoming widely used.
>
> I'm not sure of the best way to resolve this for your feed. Perhaps each 
> photo would inherit geographic
> data from its parent Entry, and if a photo had a different location than 
> its parent, it would have to go
> in a seperate Entry.
>
> The GeoRSS Line for the entire feed is a nice touch, I like. However this 
> is also not allowed by the
> current GeoRSS model .. though perhaps it should be? Seems like a 
> reasonable adjustment to the spec.
> Thoughts?
>
> Anyway sorry the majority of this reply is critiques .. lcause overall 
> this is a pretty cool use of GeoRSS.
>
> Mikel
>
>
> ----- Original Message ----
> From: Ziga Mahkovec <ziga.mahkovec at klika.si>
> To: georss at lists.eogeo.org
> Sent: Wednesday, June 21, 2006 8:23:46 AM
> Subject: [georss] GeoRSS GML used at triptracker.net
>
> Hi,
>
> I wanted to let you know that we recently implemented GeoRSS GML in our
> TripTracker.net web service (http://triptracker.net).
>
> TripTracker is used for creating and sharing travel journals.  GPS track
> logs can be imported to automatically geotag photos; nearby photos are
> also grouped into geocoded trip entries.
>
> Trips are presented using a JavaScript map interface (similar to Google
> Maps, but with richer photo presentations).  These maps render an Atom
> feed containing GeoRSS GML -- we use <gml:Point> tags to present
> locations of trip entries and photos; we also use <gml:posList> tags to
> render GPS track logs.
>
> Here is an example of a GeoRSS feed:
>
>  http://triptracker.net/trip/263/georss
>
> And the resulting map:
>
>  http://triptracker.net/trip/263/map
>
>
> This is work in progress: we're planning on making the GeoRSS output
> compatible with other viewers and possibly add support for rendering
> other GeoRSS variants.  Comments are welcome.
>
>
> Keep up the good work,
> -- 
> Ziga
>
> _______________________________________________
> 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