On 9 March 2018 at 19:39, Kristian Evers wrote:
> All,
>
> Just to follow up on this, since I am the one to blame for this error to show
> up.
Kristian -- just to add my 2c here, there's absolutely NO-ONE who can
blame you for this mistake, please do not beat yourself up over this!
I'm sure ther
On 03/09/2018 07:04 PM, Richard Duivenvoorde wrote:
> ps README.md still talking about ./configure in "Building on Unix/Linux"
> while apparently it is not there anymore?
It's there after you run autogen.sh.
___
QGIS-Developer mailing list
QGIS-Developer
On 09-03-18 16:30, Even Rouault wrote:
>
> I don't think the removal of "+nadgrids=@null" is a "universal"
> workaround. It only works when the other SRS has no +towgs84 or
> +nadgrids clause itself, which isn't the case of EPSG:28992. Basically
> if you transform between EPSG:28992 and WebMercat
On vendredi 9 mars 2018 12:19:09 CET Richard Duivenvoorde wrote:
> Hi All,
>
> I second that: not blaming anybody here. This happens in the real world.
>
> My point was that I think as QGIS we can 'hide' this issue by not using
> 5.0.0 'yet' in the osgeo4w package.
>
> I will happily use/test wh
On vendredi 9 mars 2018 11:38:17 CET Even Rouault wrote:
> Kristian
>
> your are certainly not too blame at à personal level. this is the kind of
> this that happen inevitably given a certain amount of changes . i'm
> surprised that the GDAL autotest suite did not catch this but the cause is
> li
ts.osgeo.org] På vegne af
Jeff McKenna
Sendt: 8. marts 2018 12:50
Til: qgis-developer@lists.osgeo.org
Emne: Re: [QGIS-Developer] proj5 and epsg:3857 ?
Hi Richard,
You can read my report to the PROJ team while I was testing the release
candidates:
http://lists.maptools.org/pipermail/proj/2018-Februar
Il 09/03/2018 12:27, Sebastiaan Couwenberg ha scritto:
> FWIW, proj (5.0.0-3~exp1) available in Debian experimental contains a
> patch with the cherry-picked commit that fixes this issue. [0]
Thanks Bas!
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/trainin
On 03/09/2018 12:19 PM, Richard Duivenvoorde wrote:
> I will happily use/test whatever is available in Debian sid :-)
FWIW, proj (5.0.0-3~exp1) available in Debian experimental contains a
patch with the cherry-picked commit that fixes this issue. [0]
It also contains a patch with the changes fro
Am Fr, 9.03.2018, 12:19 schrieb Richard Duivenvoorde:
>
> My point was that I think as QGIS we can 'hide' this issue by
> not using 5.0.0 'yet' in the osgeo4w package.
Hehe, proj is hiding itself, since 493 is still shown in "about" ;)
___
QGIS-Develope
s - Geospatial professional services
> http://www.spatialys.com
>
>
> Message d'origine ----
> De : Kristian Evers
> Date :09/03/2018 10:39 (GMT+01:00)
> À : qgis-developer@lists.osgeo.org
> Cc :
> Objet : Re: [QGIS-Developer] proj5 and epsg:3857 ?
>
gine De : Kristian Evers
Date :09/03/2018 10:39 (GMT+01:00) À :
qgis-developer@lists.osgeo.org Cc : Objet : Re:
[QGIS-Developer] proj5 and epsg:3857 ?
All,
Just to follow up on this, since I am the one to blame for this error to show
up.
Both by introducing it in the first place and by relea
stones?direction=asc&sort=due_date&state=open
-Oprindelig meddelelse-
Fra: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] På vegne af
Jeff McKenna
Sendt: 8. marts 2018 12:50
Til: qgis-developer@lists.osgeo.org
Emne: Re: [QGIS-Developer] proj5 and epsg:3857 ?
Hi Ri
Hi Tobias,
On Thu, 08. Mar 2018 at 10:07:02 +0100, Tobias Wendorff wrote:
> Can anyone forward this to osgeo4w-dev please?
No need.
Jürgen
--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50
Can anyone forward this to osgeo4w-dev please?
--
Von einem iPhone gesendet und wird daher Fehler enthalten…
Am 08.03.2018 um 09:49 schrieb Even Rouault :
> > But given we know this is an issue now, we should not distribute this
> > further to Windows users/osgeo4w who are NOT running a testing
> But given we know this is an issue now, we should not distribute this
> further to Windows users/osgeo4w who are NOT running a testing
setup.
Or, good thing with open source, don't wait for official release and
apply the patch that fixes the issue :
https://github.com/OSGeo/proj.4/pull/830.dif
On 08-03-18 09:05, Bas Couwenberg wrote:
> On 2018-03-08 08:43, Richard Duivenvoorde wrote:
>> As we have OSM xyz layer now, and I think a lot of people will use it as
>> a quick reference map, we should be carefull to include proj5 in
>> distributions/installs then I think?
>>
>> Like: let's not p
On 2018-03-08 08:43, Richard Duivenvoorde wrote:
As we have OSM xyz layer now, and I think a lot of people will use it
as
a quick reference map, we should be carefull to include proj5 in
distributions/installs then I think?
Like: let's not put proj5 as default in Osgeo4w untill this is
fixed/re
On 07-03-18 21:18, Even Rouault wrote:
> On mercredi 7 mars 2018 21:13:36 CET Richard Duivenvoorde wrote:
>> Hi,
>
>> Having a geocoder plugins, in 2.18 (still proj4), I can geocode my home
>
>> address, and reproject the epsg:28992 coordinate fine to epsg:3857.
>
>> But since last week Debian ha
On mercredi 7 mars 2018 21:13:36 CET Richard Duivenvoorde wrote:
> Hi,
>
> Having a geocoder plugins, in 2.18 (still proj4), I can geocode my home
> address, and reproject the epsg:28992 coordinate fine to epsg:3857.
>
> But since last week Debian has proj5, and the same plugin (in QGIS
> master)
Now I look in the terminal, and I see this text looping for ever:
src/core/raster/qgsrasterprojector.cpp: 440: (preciseSrcRowCol) [0ms]
theDestRow = 602
src/core/raster/qgsrasterprojector.cpp: 459: (preciseSrcRowCol) [0ms] x
= 514940 y = 6.83887e+6
src/core/raster/qgsrasterprojector.cpp: 441: (pre
Hi,
Having a geocoder plugins, in 2.18 (still proj4), I can geocode my home
address, and reproject the epsg:28992 coordinate fine to epsg:3857.
But since last week Debian has proj5, and the same plugin (in QGIS
master) now is off by 500 meter.
To reproduce: if you have a QGIS 2.18 with proj4, an
21 matches
Mail list logo
