Theres was also the problem that the Double to String conversion in LngLatAltSerializer performed on lng and lat but not alt. So a 3d point ends up with two strings and a double.
I came accorss this problem when I was trying to use geojson generated by this api with MongoDB. MongoDB is designed to work wth the geoJson spec and so cannot create indexes for the generated geoJson as it expects arrays of Doubles not Strings when dealing with locations.
Ive corrected these problems by removing the fastDoubleToString method from the LngLatAltSerializer.
If you look at the geoJson specifications position data should be given as an array of doubles not strings. http://geojson.org/geojson-spec.html#geometry-objects
Theres was also the problem that the Double to String conversion in LngLatAltSerializer performed on lng and lat but not alt. So a 3d point ends up with two strings and a double.
I came accorss this problem when I was trying to use geojson generated by this api with MongoDB. MongoDB is designed to work wth the geoJson spec and so cannot create indexes for the generated geoJson as it expects arrays of Doubles not Strings when dealing with locations.
Ive corrected these problems by removing the fastDoubleToString method from the LngLatAltSerializer.