Even,
thank you for your quick answer. Just one quick question - is it possible to
do what you suggest with vector tiles in a user-defined tiling scheme (CRS
which I use is EPSG:5514)?
Thanks!
Linda
-- Původní e-mail --
Od: Even Rouault
Komu: Linda Kladivová , gdal-dev@
Actually you may need to actually use -clipdst to avoid generating
partial tiles.
Le 31/01/2023 à 20:02, Even Rouault a écrit :
Linda,
you'll have to do a bit of manual work. You may use the -spat option
of ogr2ogr with bounds that exactly match the bounds of affected MVT
tiles in EPSG:3857,
Linda,
you'll have to do a bit of manual work. You may use the -spat option of
ogr2ogr with bounds that exactly match the bounds of affected MVT tiles
in EPSG:3857, and then move the generated .pbf tiles back to the full
dataset.
Even
Le 31/01/2023 à 19:42, Linda Kladivová a écrit :
Hello
Hello guys,
it is possible to update the MVT tileset using ogr2ogr?
My data often changes and I would need to reseed tiles in the specific area
given by MBR.
I am looking for similar functionality as GeoServer provides (https://docs.
geoserver.org/latest/en/user/geowebcache/rest/seed.htm
Hi Seth,
Le 31/01/2023 à 14:20, Seth G a écrit :
Hi Even,
Is it correct to say the workflow for OGR layer in MapServer is similar to that
of QGIS?
Not quite, because currently MapServer as you point out use
"materialized geometries" to get the points, the number of rings in a
polygons, etc.
Hi Even,
Is it correct to say the workflow for OGR layer in MapServer is similar to that
of QGIS?
OGR features / geometries are loaded, and then converted into MapServer shapes
using the OGRGeometry function [1]. Would using WKB here be any more performant?
The PostGIS driver already has code to
Hi,
Please find for review "RFC 92 text: WKB Only geometries" at
https://github.com/OSGeo/gdal/pull/7149
This RFC provides shortcuts to avoid instantiation of full OGRGeometry
instances
in scenarios where only the WKB representation of geometries is needed. The
hope is to save CPU time.
Thi