Re: [gdal-dev] Check validity of geometries before writing them into vector tiles?

All, Geometry validity with polygons is really hard. The only solution at Mapbox we found to fix this properly for Vector Tiles that we create was to modify an existing algorithm to solve all the potential problems of geometry validity. The result of this is https://github.com/mapbox/wagyu/ which

Re: [gdal-dev] ZSTD compression for GeoTIFF

Even Rouault-2 wrote > Hi, > > I've just pushed in libtiff upstream, and its internal copy in GDAL, > support for zstandard/ > zstd compression [1], and the appropriate changes in the GDAL GeoTIFF > driver. > This requires building libtiff (or GDAL with its internal libtiff copy) > against

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

Added the delete and validate works now. Thanks! On Wed, Feb 14, 2018 at 11:28 AM, Even Rouault wrote: > On mercredi 14 février 2018 11:00:01 CET Kurt Schwehr wrote: > > > (working from pretty close to head...) > > > > > > A follow up question on how to create cogeo

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

On mercredi 14 février 2018 11:00:01 CET Kurt Schwehr wrote: > (working from pretty close to head...) > > A follow up question on how to create cogeo files... > > I appear to need to do additional work to set BLOCK_OFFSET_?_?. How do I > go about this? > > I'm trying to create a cogeo without

Re: [gdal-dev] Creating Cloud Optimized GeoTIFFs

(working from pretty close to head...) A follow up question on how to create cogeo files... I appear to need to do additional work to set BLOCK_OFFSET_?_?. How do I go about this? I'm trying to create a cogeo without gdal_translate in java by using create and createcopy like this:

Re: [gdal-dev] Check validity of geometries before writing them into vector tiles?

Even Rouault wrote: > Perhaps you could play with the SIMPLIFICATION and SIMPLIFICATION_MAX_ZOOM > options ? Sure, as I wrote I admit that my test did not make much sense, but trying things before reading the manual sometimes reveals something interesting.   > Perhaps you should also use an

Re: [gdal-dev] Check validity of geometries before writing them into vector tiles?

On mercredi 14 février 2018 15:10:57 CET Rahkonen Jukka (MML) wrote: > Hi, > > I admit that my test was somewhat lunatic but I took some random dataset > from Finland with 68101 polygons and converted data into MVT with default > settings which means that minzoom was 0. As a result 12196 of the

[gdal-dev] ZSTD compression for GeoTIFF

Hi, I've just pushed in libtiff upstream, and its internal copy in GDAL, support for zstandard/ zstd compression [1], and the appropriate changes in the GDAL GeoTIFF driver. This requires building libtiff (or GDAL with its internal libtiff copy) against libzstd >= 1.0 My findings are that

[gdal-dev] Check validity of geometries before writing them into vector tiles?

Hi, I admit that my test was somewhat lunatic but I took some random dataset from Finland with 68101 polygons and converted data into MVT with default settings which means that minzoom was 0. As a result 12196 of the source polygons were written into the 0-level protobuf tile (in EPSG:3067