[georss] GeoAtom (split from Re: GeoRSS Location References)
Andrew Turner
ajturner at highearthorbit.com
Tue Apr 1 16:36:23 EDT 2008
On Tue, Apr 1, 2008 at 4:02 PM, Jason Birch <Jason.Birch at nanaimo.ca> wrote:
> Josh wrote:
> -----------------------
>
> 1) Feature with multiple geometries, such as Massachusetts which
> includes a number of islands and requires a "multipolygon" (with one
> set of other properties) to represent it in detail. Not so important
> for the sort of overview which GeoRSS generally provides, and it seems
> more straightforward to provide content of or a link to a GML feature
> for the more precise geometry.
> -----------------------
>
> I ran into problems with very basic applications of GeoRSS to my data
> simply because it does not support multigeometry (or the simpler
> versions of these). Multipolygons happen often, for instance when a
> single legal parcel is split by a road, right-of-way, or stream bed.
>
> I don't think that multigeometry should be lumped in with the multiple
> geometries problem. It is a completely different use-case than trying
> to refer to multiple locations in a single entry, and does not bring the
> same 1:many relationship complexity. It could be addressed relatively
> easily be an expansion of the GML geometry types that GeoRSS already
> supports.
>
I agree that a MultiGeometry in your case is a different use-case than
multiple, distinct, geometries. In fact, from Josh's use-cases, I
would think 1 & 2 should be within a single entry (they are just
representations of the single geometry that is for that entry), and 3
could be the multi-entries (distinct geometries, or fine-grained).
> I will be somewhat annoyed if GeoRSS ends up only supporting
> multigeometry through a complex multiple-entry mechanism.
>
ergo why voicing your opinion is useful! :)
More information about the georss
mailing list