[georss] elevation and Simple<->GeoRSS GML interop questions

[Joshua Lieberman]

2D Default (if you omit srsName and srsDimension):

Point:
<georss:where>
     <gml:Point srsName="urn:ogc:def:crs:EPSG::4326" srsDimension="2">
         <gml:pos>31.936 -115.834</gml:pos>
     </gml:Point>
</georss:where>

Line:
<georss:where>
     <gml:LineString srsName="urn:ogc:def:crs:EPSG::4326"  
srsDimension="2">
         <gml:pos>31.936 -115.834 31.128 -118.479</gml:pos>
     </gml:LineString>
</georss:where>

3D Geographic:

Point:
<georss:where>
     <gml:Point srsName="urn:ogc:def:crs:EPSG::4979" srsDimension="3">
         <gml:pos>31.936 -115.834 345</gml:pos>
     </gml:Point>
</georss:where>

Line:
<georss:where>
     <gml:LineString srsName="urn:ogc:def:crs:EPSG::4979"  
srsDimension="3">
         <gml:pos>31.936 -115.834 345 31.128 -118.479 303</gml:pos>
     </gml:LineString>
</georss:where>


On May 7, 2008, at 4:33 AM, Makc wrote:

> Hello list, just a side-note about these:
>
> On 5/7/08, Joshua Lieberman <josh at oklieb.net> wrote:
>> one needs generally to declare both a 3D coordinate system  
>> (compound or not)
>> and dimensions defined by that system.
>
> On 5/7/08, Joshua Lieberman <josh at oklieb.net> wrote:
>> It is generally necessary to look at the definition of the CRS. One  
>> can look
>> at the EPSG code definitions here, for example:
>> http://www.epsg-registry.org/ and find that the 3D equivalent of  
>> EPSG:4326
>> is EPSG: 4979. There only appear to be CompoundCRS versions of  
>> projected 3D
>> CRS's, e.g. EPSG:7416 is a combination of  ETRS89 / UTM zone 32N +  
>> DVR90
>> height.
>
> I was pointed to this link before, but apparently I am stupid enough
> to not figure out how to use it (twice now). Could someone please just
> paste some sample gml file that declares lat/lon/elevation system and
> some location using it, so that I could "get a feeling" of how it
> should look like?