Re: [gdal-dev] About CMake build again

2017-10-29 Thread Dmitry Baryshnikov
Hi Hiroshi, I think that anyhow the current logic of makefile mast be transfer to CMake. See the https://github.com/OSGeo/gdal/blob/trunk/gdal/configure.ac or how I did it in lib_gdal repository. This logic is rather complicated! About vagrant: $ vagrant up bash: vagrant: command not found

Re: [gdal-dev] About CMake build again

2017-10-29 Thread Dmitry Baryshnikov
Hi Kurt, And how to deal with non Linux builds like Windows MSVC, mac OS XCode etc.? Best regards, Dmitry 29.10.17 17:17, Kurt Schwehr пишет: While autoconf isn't pretty, it has done me the least amount of harm of any of the major build systems. Without patches for the downstream packager

Re: [gdal-dev] About CMake build again

2017-10-29 Thread Hiroshi Miura
Hi Dmitry, On 2017年10月29日 07:21, Dmitry Baryshnikov wrote: > > Hi Hiroshi, > > I tried to test you solution: > Thank you for testing and sharing your experience. It is working in progress status. And it is based on different policy with your solution.   Now I don't write document about a policy

Re: [gdal-dev] About CMake build again

2017-10-29 Thread Kurt Schwehr
While autoconf isn't pretty, it has done me the least amount of harm of any of the major build systems. Without patches for the downstream packagers and CI (travis/appveyor), I would be -1. e.g. debian/ubuntu, redhat/centos, macport/brew/fink, and others With those patches, I'm -0. BTW, It's no

Re: [gdal-dev] WCS driver

2017-10-29 Thread Ari Jolma
Even Rouault kirjoitti 29.10.2017 klo 12:49: > So, treat lat,lon and north,east always as exceptions. And in this case > add an option to make that exception when appropriate and when writing > the BoundingBox into the request. (But not when reading GridOrigin. > However, I still have to see

Re: [gdal-dev] About CMake build again

2017-10-29 Thread Dmitry Baryshnikov
Hi Alexander, Please read carefully that I wrote before. There are 3 options: 1. Build gdal with all dependencies getting them from github (WITH_EXTERNAL). Preferable for Windows 2. Build gdal using the system libraries. Preferable for Linux 3. Build gdal using the dependency libra

Re: [gdal-dev] Add timestamp field with value to table during ogr2ogr operation

2017-10-29 Thread Even Rouault
On dimanche 29 octobre 2017 09:58:06 CET Bo Victor Thomsen wrote: > To the list - > > I'm converting shapefiles to postgres tables using ogr2ogr. As usual > with ogr2ogr, it works very well. > > Now I want to automatically add an extra column "created" with the > current timestamp during the ogr2

Re: [gdal-dev] WCS driver

2017-10-29 Thread Even Rouault
> So, treat lat,lon and north,east always as exceptions. And in this case > add an option to make that exception when appropriate and when writing > the BoundingBox into the request. (But not when reading GridOrigin. > However, I still have to see what other servers say.) I'm not sure what you exa

Re: [gdal-dev] WCS driver

2017-10-29 Thread Ari Jolma
Even Rouault kirjoitti 29.10.2017 klo 11:52: The "tradition" in GDAL drivers such as GML, WFS is to strip AXIS from the CRS WKT exposed when they are in the "annoying" lat,long and northing,easting, From the GML driver: {{{ if (poSRS != NULL && m_bInvertAxisOrderIfLatLong && GML_IsSRSLatL

Re: [gdal-dev] WCS driver

2017-10-29 Thread Even Rouault
Hi Ari, > > I'd like to have your comment on this. > > Ari Jolma kirjoitti 28.10.2017 klo 17:39: > > Reading MapServer code, it seems to be based on the idea that x,y is > > always east,north and when it writes BoundingBox, it swaps x and y if > > the projection is inverted (like 4326). It does

Re: [gdal-dev] WCS driver

2017-10-29 Thread Ari Jolma
jratike80 kirjoitti 28.10.2017 klo 13:10: Ari Jolma-2 wrote The case of GeoServer is also strange https://msp.smartsea.fmi.fi/geoserver/wcs?SERVICE=WCS&VERSION=1.1.1&REQUEST=GetCoverage&IDENTIFIER=smartsea%3Aeusm2016&FORMAT=image%2Ftiff&BOUNDINGBOX=61610,7303970,61630,7303990,urn:ogc:def:crs:EPS

[gdal-dev] Add timestamp field with value to table during ogr2ogr operation

2017-10-29 Thread Bo Victor Thomsen
To the list - I'm converting shapefiles to postgres tables using ogr2ogr. As usual with ogr2ogr, it works very well. Now I want to automatically add an extra column "created" with the current timestamp during the ogr2ogr operation. Something like this: ogr2ogr .  -sql "SELECT *, CURREN