Re: [gdal-dev] Converting multilayer KML to single layer output

On mercredi 30 novembre 2016 05:44:54 CET Rutger wrote: > Hey, > > I am trying to convert a kml-file containing multiple layers to a new output > (GeoJSON for example), which only supports a single layer. All geometry > types in the kml are identical, all polygon. > > The only way i can make it

Re: [gdal-dev] ogr2ogr - exclude table option?

Thanks Even! The VACUUM command worked and indeed the file is now much smaller. Thank you for adding this information to the Geopackage documentation! I wasn't aware that I could run any SQL command through ogrinfo. Nice! Greetings, Andreas Am 30.11.2016 um 21:24 schrieb Even Rouault: On

Re: [gdal-dev] ogr2ogr - exclude table option?

On mercredi 30 novembre 2016 21:11:14 CET Andreas Neumann wrote: > Hi Even, > > Thanks. I will use the 'ogrinfo your.gpkg -sql "DROP TABLE table_name"' > trick for now. > > One thing though: I noticed that the filesize doesn't really shrink. Is > there a way to compact/vacuum the geopackage

Re: [gdal-dev] ogr2ogr - exclude table option?

Hi Even, Thanks. I will use the 'ogrinfo your.gpkg -sql "DROP TABLE table_name"' trick for now. One thing though: I noticed that the filesize doesn't really shrink. Is there a way to compact/vacuum the geopackage after removal of the table? The table I remove is rather big - so it would

[gdal-dev] Request for API Key parameter to be added to the TMS driver for Google and VirtualEarth/Bing

Request: Need an APIKey parameter for the TMS driver for use with VirtualEarth (Bing) and Google. The requests still work without the API key. But, according to Google and Bing, the API Key is now required to legally use their services. The API keys are free from their web sites. For low

[gdal-dev] WMTS - Need TileLevel option Servers responding with bad capabilities

Question: Is it possible to get a TileLevel option added to the new GDAL WMTS driver? Reason: WMTS servers at USGS and ESRI are returning XML Capabilities with TileLevel 18 (Google) or TileLevel 19 (default028mm). The USGS help desk said that the tile servers are only serving up to Tile

Re: [gdal-dev] Seg fault & error running gdal_rasterize on a non georeferenced raster

On mercredi 30 novembre 2016 18:43:24 CET Ari Jolma wrote: > At gdalrasterize.cpp:349 there is a call to Transformer but the > TransformArg is NULL, which leads to segfault. Above the call there is a > comment: > > // TODO: We need to add all appropriate error checking at some point. > >

[gdal-dev] ogr2ogr - exclude table option?

Hi, I want to convert a whole Postgis schema to a geopackage. This works fine with ogr2ogr -f GPKG av_1700.gpkg PG:'dbname=dbname host=localhost schemas=schemaname' Now - my problem is that the schema contains 64 tables and I want to convert all tables except one table. Is there a trick

Re: [gdal-dev] Seg fault & error running gdal_rasterize on a non georeferenced raster

Bugger. That segfault should be turned into a clean failure. I looked a bunch and wasn't sure how to safely do that. This didn't do the job... the segfault happens somewhere after this. svn diff gdalrasterize.cpp Index: gdalrasterize.cpp

Re: [gdal-dev] Seg fault & error running gdal_rasterize on a non georeferenced raster

On 29 November 2016 at 22:36, Even Rouault wrote: > Tim, > > Could you provide the dataset to reproduce as well ? And it seems your > Python script is not valid since the 'sr' variable passed in > rast_ogr_ds.CreateLayer( 'poly', srs=sr ) is not defined. Hello,

Re: [gdal-dev] Seg fault & error running gdal_rasterize on a non georeferenced raster

On mercredi 30 novembre 2016 06:44:11 CET Mark Johnson wrote: > This may be a similar problem to what was mentioned here: > > #6721: Simplifing use of gdalwarp with cutline with non-georeferenced > rasters > > https://trac.osgeo.org/gdal/ticket/6721 > (which has not been reacted to) > > There

Re: [gdal-dev] How does WMTS driver detect DataWindow?

Hi, I got to understand why WMTS service has so large WGS84 bounding box in GetCapabilities. It is because the native EPSG:3067 bounding box is first converted into WGS84 by using a densified polygon geometry. The WGS84BoundingBox is then the envelope of this warped polygon. Because of