[mapserver-dev] RFC 125: Support for CONNECTIONOPTIONS in mapfiles

[Lime, Steve D (MNIT)]

Hi Even (and all): I think the RFC looks solid. In terms of implementation I was wondering if we might consider a single OPTIONS block so that the concept (and keyword) might build some commonality across objects (for example, OUTPUTFORMAT could use this). I'd leave METADATA and VALIDATION blocks alone. So one could write:

OPTIONS
  # data options
  "key" "value"

  # connection options
  "FLATTEN_NESTED_ATTRIBUTES" "YES"

  # processing options
  "NATIVE_FILTER" "d=234"
END 

as opposed to creating a DATAOPTIONS, CONNECTIONOPTIONS and PROCESSINGOPTIONS... That would make the mapfile syntax cleaner and keep MapScript simpler.

--Steve

-----Original Message-----
From: mapserver-dev [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Even Rouault
Sent: Monday, September 30, 2019 10:00 AM
To: mapserver-dev at lists.osgeo.org
Subject: [mapserver-dev] RFC 125: Support for CONNECTIONOPTIONS in mapfiles

Hi,

As discussed a few weeks ago, I've implemented support for specifying GDAL/OGR
open options through a new Mapfile syntax

See https://mapserver.org/development/rfc/ms-rfc-125.html

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com/en/home/

_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-dev