Re: [gdal-dev] transformation failure from WGS 84 to GRS 1980

I'm running Arch Linux :) On Nov 10, 2017 01:08, "Andre Joost" wrote: > Am 09.11.2017 um 20:52 schrieb Donovan Cameron: > >> Afternoon! >> >> I recently upgraded to gdal 2.2.2 from 2.1 on linux and when I try to >> use ogr2ogr to append/update an existing table in

Re: [gdal-dev] Call for discussion on RFC 70: Guessing output format from output file name extension

Sorry, I overlooked the 'output filename to guess', while reading the PR and title. Mark ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Call for discussion on RFC 70: Guessing output format from output file name extension

On vendredi 10 novembre 2017 13:40:32 CET Mark Johnson wrote: > > ogr2ogr output.gpkg input.shp Where would you read the Magic-Headers in > > this case? > > Before the input file is opened. Mark, this RFC is about *non existing yet output* files (can't think how to make its title clearer :-)),

Re: [gdal-dev] Call for discussion on RFC 70: Guessing output format from output file name extension

> > ogr2ogr output.gpkg input.shp Where would you read the Magic-Headers in > this case? Before the input file is opened. Read the first 100 bytes, compare with known signatures if ((memcmp (blob, tiff_signature_big, 4) == 0) && (memcmp (blob, tiff_signature_little, 4) == 0)) { return

Re: [gdal-dev] GDAL make error

> Why would extra options be enabled when we haven't made any changes to the > makefile? And are these extra options likely to be the failure in building > libgdal.so? Jon, Make sure you do a "make clean" as the configuration has changed Even -- Spatialys - Geospatial professional services

Re: [gdal-dev] Call for discussion on RFC 70: Guessing output format from output file name extension

mj10777 wrote > Reading the Magic-Header signatures first and then guessing from the file > extension may be a better approach. Hi, The title says "Guessing output format from output file name extension", like in ogr2ogr output.gpkg input.shp Where would you read the Magic-Headers in this

Re: [gdal-dev] Extracting keys & values from OSM Planet

Hi Nikos, I think it would be quite easy to hack up a python script that generates a osmconf.ini with the configparser module and calls ogr2ogr via subprocess to process the data, but I don’t have done anything in that regard yet. I don’t remember exactly anymore why I chose osmconvert over

Re: [gdal-dev] Call for discussion on RFC 70: Guessing output format from output file name extension

Reading the Magic-Header signatures first and then guessing from the file extension may be a better approach. In spatialite gaia_exif.c, the function gaiaGuessBlobType has a collection of signatures to start with, combined with spatialite.c guess_mime_type returning the mime type as string.

[gdal-dev] GDAL make error

Hi all, We're having problems with a GDAL build from source and hope that someone here can point us in the right direction. We've got a server running Scientific Linux 7 and we're using Jenkins 1.602.2 for CI. Every job builds our application from scratch, which includes a build of gdal. Up

[gdal-dev] Wiki page for WCS discussion and best practices created

Hi, As an initial step I created a new page about WCS into the developers section of the GDAL wiki https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability I suppose that all who have OSGeo user account can edit the page. -Jukka Rahkonen- ___

Re: [gdal-dev] ZMAP driver, support for comment section "+"

Olivier Chatry wrote > I would gladly make a patch, but I'm not sure how I should proceed. > > Any help ? Hi, Have you already found http://www.gdal.org/frmt_various.html and a link to informal specification https://lists.osgeo.org/pipermail/gdal-dev/2011-June/029173.html and the code of the

Re: [gdal-dev] transformation failure from WGS 84 to GRS 1980

Am 09.11.2017 um 20:52 schrieb Donovan Cameron: Afternoon! I recently upgraded to gdal 2.2.2 from 2.1 on linux and when I try to use ogr2ogr to append/update an existing table in PostgreSQL/PostGIS the command fails because it can't apply a transformation. The command works fine in gdal 2.1.