[georss] Multiple GeoRSS representations in one feed?

[Andrew Turner]

I think Allan's question was about publishing multiple feeds using
different formats. So Jason, for example, could publish a Simple using
points, and then a more complex using GML or Simple with lines. Both
feeds would have the same items, just different representations of the
geographic data.

What actually would be interesting, is if there is any problem
publishing 2 representations in the same feed? RSS parsers ignore
items they don't understand, so the Simple point readers would ignore
the GML. And perhaps a more featured GML parser should consume the
"highest fidelity" geometry from a single item. So the GML ring would
override the Simple point.

Any particular problems with this? Or is it just confusing?

The potential problem with multiple feeds w/ different representations
is that if a user wants to switch the feeds from Simple to GML in
their reader, are the "read/unread" kept (GUID's the same), etc.

Andrew


On 10/20/06, Pat Cappelaere <pat at cappelaere.com> wrote:
> Allan,
>
> It is not unusual for us to display more than one feed on the map.  They are
> displayed on different layers so they can be turned on/off.
> This is really no different than feature layers.
> Pat.
>
>
> > From: Allan Doyle <adoyle at eogeo.org>
> > Date: Fri, 20 Oct 2006 08:30:38 -0400
> > To: <georss at lists.eogeo.org>
> > Subject: Re: [georss] Multiple GeoRSS representations in one feed?
> >
> > I guess I have to wonder also to what extent it's bad to have two
> > feeds? If we try to cram everything into one representation, then we
> > climb up the complexity wall again and leave the simple people (like
> > me) behind.
> >
> > Allan
> >
> > On Oct 20, 2006, at 07:23, Raj Singh wrote:
> >
> >> As Ron said, holes in polygons aren't supported in simple, but are
> >> possible in GeoRSS GML. You'll still have the chicken and egg issue
> >> that you're not likely to find many clients (that aren't "real"
> >> mapping systems) that will correctly render them. That, and
> >> aggregates, begin to stretch the limits of GeoRSS. If those
> >> sophisticated geometries are key to what you're doing, you may be in
> >> the market for a heavier standard, like GML Simple Features Profile,
> >> listed on this page <http://www.opengeospatial.org/standards/gml>.
> >> ---
> >> Raj
> >>
> >>
> >> On Oct 20, 2006, at 8:52 AM, Jason Birch wrote:
> >>
> >>> Is there any way to represent donut polygons in simple?  I can just
> >>> provide the exterior ring, but it would be nice to put holes where
> >>> they belong.
> >>>
> >>> And aggregates... I have quite a few parcels that were split by
> >>> roads, and are actually part of the same legal feature.  I don't
> >>> really need to have them joined as a MultiGeometry, but I can't
> >>> tell from the XSD whether multiple geometries are allowed inside
> >>> the "where".
> >>>
> >>> Jason
> >>
> >> _______________________________________________
> >> georss mailing list
> >> georss at lists.eogeo.org
> >> http://lists.eogeo.org/mailman/listinfo/georss
> >
> > --
> > Allan Doyle
> > +1.781.433.2695
> > adoyle at eogeo.org
> >
> >
> >
> > _______________________________________________
> > 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
>


-- 
Andrew Turner
ajturner at highearthorbit.com        42.4266N x 83.4931W
http://highearthorbit.com              Northville, Michigan, USA