[postgis-devel] [PostGIS] #816: ST_AsGML: optionally output LineString.posList rather than Curve.segments.LineStringSegments.posList

PostGIS trac at osgeo.org
Tue Feb 1 13:19:28 PST 2011


#816: ST_AsGML: optionally output LineString.posList rather than
Curve.segments.LineStringSegments.posList
-------------------------+--------------------------------------------------
 Reporter:  strk         |       Owner:  colivier     
     Type:  enhancement  |      Status:  new          
 Priority:  medium       |   Milestone:  PostGIS 2.0.0
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by strk):

 Uhm, I've found the use case:

 {{{
 SELECT xmlelement(name traffic_sign,
                   xmlforest(feature_name),
                   topology.asgml(feature)
                   )
  FROM features.traffic_signs
  WHERE feature_name = 'S1';
 }}}

 The xmlelement call encodes the xml tags brackets in output:

 {{{
 <land_parcel><feature_name>S1</feature_name><gml:TopoPoint><gml:directedNode><gml:Node
 gml:id="N14"><gml:pointProperty><gml:Point
 srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos srsDimension="2">21
 14</gml:pos></gml:Point></gml:pointProperty></gml:Node></gml:directedNode></gml:TopoPoint></land_parcel>
 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/816#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.


More information about the postgis-devel mailing list