Re: [gdal-dev] Freenode IRC taken over(was Fwd: [SAC] [Hosting] OSUOSL IRC channels moving to irc.libera.chat)

2021-05-19 Thread Greg Troxel
Even Rouault writes: > See below about Freenode IRC having been taken over (or considered as > such by most Freenode admins), which affects our existing #gdal > channel. gdal and everybody else :-( > What should we do: > > - give up with IRC at all, and just use the Slack channel ? Would make

Re: [gdal-dev] A Swift wrapper for GDAL

2021-05-19 Thread John Daniel
Hello Robert, I’ve looked at this myself a few times. Here are some interesting points: GDAL already supports SWIG bindings. If you are really into Swift, then you could potentially add Swift to SWIG and get support that way. I would not recommend using the C interface. The C interface is alread

Re: [gdal-dev] Freenode IRC taken over(was Fwd: [SAC] [Hosting] OSUOSL IRC channels moving to irc.libera.chat)

2021-05-19 Thread Pirmin Kalberer
Hi, On 19.05.21 21:00, Even Rouault wrote: See below about Freenode IRC having been taken over (or considered as such by most Freenode admins), which affects our existing #gdal channel. What should we do: - give up with IRC at all, and just use the Slack channel ? Would make things more si

Re: [gdal-dev] A Swift wrapper for GDAL

2021-05-19 Thread Gaige B. Paulsen
I’ve been using GDAL on macOS for years (and iOS as well, both mostly with Objective-C) using C bindings and some Objective-C helpers that I’ve put together over time. The C bindings are suitable for use with Objective-C and shouldn’t be difficult to use as a bridge to Swift. Also, if necessar

Re: [gdal-dev] Call for discussion on RFC 83: guidelines for the use of GDAL project sponsorship

2021-05-19 Thread Jeff McKenna
On 2021-05-19 12:19 p.m., Mateusz Loskot wrote: 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. Good document. My only comment is that this document should also define how the PSC decisions men

Re: [gdal-dev] Call for discussion on RFC 83: guidelines for the use of GDAL project sponsorship

2021-05-19 Thread Mateusz Loskot
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.osge

Re: [gdal-dev] A Swift wrapper for GDAL

2021-05-19 Thread Even Rouault
Roberto, I can't answer on the Swift specific part, but yes, the C API is what is commonly used to create bindings to other languages. What is uniquely found in the C++ one is very advanced things that most people rarely need. Even Le 19/05/2021 à 16:08, Roberto Arista a écrit : Dear gdal-d

[gdal-dev] A Swift wrapper for GDAL

2021-05-19 Thread Roberto Arista
Dear gdal-dev list, I would like to use the GDAL library for a macOS project using the Swift language. Wrapping a C++ library in Swift is not straightforward at all, and I could not find a satisfactory solution so far. There are a few projects on GitHub: > https://github.com/optionu/Humboldt > h

[gdal-dev] Call for discussion on RFC 83: guidelines for the use of GDAL project sponsorship

2021-05-19 Thread Even Rouault
Hi, in parallel to finalizing the last steps to get the relationship with NumFOCUS fully operational, here's a new RFC for your consideration to give guidelines on how we can use the sponsorship funds, who can apply, etc. Input welcome. https://github.com/OSGeo/gdal/pull/3855 Even -- http:

Re: [gdal-dev] RPC to geotransform converting

2021-05-19 Thread Even Rouault
You mean the HEIGHT_OFFSET parameter in the RPC ? Yes, that can generally be used as a first-order correction if you don't use a DEM. I'm not sure using it vs not-using it has been a deliberate choice. One could say that with the current behavior people know that something is wrong and must thu

Re: [gdal-dev] RPC to geotransform converting

2021-05-19 Thread Denis Rykov
Finally I solved the issue by adding "-to RPC_HEIGHT=XXX" to gdalwarp. It seems gdalwarp doesn't take this parameter into account even if it is presented in the RPC *.txt file. Should I file the ticket or was it done by purpose? On Tue, May 18, 2021 at 11:26 PM Denis Rykov wrote: > Thanks! > > O