[postgis-devel] Adding 4D support to asGeoJson

Sandro Santilli strk at kbt.io
Wed Jan 31 08:12:10 PST 2018

On Wed, Jan 31, 2018 at 05:32:51AM -0800, Paul Ramsey wrote:
> What, and then strip out extra dimensions for ISO GeoJSON? That seems needlessly byzantine. If people are getting 4d geojson from their 4d objects, they can just force3d them before calling asgeojson. I don’t think the standards differ enough to be worth the extra cruft.

But the standard says you SHOULD NOT do this, so by NOT doing it
we're respecting the standard, and in case a new version of the
standard defines what to do with extra elements (making them
unambiguous) we won't risk any semantic clash.

On 2018-01-30 17:25, Paul Ramsey wrote:
> https://tools.ietf.org/html/rfc7946#section-3.1.1
> "Implementations SHOULD NOT extend positions beyond three elements
> because the semantics of extra elements are unspecified and
> ambiguous."


More information about the postgis-devel mailing list