Enhancement: Please support serializing geometry without altitude

[GoogleCodeExporter]

Allowing the creation and serializing of geometries with no altitude value 
would provide a minor decrease in the size of KML files, and would also 
allow authors who do not want to assert an elevation value where they 
don't know the elevation of a vertex to choose not to.

Original issue reported on code.google.com by ja...@jasonbirch.com on 25 Jan 2009 at 1:10

[GoogleCodeExporter]

Original comment by kml.mash...@gmail.com on 8 Feb 2009 at 4:33

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I agree that adding a x,y,0 where there was only a an x,y is not proper.
libkml does not elsewhere explicitely set in the xml any default value
if one was not specified on input.

Recent changes to Coordinates and the internal Serializer make this
an easy change.  It will break a ton of unit tests and golden files though
if we make this behavioral change to SerializePretty.  One way out of that
is to introduce a new Serialize class/function with a richer and more
extensible set of arguments

Original comment by kml.b...@gmail.com on 6 May 2009 at 4:25

[GoogleCodeExporter]

r585 handles the <coordinates> parsing side of this.
a parse of <coordinates>1,2</coordinates> leads
to a has_altitude() of false.  get_altitude() does still
return 0.0.

stay tuned for possible news about serialization of
a vec3 with has_altitude() of false...

Original comment by kml.b...@gmail.com on 8 Jun 2009 at 10:51