[postgis-devel] Why do we use has_z and has_m all the time instead of n_dims

[Sandro Santilli]

On Wed, Oct 08, 2014 at 03:10:14PM +0200, Nicklas Avén wrote:
> Hallo
> 
> I am looking at http://trac.osgeo.org/postgis/ticket/2917 to create a
> twkb reader
> 
> I find myself doing som ugly steps to fit into the api with has_z and
> has_m.
> 
> Why do we handle third and fourth dimension as z and m internally when
> creating a point array?
> 
> I am thinking about the functions in ptarray.c

A POINTARRAY may point to an array of POINT2D, POINT3DZ, POINT3DM or POINT4D.
We want to allow having M and no Z.
Does this answer your question ?

--strk;