Re: [gdal-dev] Vector Tile size change in Ogr2Ogr

Hi, Bounds and other metadata are explained in https://github.com/mapbox/mbtiles-spec/blob/master/1.3/spec.md. "The metadata table SHOULD contain these four rows: bounds (string of comma-separated numbers): The maximum extent of the rendered map area. Bounds must define an area covered by all zo

Re: [gdal-dev] Vector Tile size change in Ogr2Ogr

-- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Vector Tile size change in Ogr2Ogr

Thank you Even. Can you please explain the BOUNDS usage? How it is related to EXTENT? Regards, Rajesh -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/

Re: [gdal-dev] Vector Tile size change in Ogr2Ogr

Le 11/03/2021 à 10:46, MRRAJESH a écrit : Developers, What is the default tile size when we generate the Vector tiles (MVT) using Ogr2Ogr? Can we set the tile size as 512x512? See the EXTENT dataset creation option of https://gdal.org/drivers/vector/mvt.html#dataset-creation-options It def

[gdal-dev] Vector Tile size change in Ogr2Ogr

Developers, What is the default tile size when we generate the Vector tiles (MVT) using Ogr2Ogr? Can we set the tile size as 512x512? Regards, Rajesh -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-dev mailing list