#36036: Support the 4th dimension (M) in the GEOS API
-----------------------------+------------------------------------
Reporter: Andrew | Owner: Andrew
Type: New feature | Status: assigned
Component: GIS | Version: dev
Severity: Normal | Resolution:
Keywords: GIS 4d GEOS | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"ec2ccff9a512adc715c5fc620bbe80790857b147" ec2ccff9]:
{{{#!CommitTicketReference repository=""
revision="ec2ccff9a512adc715c5fc620bbe80790857b147"
Refs #36036 -- Added note about z argument in GEOSCoordSeq.__init__().
When dropping support for GEOS 3.13 the `GEOSCoordSeq_hasZ()` function
will be available on all supported GEOS versions. Instead of the parent
geometry providing the z dimension we can reply on GEOSCoordSeq functions
directly. This will follow a similar implementation to what was done for
the M dimension.
While it could be adopted earlier we would need to guess that geometries
with 3 dimensions on GEOS < 3.14 are Z geometries.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36036#comment:28>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c42a54715-1ed61b33-1d13-4e05-a23a-11ae09d29448-000000%40eu-central-1.amazonses.com.
