Fix submitted in https://github.com/OSGeo/gdal/pull/12230
Le 30/04/2025 à 08:22, Rahkonen Jukka via gdal-dev a écrit :
Hi, Your syntax with the "gdal" frontend is correct. This command is accepted: gdal vector convert -f MVT --co NAME=foo in.shp out The reason for the error may be in the commas in the value of the TILING_SCHEME. The same error message can be triggered with gdal vector convert -f MVT --co NAME="foo,bar" in.shp out The uncommon creation option value makes probably confusion due to this mechanism https://gdal.org/en/latest/development/rfc/rfc104_gdal_cli.html#repeated-values-multi-valued-options The new front-end is announced to be unstable and experimental because of this kind of issues. Thank you for finding out one. -Jukka Rahkonen- ________________________________________ Lähettäjä: gdal-dev käyttäjän Richard Greenwood via gdal-dev puolesta Lähetetty: Keskiviikko 30. huhtikuuta 2025 5.52 Vastaanottaja: GDAL List Aihe: [gdal-dev] gdal 3.11 -dsco vs --co In the docs at 'latest'https://gdal.org/en/latest/drivers/vector/mvt.html#dataset-creation-optionsit seems like -dsco needs to be --co for the new 'gdal' front-end cli but still -dsco for the the old 'ogr2ogr'. Am I correct or am I overlooking something?I am also getting an error with 'gdal vector pipeline write' when I use: --co TILING_SCHEME="EPSG:3738,1622000,1284700,686000"ERROR 1: write: Invalid value for argument 'creation-option'. <KEY>=<VALUE> expectedThanks-- Richard W. Greenwood _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
-- http://www.spatialys.com My software is free, but my time generally not. _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
