[mapserver-dev] Using PointZM by default

[Seth G]

Thanks Even. I might add a set of "performance" tests to the Python test suite so we can track performance between releases. 
Reading through the previous discussions one option was to set it to ON by default for a 7.x release, and then remove all the conditional code for a v8 release. Alternatively remove all conditional code for the net 7.4 release. 
Any preferences / risks with regards to these approaches?

--
web:http://geographika.co.uk
twitter: @geographika

On Fri, Mar 1, 2019, at 11:41 AM, Even Rouault wrote:
> On vendredi 1 mars 2019 01:14:34 CET Seth G wrote:
> > Hi all,
> > 
> > There is a pull request [1] currently open to set USE_POINT_Z_M as ON by
> > default. I recently made an update to this for the CMake build [2].
> > 
> > As Tamas and Julien-Samuel have pointed in the comments on the pull requests
> > it may be better to simply use PointZM throughout MapServer by default, and
> > remove this option altogether.
> > 
> > There are currently issues with MapScript bindings and testing where the
> > output is not guarenteed due to the compile options and could lead to
> > memory corruption issues.
> > 
> > Possible risks are breaking some tests (which can be updated), and reducing
> > performance. I presume there is no easy way to measure performance between
> > changes / releases?
> > 
> > Does anyone have any thoughts on reasons not to use PointZM by default
> > throughout MapServer?
> 
> I'm +1 on enabling ZM unconditionaly. This is a topic I raised a few years 
> ago.
> I found this thread
> https://lists.osgeo.org/pipermail/mapserver-users/2017-July/080102.html
> where I did a small benchmark. ZM was 2% slower.
> 
> Even
> 
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com
>