Re: [gdal-dev] Motion: add Javier Jiménez Shaw to GDAL PSC
+1 Mateusz On Sat, 16 Sept 2023, 13:32 Even Rouault, wrote: > Hi, > > I would like to nominate Javier Jiménez Shaw for GDAL PSC membership. > Javier has been involved with GDAL for quite a time now, as a responsive > user & ticket reporter, and has occasionally contributed fixes. Javier > is well anchored in our ecosystem, with deep knowledge of CRS topics and > PROJ (I've also nominated him for PROJ membership), contributing to PDAL > as well. As part of his job, he's involved in orthomosaic/raster > generation out of images and photogrammetry pipelines. His perspective > would be most welcome. > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Grant Dan Baston Merge Rights
+1 Mateusz On Tue, 12 Sept 2023 at 21:21, Howard Butler wrote: > > Dear PSC, > > Dan Baston is an active GDAL maintainer who does not currently have merge > rights. Let's fix that so he can get more work done without waiting on > someone to merge things up :) > > /me starts with +1 > > Howard > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Adopt GDAL 3.7.2RC1 as 3.7.2 release
+1 Mateusz On Thu, 7 Sept 2023, 22:43 Even Rouault, wrote: > Hi, > > Motion: > > Adopt GDAL 3.7.2RC1 as 3.7.2 release > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Inquiry about GDAL's Capabilities for Converting 3D .DGN Files to KML/GeoJSON
On Tue, 29 Aug 2023 at 11:36, Shahrukh Mirza Nawandish < mirza.nawand...@haritaevi.com> wrote: > Hello everyone, > > I am inquiring about GDAL's capabilities in converting 3D .DGN files to > KML/GeoJSON or any other formats. If GDAL supports this conversion, > https://gdal.org/programs/ogr2ogr.html https://gdal.org/drivers/vector/dgn.html https://gdal.org/drivers/vector/dgnv8.html https://gdal.org/drivers/vector/geojson.html https://gdal.org/drivers/vector/kml.html -- Best regards, Mateusz Loskot ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Adopt GDAL 3.7.0RC1 as 3.7.0 release
+1 Mateusz On Tue, 9 May 2023 at 14:33, Daniel Morissette wrote: > > +1 > > Daniel > > On 2023-05-08 09:02, Even Rouault wrote: > > Hi, > > > > Motion: > > > > Adopt GDAL 3.7.0RC1 as 3.7.0 release > > > > Starting with my +1 > > > > Even > > > > -- > Daniel Morissette > Mapgears Inc > T: +1 418-696-5056 #201 > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Adopt GDAL 3.6.3RC1 as 3.6.3 release
+1 Mateusz On Thu, 9 Mar 2023 at 16:41, Even Rouault wrote: > > Same motion, just fixing the title to reflect the correction version > number, as kindly pointed out. > > Le 09/03/2023 à 16:33, Even Rouault a écrit : > > Hi, > > > > Motion: > > > > Adopt GDAL 3.6.3RC1 as 3.6.3 release > > > > Starting with my +1 > > > > Even > > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Adopt GDAL 3.6.3RC1 as 3.6.1 release
+1 Mateusz On Thu, 9 Mar 2023 at 16:33, Even Rouault wrote: > > Hi, > > Motion: > > Adopt GDAL 3.6.3RC1 as 3.6.3 release > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Using GDAL with opencv in C++ there is errors under windows
On Tue, 7 Mar 2023 at 09:32, Raivo Rebane wrote:
>
> I minimized the program :
>
> #include
> #include
> #include
> #include
>
> int main()
> {
> GDALAllRegister();
> GDALDataset* dataset =
> static_cast(GDALOpen("634632_2012_tava.tiff", GA_ReadOnly));
> GDALClose(dataset);
>
> return 0;
> }
>
The errors like
LNK2001 unresolved external symbol
typically mean a program is not being linked against required libraries.
You need to refer to documentation of the compilation toolset you are using
in order to learn how to configure build of your program properly,
how to pass gdal.lib to its linker, etc.
If you are using CMake, you can follow this recommendation
https://gdal.org/development/cmake.html
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Report on GEOS maintenance grant
On Mon, 27 Feb 2023 at 15:34, Daniel Baston wrote: > > As February comes to a close, I’m winding down the GEOS maintenance work that > the GDAL PSC funded in 2022 [1]. Dan, this is a great list of efforts, thank you. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 93: OGRLayer::UpdateFeature() method
+1 Mateusz On Wed, 22 Feb 2023 at 10:20, Even Rouault wrote: > > Hi, > > Motion: adopt RFC 93: OGRLayer::UpdateFeature() method > > https://github.com/OSGeo/gdal/pull/7249 > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] OpenJPEG JPEG2000 Driver
On Wed, 15 Feb 2023 at 19:14, Simon Eves wrote: > > I am building OpenJPEG with SHARED_LIBS off, as we only need the static > version for GDAL. > GDAL itself builds default (SHARED_LIBS on) as we need static for our main > product build, I know nothing about OpenJPEG build configuration, but GDAL uses CMake's native BUILD_SHARED_LIBS to control the shared/static library build > We don't need to link GDAL statically into any higher-level shared libs, just > the main monolithic executable. > [...] > My main concern remains the need to hack the configure script to get the GDAL > build to agree that OpenJPEG is usable, In theory, BUILD_SHARED_LIBS=ON could/should cascade to all dependencies - you want static GDAL, good, we will assume you link it against static OpenJPEG, etc. However, I remember, I had to modify the old NMAKE makefile to make GDAL link against static curl and a few others I did build as static libraries, e.g. forcing those deps as static-s and adding list of dependencies of those dependencies, etc. So, I'd say hacking build config for uncommon builds nothing buggy or unexpected. Best regards. -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] OpenJPEG JPEG2000 Driver
On Wed, 15 Feb 2023 at 01:34, Simon Eves wrote: > > I tried adding -DCMAKE_CPP_FLAGS="-fPIC" -DCMAKE_CXX_FLAGS="-fPIC" to the > OpenJPEG build CMake invocation, but that made no difference. > More CMake-idiomatic way is to use -DCMAKE_POSITION_INDEPENDENT_CODE=ON instead. It used to be there https://github.com/OSGeo/gdal/commit/a0128debca5dd77a64188cc7ac3ba60866a70e89 until https://github.com/OSGeo/gdal/issues/5649 and there is GDAL-specific variable now -DGDAL_OBJECT_LIBRARIES_POSITION_INDEPENDENT_CODE=ON https://github.com/OSGeo/gdal/blob/master/gdal.cmake#L42-L43 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 91: GDALDataset::Close() method
+1Mateusz On Wed, 25 Jan 2023 at 12:56, Even Rouault wrote: > > Hi, > > Motion: adopt RFC 91: GDALDataset::Close() method > > https://github.com/OSGeo/gdal/pull/7108 > > Starting with my +1, > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Approve RFC90: Direct access to compressed raster data
+1 Mateusz On Mon, 16 Jan 2023, 18:02 Even Rouault, wrote: > Hi, > > Motion: Approve RFC90: Direct access to compressed raster data: > > https://github.com/OSGeo/gdal/pull/7020 > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC89: SQL query logging callback
+1 Mateusz On Tue, 20 Dec 2022 at 04:58, Even Rouault wrote: > > It would be great if a few other PSC members could cast their vote. > > Even > > Le 15/12/2022 à 23:38, Even Rouault a écrit : > > +1 Even > > > > Le 12/12/2022 à 15:10, ElPaso a écrit : > >> Hi, > >> > >> Motion: > >> > >> Adopt RFC89: SQL query logging callback [1] > >> > >> A draft implementation is available at [2]. > >> > >> An example of how client code could make use of this new > >> functionality is avaiable for QGIS at [3]. > >> > >> Kind regards. > >> > >> > >> [1] https://github.com/OSGeo/gdal/pull/6837 > >> > >> [2] > >> https://github.com/elpaso/gdal/tree/rfc89_sql_logging_callback_implementation > >> > >> [3] https://github.com/elpaso/QGIS/tree/ogrprovider-sql-logging > >> > >> > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC88: Use GoogleTest framework for C/C++ unit tests
+1 Mateusz On Mon, 21 Nov 2022 at 12:40, Even Rouault wrote: > > Hi, > > Motion: > > Adopt RFC88: Use GoogleTest framework for C/C++ unit > tests(https://github.com/OSGeo/gdal/pull/6720) > > Starting with my +1, > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Call for discussion: RFC88: Use GoogleTest framework for C/C++ unit tests
On Wed, 16 Nov 2022 at 19:42, Even Rouault wrote: > > Text at https://github.com/OSGeo/gdal/pull/6720 > > The document proposes and describes conversion of the existing C/C++ > autotest suite to use the `GoogleTest > framework <https://github.com/google/googletest>`__. > > GoogleTest is a popular and maintained framework for C/C++ test > writing, that is a better replacement for the `TUT framework > <https://github.com/mrzechonek/tut-framework>`__ that we use currently. +1 Mateusz It was me who 'polluted' GDAL with TUT and here it is why I did it: It was a very long time ago to support porting GDAL (and GEOS too) to Windows CE platform which was very limited in terms of C and C++ support. And. we also had to develop some C library routines https://wcelibcex.sourceforge.net/ And, Python for Windows CE was very limited. And, it was much easier to debug C/C++ than Python, So, I decided to start C/C++ counterpart of the autotest suite. At that time, TUT was small, portable, feature-complete framework that we incorporated by copying its single header. Since the C++ autotest is still alive, switching to a modern test framework is much desired and Google Test is sensible choice. I see no reason to stay with TUT, which is rather a niche library nowadays. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Add Alessandro Pasotti as GDAL maintainer
+1 Mateusz On Mon, 14 Nov 2022, 16:45 Howard Butler, wrote: > Dear PSC, > > As a result of our fundraising activity and development of NumFOCUS as a > financial conduit, it is my pleasure to put forward a motion to approve > Alessandro Pasotti as a contracted GDAL maintainer for the period beginning > on November 21st, 2022 and ending November 21st, 2023. > > Details of the maintenance tasking and duties can be found at the > previously approved RFC 83 > https://gdal.org/development/rfc/rfc83_use_of_project_sponsorship.html > > The terms of the contract are for a maximum of 250 hours at 110 €/hr. > > Alessandro will plan to focus on GDAL tasks that make it easier to > developer GUI applications like QGIS (of which he is also a very active > contributor). This includes testing, APIs, and driver hardening. > > Howard > > PS I will coordinating the contracting activity in my role as the GDAL > NumFOCUS contracting liaison, with Frank Warmerdam acting as the secondary. > Please contact us directly with any comments or concerns. > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 87: Signed int8 data type for raster
+1 Mateusz p. s. An alias wouldn't hurt, not a substantial change but could be useful, could be just tossed in. On Mon, 14 Nov 2022, 13:22 Even Rouault, wrote: > Hi, > > I feel the discussion phase has finished. There were a few questions > about the existing GDT_Byte unsigned 8-bit integer type, if it should be > renamed/aliased/etc, but no obvious conclusion emerged from this, and > I'd suggest we keep with the status-quo with GDT_Byte, and the RFC > remains on just adding GDT_Int8 for signed 8-bit integer. > > Motion: > > Adopt RFC 87: Signed int8 data type for raster > (https://github.com/OSGeo/gdal/pull/6634) > > Starting with my +1, > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt GDAL 3.5.3RC1 as final 3.5.3 release
+1 Mateusz Thank you! On Thu, 27 Oct 2022 at 14:23, Even Rouault wrote: > > Hi, > > Motion: > > Adopt GDAL 3.5.3RC1 as final 3.5.3 release > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Approve Even Rouault as a contracted GDAL maintainer for 2022-2023
+1 Thank you Even a ton ! On Sat, 27 Aug 2022, 14:42 Howard Butler, wrote: > Dear PSC, > > It has come to my attention that Even's term as a GDAL Maintainer > officially ended 31 JUL 2022. I propose that we extend him for another year > from 01 AUG 2022 to 31 JUL 2023 under the previous terms and conditions. > > Although a small formality, we should make sure to keep a small bit of > process around these things. > > /me starts with +1 > > Howard > > PS, expect a GDAL Sponsorship Annual Report next week. > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt GDAL 3.5.1RC2 as final 3.5.1 release
+1 Mateusz On Fri, 1 Jul 2022 at 09:14, Even Rouault wrote: > > Hi, > > Motion: > > Adopt GDAL 3.5.1RC2 as final 3.5.1 release > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] building on macOS - fatal error: 'direct.h' file not found
On Wed, 29 Jun 2022 at 03:50, wrote: > > > > You can still build with Autotools! > > > [...] > Therefore the purpose of this exercise is to get the CMake system > working. So if my understanding is correct, avoiding CMake is not an > option for me if I want to use GDAL 3.6. Correct. CMake has been out there for a very ling time and it is battle-tested on macOS, and other systems too, even on some exotic ones. CMake is like democracy, not ideal, but it's best the humanity has worked out so far that works for well all countries. I suggest to stop CMake rants. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] building on macOS - fatal error: 'direct.h' file not found
On Tue, 28 Jun 2022 at 03:28, Nik Sands wrote:
> However, I’m getting numerous build errors, starting with the following error
> when running cmake to build GDAL 3.5.0:
>
> fatal error: 'direct.h' file not found
Check cmake command output for
-- Looking for direct.h
and what is the look-up result it reports.
GDAL's CMake configuration checks for direct.h
https://github.com/OSGeo/gdal/blob/14be6dea87fd44dc58c3e6a2befb5913147ddbc7/cmake/helpers/configure.cmake#L38
> I’m a hobbyist and not a professional developer, so my understanding of these
> things is quite limited.
You can still build with Autotools!
> However, my research so far indicates that ‘direct.h’ is a Windows-specific
> header file
Correct.
> and therefore perhaps cmake has not been configured correctly for macOS in
> this GDAL distribution?
As per the earlier link, it's simple, it runs
`check_include_file("direct.h" HAVE_DIRECT_H)`
and if the header is found, then HAVE_DIRECT_H is set.
The CMake configuration does almost the same as the Autotools does:
https://github.com/OSGeo/gdal/blob/14be6dea87fd44dc58c3e6a2befb5913147ddbc7/configure.ac#L295
Question is, is HAVE_DIRECT_H set on macOS or not.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 86 Column-oriented read API for vector layers
+1 Mateusz On Fri, 10 Jun 2022 at 11:24, Even Rouault wrote: > > Hi, > > As the discussion seems to have calmed down, I move to adopt RFC 86: > Column-oriented read API for vector layers : > https://github.com/OSGeo/gdal/pull/5830 > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 3.5.0 is released
On Fri, 13 May 2022 at 14:29, Even Rouault wrote: > > The 3.5.0 release is a new feature release with the following highlights: > > * [RFC 84](https://gdal.org/development/rfc/rfc84_cmake.html): >Addition of a CMake build system, which deprecates the existing >autoconf/automake and nmake build systems, that will be removed Awesome! Thank you very much to all involved in making the CMake into GDAL! The initial attempt (codename: cmake4gdal) was made around 2011 by folks at Kitware... :) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt GDAL 3.4.3 RC2
+1 On Mon, 2 May 2022, 16:12 Howard Butler, wrote: > > > > On May 1, 2022, at 3:45 PM, Even Rouault > wrote: > > > > Hi, > > > > Motion: > > > > Adopt GDAL 3.4.3 RC2 as final 3.4.3 release > > > > Starting with my +1 > > +1 > > Howard > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] how to build gdal 3.4.2
On Tue, 26 Apr 2022, 08:28 Kavitha K, wrote: > Hi All, > > I have downloaded gdal-3.4.2 > cd gdal-3.4.2 > ./configure > checking for internal_proj_create_from_wkt in -linternalproj... no > configure: error: PROJ 6 symbols not found > > [root@pi-dnac-158 proj-6.0.0]# ./configure --prefix /usr/local > > checking for pkg-config... /bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for SQLITE3... configure: error: Package requirements (sqlite3 >= > 3.7) were not met: > > No package 'sqlite3' found > https://gdal.org/download.html#build-requirements -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] zlib vulnerability CVE-2018-25032 affecting GAL
On Thu, 7 Apr 2022 at 15:08, Greg Troxel wrote: > Even Rouault writes: > I therefore think it would be good to consider removing the vendored > copies, or at least requiring explicit config to turn them on. +1 > I wonder if it's still really necessary/helpful to have included libs > like zlib. Good question that I have wondered myself about. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] zlib vulnerability CVE-2018-25032 affecting GAL
On Thu, 7 Apr 2022 at 13:54, Andrew C Aitchison wrote: > On Thu, 7 Apr 2022, Mateusz Loskot wrote: > > On Thu, 7 Apr 2022 at 12:29, prashanti seri > > wrote: > >> Does zlib vulnerability CVE-2018-25032 affect GDAL as it uses this lib? > > > > Hints: > > https://github.com/OSGeo/gdal/blob/master/frmts/zlib/zlib.h#L40 > > https://github.com/OSGeo/gdal/blob/patch/3.2.2.1/gdal/frmts/zlib/zlib.h#L40 > > https://github.com/OSGeo/gdal/blob/release/3.4/gdal/frmts/zlib/zlib.h#L40 > > [...] > so I don't see how zlib 1.2.3 protects gdal from this bug. The three hints were supposed to help OP find answer to her question above: "***Does ***zlib vulnerability ***affect*** GDAL?", that's it. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] zlib vulnerability CVE-2018-25032 affecting GAL
On Thu, 7 Apr 2022 at 12:29, prashanti seri wrote: > Does zlib vulnerability CVE-2018-25032 affect GDAL as it uses this lib? Hints: https://github.com/OSGeo/gdal/blob/master/frmts/zlib/zlib.h#L40 https://github.com/OSGeo/gdal/blob/patch/3.2.2.1/gdal/frmts/zlib/zlib.h#L40 https://github.com/OSGeo/gdal/blob/release/3.4/gdal/frmts/zlib/zlib.h#L40 Hint on solution: https://gdal.org/build_hints.html#zlib Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Errors during make - GDAL/Linux
On Tue, 5 Apr 2022 at 22:33, Ritu Vatsalya wrote: > I am trying to install GDAL 3.3.3 on Red Hat Enterprise Linux release 8.5. > > jpeg2000dataset.cpp:40:10: fatal error: jasper/jasper.h: No such file or > directory > > #include > > ^ > Please suggest. > https://github.com/OSGeo/gdal/issues/2402#issuecomment-613541129 By the way, at near the top of https://www.google.com/search?q=fatal+error%3A+jasper%2Fjasper.h%3A Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.4.2 RC2
+1 Mateusz On Thu, 10 Mar 2022 at 17:52, Howard Butler wrote: > > +1 > > Howard > > > On Mar 10, 2022, at 2:03 AM, Rahkonen Jukka (MML) > > wrote: > > > > +1 > > > > -Jukka Rahkonen- > > > > -Alkuperäinen viesti- > > Lähettäjä: gdal-dev Puolesta Even Rouault > > Lähetetty: torstai 10. maaliskuuta 2022 9.42 > > Vastaanottaja: gdal-dev@lists.osgeo.org > > Aihe: [gdal-dev] Motion: promote GDAL 3.4.2 RC2 > > > > Hi, > > > > Motion: > > > > Adopt GDAL 3.4.2 RC2 as final 3.4.2 release > > > > Starting with my +1 > > > > Even > > > > -- > > http://www.spatialys.com > > My software is free, but my time generally not. > > > > ___ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/gdal-dev > > ___ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/gdal-dev > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] VRT dataset to text in-memory?
On Thu, 3 Mar 2022 at 11:16, Michael Sumner wrote: > > Hello, reading the raster VRT tutorial > > https://gdal.org/drivers/raster/vrt.html#creation-of-vrt-datasets > > with this code: > > // > int nBand; > GDALDriver *poDriver = (GDALDriver *) GDALGetDriverByName( "VRT" ); > GDALDataset *poSrcDS, *poVRTDS; > poSrcDS = (GDALDataset *) GDALOpenShared( pszSourceFilename, GA_ReadOnly ); > poVRTDS = poDriver->CreateCopy( "", poSrcDS, FALSE, NULL, NULL, NULL ); > // > > Is there a way to obtained the VRT XML text representing poVRTDS without > writing to an actual file? Check what the https://gdal.org/programs/gdalbuildvrt.html does: https://github.com/OSGeo/gdal/blob/master/apps/gdalbuildvrt_bin.cpp#L192-L196 which is this call https://github.com/OSGeo/gdal/blob/master/apps/gdalbuildvrt_lib.cpp#L1691 which uses this builder class https://github.com/OSGeo/gdal/blob/master/apps/gdalbuildvrt_lib.cpp#L1769 which is/can be built as a library and linked against. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] [External] : Re: how to build netCDF driver plugin
On Fri, 25 Feb 2022, 07:01 Fengting Chen, wrote: > After fix the plugin library name, the netCDF driver plugin on linux is > working. However, it still didn’t work on windows: > > > > E:\tmp\gdal>gdalinfo > > ERROR 1: Can't load requested DLL: > E:\tmp\gdal\bin\gdalplugins\gdal_netCDF.dll > > 126: The specified module could not be found. > > > > ERROR 1: Can't load requested DLL: > E:\tmp\gdal\bin\gdalplugins\gdal_netCDF.dll > > 126: The specified module could not be found. > > > > I verified that specified gdal_netCDF.dll exists at above directory and > netcdf.dll is in the path of %PATH%. > > > > Any possible problem? > Lots. Use the process monitor (sysinternals, downloadable from Microsoft website) to investigate what DLLs are being loaded and from where, and which fail to be found. -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] [geos-devel] GEOS Maintenance Grant
+1 from GDAL PSC member Mateusz On Tue, 15 Feb 2022 at 19:11, Regina Obe wrote: > > GEOS PSC +1 > > > -Original Message- > > From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of > > Howard Butler > > Sent: Tuesday, February 15, 2022 10:38 AM > > To: gdal dev > > Cc: GEOS Development List > > Subject: [geos-devel] GEOS Maintenance Grant > > > > GDAL PSC, > > > > When we wrote the GDAL RFCs on sponsorship, we provided an escape > > clause to allow us to direct resources to other projects upon which GDAL > > depends. Our sponsorship numbers are still increasing, which provides us > an > > opportunity to directly support some of those projects, and one of them is > > obviously GEOS. GEOS provides all of the geometry algebra support for > > GDAL/OGR and many other open source geospatial softwares including > > Shapely, PostGIS, GeoPandas, MapServer, and more. > > > > Dan Baston of the GEOS PSC has been identified as the developer with > > capacity and interest in the next year to take on GEOS development on APIs > > and performance, which he has a long history of doing for the project. > This > > support should allow him to work longer, multi-release upgrades that will > > provide strong performance and convenience benefits for the project. > > > > I motion to provide the GEOS PSC with a $50,000 USD grant to address > > performance, API, and other work that does not attract directed funding in > > GEOS. The GEOS PSC will be responsible for coordinating work tasks, rates, > > and development timelines. Howard Butler or Even Rouault of the GDAL > > NumFocus liaison team will coordinate dispersement as directed by the > > GEOS PSC and NumFocus rules. > > > > Thank you again to the GDAL Sponsors https://gdal.org/sponsors/index.html > > who have made this kind of grant possible. A better GEOS makes for a > better > > GDAL. > > > > Howard > > > > ___ > > geos-devel mailing list > > geos-de...@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/geos-devel > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: grant github commit rights to Nyall Dawson
+1 Mateusz On Wed, 26 Jan 2022 at 00:34, Even Rouault wrote: > > Hi, > > I'd like to motion to grant github commit rights to Nyall. We don't have > much people currently doing reviews of pull requests and pressing the > "Merge" button, and Nyall is definitely in a capacity of fulfilling this > responsibility, at least in the areas where he fills comfortable. His > own pull requests are of excellent quality and he's one of the few to > review my work. > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 85: Policy regarding substantial code additions
+1 Mateusz On Fri, 21 Jan 2022 at 11:18, Even Rouault wrote: > > Hi, > > As the discussion seems to have calmed down, I move to adopt RFC 85: > Policy regarding substantial code additions: > https://github.com/OSGeo/gdal/pull/5128 > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Shortening schedule for CMake adoption ?
On Mon, 17 Jan 2022 at 14:37, Even Rouault wrote: > The new CMake build system > (https://gdal.org/development/rfc/rfc84_cmake.html) has made excellent > progress, and I believe that it should be in a production ready state on > time for GDAL 3.5.0 (~ May). Thanks for those efforts! > Consequently we could shorten the rather conservative schedule +1 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL windows build with sqlite3
On Wed, 15 Dec 2021, 21:55 Fengting Chen, wrote: > The sqlite3 I downloaded for windows only has source code and sqlite3.dll. > There is no sqlite3_i.lib. > How do I configure GDAL build to make it work with sqlite3.dll or how I can get/build sqlite3_i.lib for windows? Build SQLite yourself or dump def and lib, e.g. https://stackoverflow.com/a/56717285 ML ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL error: not found for legacy project
On Wed, 15 Dec 2021 at 14:15, Clive Swan wrote: > > I ran pip install C:/users/me/GDAL-3.4.0.tar.gz > > Now I get a Setup.py not found for legacy project error. > > WHAT?? RTFM did not help? https://gdal.org/api/python.html#windows -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] [ mailing list ]
On Tue, 30 Nov 2021 at 03:21, 박소원 wrote: > > Dear sir, > > Could you please take me off mailing list? Go to https://lists.osgeo.org/mailman/listinfo/gdal-dev Scroll to the bottom and follow the instructions starting with "To unsubscribe from gdal-dev,..." Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.4.0RC3 as final issue
+1 Mateusz On Thu, 4 Nov 2021 at 15:23, Rahkonen Jukka (MML) wrote: > > +1 > > -Jukka Rahkonen- > > -Alkuperäinen viesti- > Lähettäjä: gdal-dev Puolesta Even Rouault > Lähetetty: torstai 4. marraskuuta 2021 14.33 > Vastaanottaja: gdal-dev@lists.osgeo.org > Aihe: [gdal-dev] Motion: promote GDAL 3.4.0RC3 as final issue > > Hi, > > RC3 should be the last iteration needed to allow 3.4.0 to be released. > > Motion: > > Adopt GDAL 3.4.0 RC3 as final 3.4.0 release > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.3.3 RC1
+1 Mateusz On Wed, 27 Oct 2021 at 14:45, Howard Butler wrote: > > +1 > > Howard > > > On Oct 27, 2021, at 6:44 AM, Rahkonen Jukka (MML) > > wrote: > > > > +1 > > > > -Jukka Rahkonen- > > > > -Alkuperäinen viesti- > > Lähettäjä: gdal-dev Puolesta Even Rouault > > Lähetetty: keskiviikko 27. lokakuuta 2021 14.43 > > Vastaanottaja: gdal-dev@lists.osgeo.org > > Aihe: [gdal-dev] Motion: promote GDAL 3.3.3 RC1 > > > > Hi, > > > > Having heard no issues being reported regarding RC1 > > > > Motion: > > > > Adopt GDAL 3.3.3 RC1 as final 3.3.3 release > > > > Starting with my +1 > > > > Even > > > > -- > > http://www.spatialys.com > > My software is free, but my time generally not. > > > > ___ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/gdal-dev > > ___ > > gdal-dev mailing list > > gdal-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: RFC 84: Migrating build systems to CMake
+1 Mateusz Great stuff! It's been a dream for long to pull the CMake for GDAL off. On Mon, 11 Oct 2021 at 16:14, Howard Butler wrote: > > All, > > Discussion on this topic has died down, and it appears there are no major > objections, so I would like to put forward a motion to approve RFC 84. With a > conservative timeline, the final outcome of this effort is GDAL will be > CMake-only in May 2023. > > You can view the proposal at > https://github.com/OSGeo/gdal/blob/1d3c283d40f4d2145c11dfca4b537fb357f53600/gdal/doc/source/development/rfc/rfc84_cmake.rst > > +1 Howard > > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Approve Nyall Dawson as a contracted GDAL maintainer
+1 Mateusz On Tue, 14 Sept 2021 at 16:59, Howard Butler wrote: > > Dear PSC, > > As a result of our fundraising activity and development of NumFOCUS as a > financial conduit, it is my pleasure to put forward a motion to approve Nyall > Dawson as a contracted GDAL maintainer for the year 2021-2022 beginning on > October 1st, 2021 and ending September 30th, 2022. > > Details of the maintenance tasking and duties can be found at the previously > approved RFC 83 > https://gdal.org/development/rfc/rfc83_use_of_project_sponsorship.html > > The terms of the contract are for a maximum of 500 hours at 90 €/hr. > > Howard > > PS I will coordinating the contracting activity in my role as the GDAL > NumFOCUS contracting liaison, with Frank Warmerdam acting as the secondary. > Please contact us directly with any comments or concerns. > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: Approve Even Rouault as a contracted GDAL maintainer
+1 Mateusz On Tue, 17 Aug 2021, 17:33 Howard Butler, wrote: > Dear PSC, > > As a result of our fundraising activity and development of NumFOCUS as a > financial conduit, it is my pleasure to put forward a motion to approve > Even Rouault as a contracted GDAL maintainer for the year 2021-2022 > beginning on August 1st, 2021 and ending July 31st, 2022. > > Details of the maintenance tasking and duties can be found at the > previously approved RFC 83 > https://gdal.org/development/rfc/rfc83_use_of_project_sponsorship.html > > The terms of the contract are for 833 hours at $120/hr USD. > > Howard > > PS I will coordinating the contracting activity in my role as the GDAL > NumFOCUS contracting liaison, with Frank Warmerdam acting as the secondary. > Please contact us directly with any comments or concerns. > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] clang-tidy configs for gdal ?
On Thu, 10 Jun 2021 at 22:11, Kurt Schwehr wrote: > > My recommendation with clang-tidy is to start with all warnings disabled. Indeed, work with checks one by one, e.g. like here https://github.com/libgeos/geos/commit/b7101be6533a1273f715a3309889c23b7ae02e4f https://github.com/libgeos/geos/commit/6f0c2bac087180369760e9fed244bb797582a3b2 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC 83: guidelines for the use of GDAL project sponsorship
+1 Mateusz On Tue, 8 Jun 2021 at 12:50, Even Rouault wrote: > > Hi, > > Motion: > > adopt RFC 83: guidelines for the use of GDAL project sponsorship ( > https://github.com/OSGeo/gdal/pull/3855 ) > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Freenode IRC taken over(was Fwd: [SAC] [Hosting] OSUOSL IRC channels moving to irc.libera.chat)
On Thu, 20 May 2021 at 20:07, Richard Duivenvoorde wrote: > > But... the cool thing is[...] you can have different matrix identities. Although I'm aware, my personal preference is to avoid that feature and chain myself to the matrix.org. ...one's habits one's worst enemy Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Freenode IRC taken over(was Fwd: [SAC] [Hosting] OSUOSL IRC channels moving to irc.libera.chat)
On Thu, 20 May 2021 at 11:09, Sandro Santilli wrote: > On Wed, May 19, 2021 at 09:00:52PM +0200, Even Rouault wrote: > > > > > > - something else ? > > In case you missed it, OSGeo is now hosting a Matrix homeserver: > https://wiki.osgeo.org/wiki/SAC:MatrixSynapse > > Matrix is an open protocol for instant messaging based on HTTP, > supports bridges to different IM systems (including IRC and Slack). Those of us who used to use Matrix, stopped using it, perhaps deactivated their accounts, then want to use it again, perhaps with the same username, then don't bang your head at the desk in frustration when the "computer says no!" Here is response I have received from the Matrix support team after learning to get in touch with them about the issue [1] """ Hi Mateusz Unfortunately it is impossible to verify the identity of deleted users. Per the matrix.org Privacy Notice ( https://matrix.org/legal/privacy-notice#2211-account-and-profile-information ): "Your username is stored indefinitely to avoid account recycling." To protect the security and privacy of our users we never reactivate or release deleted usernames. We recommend you create a new account using a different Matrix ID. Matrix.org Support """ [1] https://github.com/matrix-org/synapse/pull/7908#issuecomment-708338470 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ 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 83: guidelines for the use of GDAL project sponsorship
On Wed, 19 May 2021 at 14:46, Even Rouault wrote: > [...] Input welcome. > https://github.com/OSGeo/gdal/pull/3855 I left some as the PR comments. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Build GDAL on windows with dependency on PROJ
On Fri, 14 May 2021, 00:42 Fengting Chen, wrote: > However, I couldn’t find the PROJ source code with makefile for Windows. I > am wondering how is PROJ built on Windows in order to build GDAL 3.3 on > Windows? > RTM https://proj.org/install.html#cmake There is proj mailing list. ML ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC80
+1 Mateusz On Fri, 16 Apr 2021 at 16:50, Even Rouault wrote: > > Hi, > > I hereby motion to adopt RFC 80: > > https://github.com/OSGeo/gdal/pull/3682 > > This also implies adopting the "GDAL Sponsorship Prospectus" at > > https://docs.google.com/document/d/1yhMWeI_LgEXPUkngqOitqcKfp7ov6WsS41v5ulz-kd0/edit?ts=60777468# > whose a PDF version will be uploaded on the website > (https://github.com/OSGeo/gdal/pull/3681 to be updated) > > and the proposed answers to the NumFOCUS application form are at: > https://docs.google.com/document/d/1bc5jdpCe1axdyBHxbJnun7e0DTyDoZI_eFYgJYnOhB8/edit > > which will be submitted consequently. > > Starting with my +1 > > Even > > > -- > http://www.spatialys.com > My software is free, but my time generally not. > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] Fwd: [IIIF-Discuss] IIIF Maps Community Call on Wednesday March 24
FYI, GDAL is on the agenda ML -- Forwarded message - From: Eliot Jordan Date: Tue, 23 Mar 2021 at 20:42 Subject: [IIIF-Discuss] IIIF Maps Community Call on Wednesday March 24 To: IIIF Discuss Map Enthusiasts - We have a maps community call scheduled for Wednesday March 24 at 8:00 AM PDT, 11:00 AM EDT, 15:00 UK, 16:00 CET. Zoom Link: https://stanford.zoom.us/j/99449304468?pwd=UUNzMmFtV2dXSWs2MjVicnplS29LUT09 Agenda: https://docs.google.com/document/d/1Rfl7ufHFJtLUgLdaZUjX8CPEsmy0fPW3MWY_GPDRHl4 If you have anything you’d like to talk about or any related work you’ve done recently please add to the agenda! See you there. - Eliot __ Eliot Jordan Geospatial Infrastructure Developer Princeton University Library ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Is it possible to switch warnings off?
On Sun, 7 Mar 2021 at 21:42, Joaquim Manuel Freire Luís wrote: > > I have this strange case where some warnings come from don’t know where. > [...] > Warning 1: The dataset has several variables that could be identified as > vector fields, but not all share the same primary dimension. Consequently > they will be ignored. https://github.com/OSGeo/gdal/blob/fa752ad6eabafaf630a704e1892a9d837d683cb3/gdal/frmts/netcdf/netcdfdataset.cpp#L11567-L11570 > Is there anyway to shut up this warnings, or warnings in general? https://gdal.org/api/cpl.html?highlight=cplerror#_CPPv48CPLError6CPLErr11CPLErrorNumPKcz "The effect of this function can be altered by applications by installing a custom error handling using CPLSetErrorHandler()." Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: adopt RFC79: Listing of Service Providers on GDAL website
+1 Mateusz On Thu, 25 Feb 2021 at 11:30, Even Rouault wrote: > > Hi, > > I motion to adopt RFC79: Listing of Service Providers on GDAL website: > https://github.com/OSGeo/gdal/pull/3473 > > Starting with my +1 > > Even > > -- > http://www.spatialys.com > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] The proper way to call gdal "scripts" on Windows?
On Thu, 25 Feb 2021 at 09:34, Idan Miara wrote: > > Is there an easier way but to call "python c:\Python38\Scripts\gdal_calc.py", > for instance? https://docs.python.org/3/using/windows.html#finding-the-python-executable "On the first page of the installer, an option labelled “Add Python to PATH” may be selected to have the installer add the install location into the PATH. The location of the Scripts\ folder is also added." Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Finding the Map-Tiles(x, y) in a given Bounding box and zoom level
On Wed, 24 Feb 2021 at 21:01, MRRAJESH wrote: > > 1. Any C# nuget packages available for mercantile? Search. > 2. Any GDAL methods to achieve the functionality (i.e., get the tile numbers > for a given BBOX and level)? No. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Pushing OGRLineString * var to a vector problematic ??
On Sat, 13 Feb 2021 at 08:11, Ahmet Temiz wrote:
>
> I want to get your view
> Is putting OGRLineString * var to a vector and then a setter a good idea?
>
> ... // same as tutorial
> if( poGeometry != NULL && wkbFlatten(poGeometry->getGeometryType()) ==
> wkbLineString )
> {
> OGRLineString *poLine = (OGRLineString *) poGeometry;
> v_faultLine.push_back(poLine); /// std::vector < OGRLineString
> * > v_faultLine;
IN the same https://gdal.org/tutorials/vector_api_tut.html you can read
"Note that OGRFeature::GetGeometryRef() [...] return a pointer
to the internal geometry owned by the OGRFeature"
That should explain the v_faultLine is collection of observers and not owners.
If you use it as such, i.e. without trying to take over the
ownership/deallocate,
you should be safe.
> . ...
> }
>
>this->setFaultLine (v_faultLine);
It is not possible to say that it is "a good idea" without
knowing what the setFaultLine expects and does.
If it expects it will take over ownership of elements in v_faultLine,
then watch the holes in your knees.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Geometry validation
On Tue, 9 Feb 2021 at 08:02, Илья Нецветаев wrote: > 1. What does exactly "valid geometry" mean? You will find it in the OGC SFS specification > What does IsValid check? Read https://postgis.net/docs/ST_IsValid.html and https://postgis.net/docs/postgis_usage.html#OGC_Validity Read the GEOS library source code to learn the details. Ask https://lists.osgeo.org/mailman/listinfo/geos-devel > As it is written in docs: Returns true if geometry has no points". I'm not > sure, that I understand it correctly. Empty geometry is a valid geometry. See OGC SFS. > 2. Is there a proper way to replace MakeValid with something in order to keep > my app functional? Read the GEOS library source code to learn the details. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Alpine Docker build with ODBC support
On Tue, 9 Feb 2021 at 07:31, andrew.murdoch@gmail.com wrote: > > I just want to be sure that I'm on the right track to getting ODBC support > into a GDAL docker alpine build. > [...] > I've added a reference to "unixodbc-dev", but this does not seem to be a > supported/expected ODBC library for GDAL? I know nothing about Alpine packages, but perhaps you need to install the unixODBC binary package explicitly (i.e. it's not dragged in by unixodbc-dev). Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Converting KML data with styles to GeoJSON output
On Tue, 9 Feb 2021 at 08:05, MRRAJESH wrote: > > I am trying to convert a kml-file with styles to a GeoJSON. Observed that > only data is converted but styles information is missing. How to get the > Geojson data along with styles? Does GeoJSON support styles? 1. https://tools.ietf.org/html/rfc7946 2. https://gdal.org/drivers/vector/geojson.html?highlight=style Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] gdalbuildvrt files not recognized
On Thu, 4 Feb 2021 at 23:22, Simon Shak wrote: > > However, your suggestion to check the filelist.txt file has found the error. > Somehow a trailing space was before the CRLF and caused it to not recognize > the file. There also could be an issue if there are spaces in file names. I don't know if gdalbuildvrt can handle those on all platforms. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] gdalbuildvrt files not recognized
On Thu, 4 Feb 2021, 23:02 Simon Shak, wrote: > > If I do it straight via commandline as: > for %f in (input\*.ecw) do (gdalbuildvrt output.vrt %f) > I wind up with a VRT with only one of the several hundred files in it. > Yes, that's expected, isn't it. if I try it using a file list by first: > for %f in (input\*.ecw) do (echo %f >> filelist.txt) > then: > gdalbuildvrt -input_file_list filelist.txt output.vrt > I assume you've read the docs, why don't you feed it with input/*.ecw directly. I get a bunch of errors saying: > ERROR 4: `ecw\N39.250W119.500N39.375W119.375.ecw ' not recognized as a > supported file format. > I'd verify content of the file is single file name per line. It may matter the EOL is LF, not CRLF, can't remember. ML ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.2.1 RC1
+1 Mateusz Loskot, mate...@loskot.net (Sent from mobile, may suffer from top-posting) On Thu, 31 Dec 2020, 09:58 Even Rouault, wrote: > Hi, > > Having heard no issues being reported regarding RC1 > > Motion: > > Adopt GDAL 3.2.1 RC1 as final 3.2.1 release > > Starting with my +1 > > Even > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2
On Tue, 22 Dec 2020 at 12:47, Bugbuster wrote: > > You may be right about the update of VS2015. > My version is 19.00.23026 (to be compared to yours : 19.00.23506) > > An I do have the error with the small test you sent. > > Do you have any idea declare/initialize the NaN attribute in another way ? https://duckduckgo.com/?q=static+const+double+member+c%2B%2B03 e.g. https://stackoverflow.com/a/50764180/151641 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2
On Tue, 22 Dec 2020 at 11:11, Bugbuster wrote: > > When compiling GDAL 3.2, I get an error in gcore/tilematrixset.hpp > tilematrixset.hpp(47): error C2131: expression did not evaluate to a > constant > failure was caused by non-constant arguments or reference to a non-constant > symbol > note: see usage of 'std::numeric_limits::quiet_NaN()' VS 2015 should swallow that fine https://rextester.com/LQPF72765 but, AFAIR, you need the latest update of the VS 2015 in order to get more complete C++11 support. Best regards. -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] How to wrap a C++ library using GDAL in a Python library?
On Wed, 9 Dec 2020 at 17:19, Sean Gillies via gdal-dev wrote: > > Hi Mateusz, > > The OSGeo sysadmins found something to correct in mailman configuration, I'm > giving that a test here. Sean, >From my perspective, that 'something' does the job and despams your message. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] How to wrap a C++ library using GDAL in a Python library?
On Tue, 8 Dec 2020 at 23:16, Sean Gillies wrote: > > The state of the art for very thin Python bindings for a C++ project seems to > be pybind11. It's used for numpy's FFT module, based on pocketfft. My observations are similar to that and pybind11 is the currently popular solution. I personally like to stick to vanilla Python API though, not easy, but not a terrible experience either. > If some of you are surprised to see me post again on this thread, it's > because my s...@mapbox.com address is getting marked as spam. FYI, your messages from that address always landed in my GMaill inbox marked as spam. That actually is the case for every message from @mapbox.com (e.g. from OSRM folks). Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Adopting Contributor Covenant v2.0 as code of conduct
On Wed, 25 Nov 2020 at 15:13, Even Rouault wrote: > > Honestly I don't really care about which CoC we select. We just need (a > somewhat reasonable) one, and above all, not create a new one. Yes, let's use the OSGeo's. Although it's a pity that we, as a civilisation, need a written CoC at all. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Adopting Contributor Covenant v2.0 as code of conduct
On Wed, 25 Nov 2020, 14:53 Greg Troxel, wrote:
>
> > As required by OSGeo for its projects [1] and some institutions that
> want to
> > interact with us, I've prepared in
> https://github.com/OSGeo/gdal/pull/3219 a
> > pull request adding the Contributor Covenant v2.0 [2] as the code of
> conduct
> > for the project.
>
> I much prefer the OSGeo COC to the one you have proposed instead. In
> particular ("Diversity Statement") talks about being welcoming to all
> rather than having a large but finite list of non-discrimination reasons
>
+1
which notably leaves out political views and being a veteran. While I
> strongly support being courteous to everyone, these codes can veer into
> a political statement particularly when they include and exclude
> particular groups by having a list.
+1
I feel that OSGeo's avoids that,
> and the Contributor Covenant not as well.
>
+1
For now, I'm opposed, and prefer to just add a line in README.md
>
> See [the standard OSGeo Code of Conduct](
> https://www.osgeo.org/resources/osgeo-code-of-conduct/).
>
+1
--
Mateusz Loskot, mate...@loskot.net
(Sent from mobile, may suffer from top-posting)
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL t-shirts!
On Wed, 11 Nov 2020, 17:19 Howard Butler, wrote: > All, > > Joe Morrison [1] coordinated the creation of new GDAL t-shirts with a fun > update to the logo. Proceeds of the sales will be donated to OSGeo. Visit > https://teespring.com/gdal to get yourself one. > > Howard > > [1] https://twitter.com/mouthofmorrison/status/1326556800997527557?s=20 > Awesome! I really like the back side, brilliant idea. Kudos! Mateusz Loskot, mate...@loskot.net (Sent from mobile, may suffer from top-posting) ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.2.0 RC1
+1 Mateusz On Thu, 29 Oct 2020 at 09:55, Even Rouault wrote: > > Motion: > Adopt GDAL 3.2.0 RC1 as final 3.2.0 release > > Starting with my +1 -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] How to build GDAL 3.1.3 with sqlite3 3.33.0
On Tue, 20 Oct 2020 at 04:34, Doug Niven wrote: > > I’m having trouble building GDAL 3.1.3 with sqlite3 3.33.0 in Centos 7. > > The compile steps work, but the build does not. > I believe this is because of conflicts between the built-in version of > sqlite3 in Centos (3.7.17) and the newer one (3.33.0) I’ve built in > /usr/local/ and /usr/local/lib > /usr/local/lib, where the sqlite3 library files are, is in my LD_LIBRARY_PATH > /usr/local/bin, where sqlite3 is, is also in my PATH > > I’m curious how others have successfully managed to build GDAL with the above > in mind. As usual: ./configure --help ./configure --help | grep -i sqlite So, you should be able to ./configure --with-sqlite3=/usr/local as per https://github.com/OSGeo/gdal/blob/master/gdal/m4/ax_lib_sqlite3.m4#L36-L37 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Clang-format
On Sat, 10 Oct 2020 at 23:39, Even Rouault wrote: > > > However, I found it strange that there is no automatic formatting with > > clang-format for C++ code. > > > > In this page > > https://gdal.org/development/rfc/rfc69_cplusplus_formatting.html it is > > suggesting to use it. That would be great! Enabling it in your favourite > > editor makes the code nicer, without any extra work. And more consistent! > > > About "when" to apply it (reformatting *all* the existing code), I think a > > good moment could be just before creating a "big" release branch, like 3.2. > > Then the backport of bug fixes would be easy (otherwise it is a nightmare). > > > > What do you think? > > > Was discussed at that time in > https://lists.osgeo.org/pipermail/gdal-dev/2017-May/thread.html#46560 > > I would be quite in favor of the principle > > A few points I've in mind: > > - I'm slightly worried about clang-format output changing between versions of > the tool (based on my experience with PROJ, I can tell you that they are > different between 3.8, which is the one we used for PROJ, and 10), which > would be an issue as we cannot be certain that our set of contributors to > have different versions. Not sure if having a custom .clang-format file > (possibly a 'standard' one that we put in our tree to make output stable) > would help ? This would have to be investigated & tested. I think, it would require us to stick to a particular clang-format version that is allowed to (re)format GDAL. Contributors who want to use clang-format would have to use the decided version only. I suspect, higher versions of clang-format systematically suffer from less and less behaviour discrepancies, so it may be sensible to pick one of the later versions, instead of 3.8. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDALDatasetDriver->poDriver = NULL
On Thu, 8 Oct 2020 at 17:17, Momtchil Momtchev wrote:
>
> Is it normal that for this code
>
> int main() {
> GDALAllRegister();
> const char *pszFormat = "GTiff";
> GDALDriver *driver = GetGDALDriverManager()->GetDriverByName(pszFormat);
> if (driver == nullptr) {
> printf("driver is null\n");
> return 1;
> }
> std::string path = "sample.tif";
> GDALAccess access = GA_ReadOnly;
> GDALOpenInfo *open_info = new GDALOpenInfo(path.c_str(), access);
> GDALDataset *ds = driver->pfnOpen(open_info);
> printf("%p\n", ds->GetDriver());
> printf("%s\n", ds->GetDriver()->GetDescription());
> }
>
> I get ds->GetDriver = NULL (and a segfault on the following line)? Tried on
> 3.1.2 and 3.1.0
Try to open a dataset as presented here
https://gdal.org/tutorials/raster_api_tut.html
Best regards.
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] OGR C++ API to load Esri JSON
On Wed, 23 Sep 2020 at 14:48, Michal Schneider wrote: > > I see OGR_G_CreateGeometryFromJson in ogr_api.h, > but can't see OGR_G_CreateGeometryFromEsriJson there... https://gdal.org/api/vector_c_api.html#_CPPv432OGR_G_CreateGeometryFromEsriJsonPKc IOW, in first 10 links from the search result set of https://gdal.org/search.html?q=ESRI Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Compiling GDAL with Visual Studio 2019
On Wed, 9 Sep 2020 at 16:58, Alexis Vaisse wrote: > > I get the help content, but also the strange message "The system cannot > find the path specified" again. It's a typical error issued by cmd.exe when it can not find program/command requested to run. > cd port >nmake /nologo /f makefile.vc >call prev_dllbuild.bat > The system cannot find the path specified. This must be related to this bit https://github.com/OSGeo/gdal/blob/release/3.1/gdal/port/makefile.vc#L136-L142 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Compiling GDAL with Visual Studio 2019
On Tue, 8 Sep 2020 at 14:50, Alexis Vaisse wrote:
>
> D:\Terrain\Extern\gdal-3.1.3>nmake -f makefile.vc MSVC_VER=1927 WIN64=1
>
> Microsoft (R) Program Maintenance Utility Version 14.27.29110.0
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> cd port
> nmake /nologo /f makefile.vc
> call prev_dllbuild.bat
> The system cannot find the path specified.
>
> D:\Terrain\Extern\gdal-3.1.3\port>IF NOT EXIST dllbuild.prev (ECHO 1 )
> 1>dllbuild.prev
>
> D:\Terrain\Extern\gdal-3.1.3\port>SET /P PREV_DLLBUILD= 0
> D:\Terrain\Extern\gdal-3.1.3\port>IF NOT "1" == "1" (ECHO 1 ) 1>dllbuild.prev
> NMAKE : fatal error U1077: 'call' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64\nmake.EXE"' :
> return code '0x2'
> Stop.
I downloaded latest
https://github.com/OSGeo/gdal/releases/download/v3.1.3/gdal-3.1.3.tar.gz,
unpacked, and tried to build:
```
D:\tmp\gdal\gdal-3.1.3>nmake -f makefile.vc MSVC_VER=1927 WIN64=1
EXT_NMAKE_OPT=D:\tmp\gdal\gdal-3.1.3\nmake.opt.local
Microsoft (R) Program Maintenance Utility Version 14.27.29111.0
Copyright (C) Microsoft Corporation. All rights reserved.
cd port
nmake /nologo /f makefile.vc
call prev_dllbuild.bat
D:\tmp\gdal\gdal-3.1.3\port>IF NOT EXIST dllbuild.prev (ECHO 1 ) 1>dllbuild.prev
D:\tmp\gdal\gdal-3.1.3\port>SET /P PREV_DLLBUILD= 0IF NOT "1" == "1" (ECHO 1 ) 1>dllbuild.prev
type cpl_config.h.vc.begin > cpl_config.h
type cpl_config.h.vc.common >> cpl_config.h
IF NOT "1"=="1" type cpl_config.h.vc.no_dll >> cpl_config.h
type cpl_config.h.vc.end >> cpl_config.h
cl /nologo .
```
As you can see, I can not reproduce your problem.
I can also build just inside the port subdirectory without any problems:
```
D:\tmp\gdal\gdal-3.1.3> cd port
D:\tmp\gdal\gdal-3.1.3\port>nmake -f makefile.vc MSVC_VER=1927 WIN64=1
EXT_NMAKE_OPT=D:\tmp\gdal\gdal-3.1.3\nmake.opt.local clean
Microsoft (R) Program Maintenance Utility Version 14.27.29111.0
Copyright (C) Microsoft Corporation. All rights reserved.
del *.obj *.lib cpl_config.h dllbuild.prev
D:\tmp\gdal\gdal-3.1.3\port>nmake -f makefile.vc MSVC_VER=1927 WIN64=1
EXT_NMAKE_OPT=D:\tmp\gdal\gdal-3.1.3\nmake.opt.local
Microsoft (R) Program Maintenance Utility Version 14.27.29111.0
Copyright (C) Microsoft Corporation. All rights reserved.
call prev_dllbuild.bat
D:\tmp\gdal\gdal-3.1.3\port>IF NOT EXIST dllbuild.prev (ECHO 1 ) 1>dllbuild.prev
D:\tmp\gdal\gdal-3.1.3\port>SET /P PREV_DLLBUILD= 0IF NOT "1" == "1" (ECHO 1 ) 1>dllbuild.prev
type cpl_config.h.vc.begin > cpl_config.h
type cpl_config.h.vc.common >> cpl_config.h
IF NOT "1"=="1" type cpl_config.h.vc.no_dll >> cpl_config.h
type cpl_config.h.vc.end >> cpl_config.h
cl /nologo .
```
I tried all the commands inside "x64 Native Tools Command Prompt for VS 2019",
from the VS 2019 16.7.2
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Compiling GDAL with Visual Studio 2019
On Tue, 8 Sep 2020 at 11:26, Alexis Vaisse wrote: > I’m trying to compile GDAL with Visual Studio 2019. > The batch file to generate the project runs with no error. But when I try > to compile the project, I get so many different errors I guess I did > something wrong, but I don’t know what. > > Did somebody already succeed in compiling GDAL for Visual Studio 2019? Yes, many times. First, you don't have to generate .vcxproj files with the .bat script to build GDAL. Just run `nmake.exe` command in the VS Command Prompt. However, before you attempt to build GDAL, you need to: - Read https://trac.osgeo.org/gdal/wiki/BuildingOnWindows - Check also https://trac.osgeo.org/gdal/wiki/BuildHints for specific needs/dependencies/drivers - Collect dependencies you require - Edit nmake.opt to disable/enable features/drivers you don't need/need, you have third-party dependencies for, etc. - Run NMAKE GDAL is not a self-contained project. GDAL has numerous dependencies that you need to provide/install, On Windows, manual editing of nmake.opt to configure your build is necessary. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.1.3 RC1
On Thu, 3 Sep 2020 at 10:45, Even Rouault wrote: > > Having heard no issues with RC1, > > Motion: > Adopt GDAL 3.1.3 RC1 as final 3.1.3 release > > +1 Even +1 -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Linking error when building Informix OGR driver
On Tue, 25 Aug 2020 at 14:16, Jeremy Palmer wrote: > > Thanks Mateusz. > > I still get linking errors with that patch applied. > However, the SDK libraries are now in the linking tool arguments: ¯\_(ツ)_/¯ Try to completely clean and re-build, perhaps Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Linking error when building Informix OGR driver
On Tue, 25 Aug 2020 at 12:58, Jeremy Palmer wrote: > > Then I run make which is ok until linking of app tools: > > /bin/bash /home/informix/dev/gdal/gdal/libtool --mode=link --silent g++ > gdalinfo_bin.lo /home/informix/dev/gdal/gdal/libgdal.la -o gdalinfo > /opt/IBM/Informix_Client-SDK/lib/c++/libifc++.so: undefined reference to > `mi_cleanup' > ... heaps of informix function references > /opt/IBM/Informix_Client-SDK/lib/c++/libifc++.so: undefined reference to > `_ifx_gl_mbsrchr' > collect2: error: ld returned 1 exit status > GNUmakefile:90: recipe for target 'gdalinfo' failed > make[1]: *** [gdalinfo] Error 1 > make[1]: Leaving directory '/home/informix/dev/gdal/gdal/apps' > GNUmakefile:120: recipe for target 'apps-target' failed > make: *** [apps-target] Error 2 See this thread, and try the GitHub link at the bottom https://lists.osgeo.org/pipermail/gdal-dev/2017-September/047275.html Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] gdal 3.1.2 installation in RHEL 7 , stuck with dependency installation. kindly help
On Thu, 13 Aug 2020 at 14:08, Kavitha K wrote: > checking for SQLITE3... configure: error: Package requirements (sqlite3 >= > 3.11) were not met: > > No package 'sqlite3' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables SQLITE3_CFLAGS > and SQLITE3_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > [...] > [root@pi-22 sqlite-tools-linux-x86-3320300]# cd /usr/local/bin > [root@pi-22 bin]# ls |grep sql > sqldiff > sqlite3 > sqlite3_analyzer You need SQLite development package, with header(s) and library, not just SQLite executable program(s). Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] https://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries not updated for gdal 3.1.2 for RHEL install
On Thu, 13 Aug 2020 at 14:00, Kavitha K wrote: > > But the ELGIS link is missing with latest version under this description. > > One added suggestion: If there is dependency for the latest gdal version, > kindly include those dependency download location and detailed installation > procedure in RHEL. GDAL maintainers do not maintain (or are responsible for) binary packages of GDAL. Direct your questions/suggestions to https://lists.osgeo.org/mailman/listinfo/el Check this too https://wiki.osgeo.org/wiki/Enterprise_Linux_GIS Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] MSSQLSpatial not using BCP to load
On Tue, 30 Jun 2020, 15:27 Hector muro, wrote: > Hi Mateusz > > Thanks a lot for that. I can see that in my gdal copy it is commented out. > But I also see all these paths refer to a Windows installation. Does this > mean the BCP support is only available for a Windows installation? > ¯\_(ツ)_/¯ It definitely is a feature toggled at compile--time Mateusz Loskot, mate...@loskot.net (Sent from mobile, may suffer from top-posting) ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] MSSQLSpatial not using BCP to load
On Mon, 29 Jun 2020 at 15:53, Hector muro wrote:
>
> As a part of a project I need to load quite big geojsons into SQL Server and
> I am using ogr2ogr to do so.
>
> Here is an example command I am using:
>
> ogr2ogr -f MSSQLSpatial
> "MSSQL:server=xxx;database=xxx;UID=xxx;PWD=xxx;DRIVER={ODBC Driver 17 for SQL
> Server}" -append --config SPATIAL_INDEX NO --config MSSQLSPATIAL_USE_BCP TRUE
> --config MSSQLSPATIAL_BCP_SIZE 1 --config
> MSSQLSPATIAL_USE_GEOMETRY_COLUMNS NO -nln INM.nv_lv_ohline -nlt GEOMETRY
> -t_srs EPSG:27700 -s_srs EPSG:4326 -skipfailures -splitlistfields
> $DATA/data.json
>
> I found that it is very slow and I have been checking the SQL Server profiler
> (as suggested already in this thread:
> https://lists.osgeo.org/pipermail/gdal-dev/2018-May/048520.html) and I can
> confirm that it is trying to insert every record one-by-one, hence the
> slowness.
>
> What I can't get to understand is how to point gdal to my sql server
> installation.
>
> SQL Server version: 2016
> GDAL: 3.0.4
Double check your GDAL is built with MSSQL_BCP_SUPPORTED=1 macro defined
https://github.com/OSGeo/gdal/blob/7ce18dfea8c2c6c2d73d5824cf1c91f6e0287a75/gdal/nmake.opt#L288-L298
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.1.1 RC1
On Thu, 25 Jun 2020 at 12:18, Even Rouault wrote: > > Motion: > Adopt GDAL 3.1.1 RC1 as final 3.1.1 release > > +1 Even +1 Mateusz -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Reading a double from file
On Tue, 16 Jun 2020 at 10:08, Andrew C Aitchison wrote: > > Does gdal have a standard, endian-independent, > way to read floating point values from file ? > Specifically IEEE-754 little-endian 64bit values. > > So far my driver has used a union to "cast" 8 bytes to a double, > but I now discover that, whilst this is valid C, it is not valid C++. > I am looking for a portable way to read such values from file > into a C++ double. This cannot be the first gdal driver to need to do this. Generally, use std::memcpy or std::copy. Detect if you need to swap bytes and swap bytes. Specifically, among others: https://github.com/OSGeo/gdal/blob/master/gdal/frmts/blx/blx.c#L486-L502 BTW, for reading float-point values from text, CPLAtof, CPLScanString, etc: https://github.com/OSGeo/gdal/blob/master/gdal/port/cpl_conv.h#L83-L119 -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC3
+1 Mateusz On Tue, 5 May 2020 at 15:43, Howard Butler wrote: > > > > On May 5, 2020, at 4:39 AM, Even Rouault wrote: > > Hi, > > > > Motion: promote GDAL 3.1.0 RC3 to final 3.1.0 > > > > Starting with my +1 > > > +1 Howard > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2
On Thu, 30 Apr 2020 at 11:34, Even Rouault wrote: > > Having adressed the few issues raised about RC1, I believe RC2 is good to go. > Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 > Starting with my +1 > Even +1 Mateusz ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Windows CI build times
On Fri, 17 Apr 2020 at 01:45, Mike Taves wrote: > > It seems that many projects have shifted from AppVeyor to AZP for > performance benefits. Or GitHub Actions, which is an incarnation of AzP. > As you mentioned, some of the dependencies could be built and cached, > rather than using vcpkg. caching can work for the vcpkg installs on AppVeyor easily https://github.com/boostorg/gil/blob/develop/.appveyor.yml#L75-L76 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Building on windows
On Sun, 15 Mar 2020 at 13:08, Darrel Maddy wrote: > > I have recently switched back to windows for a specific project that uses the > gdal library. I am getting the following error on compilation of the VS > project > > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio\2019\Enterprise\VC\Tools\MSVC\14.22.27905\bin\HostX86\x64\cl.EXE"' : > return code '0x2' > > The cl.exe file is present in the directory (there are a number of similar > messages that follow) and I am unsure how to proceed. Any suggestions? That is just a tiny bit of detailed error that does not tell much. Possibly, your nmake.opt is configured to link some GDAL dependencies which you are actually missing, then NMAKE will fail if cl/link fail. Besides, you don't tell anything about - what version of GDAL you build - what commands you run to build - you say you compile of the VS project, but what is "the" project, is it one generated with generate_vcxproj.bat? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] How do I install GDAL on Windows 10?
On 25 February 2020 06:59:15 CET, /dev /local/ca wrote: >I want to install and use GDAL on Windows 10. > >I don't know what 'conda' is, I don't care what it is, and I don't want >to >install it and screw up my machine. You've chosen the operating system wrongly as apparently it does not fit your attitude. Luckily, you've got the WSL on Windows 10. Use it and chances are you'll stop complaining across the Web... -- Mateusz Loskot, mate...@loskot.net (Sent from K-9 on mobile, may suffer from top-posting) ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Help with CPL_DEBUG
On Mon, 17 Feb 2020 at 18:34, Joaquim Manuel Freire Luís wrote: > On Mon, 17 Feb 2020 at 18:05, Joaquim Manuel Freire Luís > wrote: > >> > >> Hi Even, > > > FYI, you have e-mailed the public gdal-dev mailing list. > > Yes, I know but since Even responds all the times ... I took the liberty I hope such liberty doesn't spread too widely, unless accepted ...and followed by stream of invoices to Even. > I also read that page, and used "CPL_DEBUG=ON" in my command, > but no message was printed hence my suspicion that I might not be using it > correctly. I believe there may be/is difference between --config CPL_DEBUG ON vs --config CPL_DEBUG=ON The Wiki page does not mention the latter, does it? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Help with CPL_DEBUG
On Mon, 17 Feb 2020 at 18:05, Joaquim Manuel Freire Luís wrote: > > Hi Even, FYI, you have e-mailed the public gdal-dev mailing list. > I have no idea why that might happen and tried to run it with CPL_DEBUG as in > gmt grdgdal lixo.csv -R0/10/0/10 -Gjunk.nc -I0.05 -F"-a nearest -co > CPL_DEBUG=ON" > (this is a mixed GMT and GDAL syntax (the part under double quotes), never > mind. It just works locally) > > But got no debug printouts from the CI test. Am I wrongly using the > CPL_DEBUG? All GDAL versions in CI are above 2.1 See https://trac.osgeo.org/gdal/wiki/ConfigOptions#CPL_DEBUG, may help. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Refreshing GDAL's logo
On Mon, 10 Feb 2020 at 22:30, Sean Gillies wrote: > On Mon, Feb 10, 2020 at 1:56 AM Even Rouault > wrote: >> >> So looking at https://github.com/OSGeo/gdal/issues/2117, it seems we didn't >> get more proposals than the ones from 2 weeks ago. There are 3 proposals in >> the initial post of the ticket: nirvn_v1, nirvn_v2 and nirvn_v3 >> In https://github.com/OSGeo/gdal/issues/2117#issuecomment-570059241 , there's >> also a variant of nirvn_v3 with the compas/satellite replacing the A. >> >> Thoughts ? (PSC and community) > > > Of the three proposals I'm -1 on v1, +0 on v2, -0 on v3. Likewise, I'm happy to copy Sean's scoring as my own. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] WGS84 -> WGS84 transform flips axes
On Thu, 6 Feb 2020 at 13:29, Daniel Evans wrote: > > I'm still so backwards that I rely on the Git repository and the Python API > documentation for information (https://gdal.org/python/) > but I've discovered that the latter is rather out of date today, as options > like GetAxisMappingOrder aren't listed at all. Any API reference, even an up to date one, is intrinsically a specific and narrow view at a library features and as such it is not a reliable source of information about architecture, behaviour, caveates and corner cases of a complex system like GDAL. It's not uncommon Python-oriented developers skip the *core* docs thinking "that is for the C/C++ camp folks" and relying on the Python API reference. It's a mistake. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] WGS84 -> WGS84 transform flips axes
On Thu, 6 Feb 2020 at 13:20, Daniel Evans wrote: > > > Try https://gdal.org/tutorials/osr_api_tut.html#crs-and-axis-order > > Thanks - I hadn't spotted your response until sending mine just now. That is > indeed what's going on, with the setting being changed depending on how an > SRS has been used. You're welcome. BTW, I know most of us still remember search-less gdal.org, and we don't even attempt to search the GDAL docs, but last May things have greatly improved - we've got ourselves the new shiny slick and cool search box :) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
