[mapserver-dev] Dropping support for GDAL < 2 ?

[Seth G]

+1 on dropping old GDAL versions for future MapServer releases. We've done this with SWIG and CMake recently. 

With regards to the Mapfile syntax, there is precedent with the PROCESSING "OO:KEY=VALUE" approach in FORMATOPTION:

> FORMATOPTION "METADATA_ITEM:PRODUCER=MapServer, with GDAL trunk"

A new Mapfile keyword will require changes for SWIG support I believe?

My preference from a syntax point of view (although blissfully unaware of the implementation issues it will raise!) would be to turn PROCESSING into a block with the same syntax as METADATA e.g. 

PROCESSING
   "CONTOUR_INTERVAL" "5"
   "CLUSTER_GET_ALL_SHAPES" ON"
   "OPENOPTION_KEY1" "VALUE1"
   "OPENOPTION_KEY2" "VALUE2"
END

SWIG could then use a dict type approach in the same way as METADATA to update and add, modify keys and values in the PROCESSING block. 

Seth


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

On Thu, Aug 22, 2019, at 3:46 PM, Even Rouault wrote:
> On jeudi 22 août 2019 15:29:29 CEST Tamas Szekeres wrote:
> > Even,
> > 
> > I agree with dropping the support if needed.
> > The open option seems to be a driver specific attribute, wouldn't it be
> > sufficient to use a processing directive for that?
> 
> I see PROCESSING as more for MapServer own special treatments.
> And you would need to somehow indicate that the processing option is an open 
> option, so something like
> 
> PROCESSING "OO:KEY=VALUE"
> 
> I find
> OPENOPTION "key" "value"
> cleaner
> 
> Even
> 
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev