[postgis-devel] Adding 4D support to asGeoJson

Paul Ramsey pramsey at cleverelephant.ca
Wed Jan 31 05:32:51 PST 2018

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.


> On Jan 30, 2018, at 10:39 PM, Sandro Santilli <strk at kbt.io> wrote:
> On Tue, Jan 30, 2018 at 06:00:21PM -0500, Alexandre Lessard wrote:
>> 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."
>>> Do we really want to go there?
>> The original GeoJson spec allowed it and openlayers already treats the
>> fourth dimension as the measure, using a XYZM layout.
>> I can't think of better way to pass the M data from postgis to a client app
>> such as openlayers than through GeoJson.
> Maybe add an optional function argument to request the kind of
> standard, as we have for WKT (ISO, OGC, Extended) ?
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel

More information about the postgis-devel mailing list