Skip to main content
  • EN

Hi Everyone,

A simple question i hope, but how can i use the right transformer, to ensure that a <gml:pos> is written in my CityGML? Currently a <gml:posList> element is written.

Here is what i am getting:

<bldg:lod2MultiSurface>
	<gml:MultiSurface srsName="EPSG:27700" srsDimension="3">
	<gml:surfaceMember>
		<gml:Polygon>
			<gml:exterior>
				<gml:LinearRing>
					<gml:posList>555687.68 236458.51 216.48 555689.24 236454.66 214.32 555699.8 236458.94 214.35 555698.46 236462.26 216.21 555698.28 236462.72 216.47 555687.68 236458.51 216.48</gml:posList>
				</gml:LinearRing>
			</gml:exterior>
		</gml:Polygon>
	</gml:surfaceMember>
	</gml:MultiSurface>
</bldg:lod2MultiSurface>

Hello @steveway,

 

With gml:posList and gml:pos being interchangeable we currently only support gml:posList due to the fact it is more compact. If you would like this functionality to be added(to differentiate whether gml:pos or gml:posList is used when writing), you could post an idea regarding this functionality.

The ideas forum can be found here: https://knowledge.safe.com/content/idea/list.html

 

 

Out of curiosity, may I ask why you would want to write to gml:pos as opposed to gml:posList?

Hello @steveway,

 

With gml:posList and gml:pos being interchangeable we currently only support gml:posList due to the fact it is more compact. If you would like this functionality to be added(to differentiate whether gml:pos or gml:posList is used when writing), you could post an idea regarding this functionality.

The ideas forum can be found here: https://knowledge.safe.com/content/idea/list.html

 

 

Out of curiosity, may I ask why you would want to write to gml:pos as opposed to gml:posList?
Hi Trent, thanks for taking time to reply. I agree with you, they are interchangeable, and actually, posList is more efficient as it is compact.

 

 

The reason i ask, is that client specification has defined gml:pos.

 

 

Many Thanks,

 

Steve

 

 

Reply


Community Stats

29,712
Posts
112,921
Replies
37,367
Members
Terms & ConditionsCookie settings