The resulting set, after being converted to a PBF using json2geobuf and decoded with geobuf2json (or other decoders) shows the same (first occurring) altitude for all points in the set:
Looks like a bug. Related: #30. Currently Geobuf doesn't support missing altitude but at least it should fall back with a 0 value, not copy over the same one from the first coordinate.
Given a MULTIPOINT set like:
The resulting set, after being converted to a PBF using json2geobuf and decoded with geobuf2json (or other decoders) shows the same (first occurring) altitude for all points in the set:
The issue does not occur if the point in the sample set is given an altitude of 0 or another value.