I keep haviing issues with projects which lose the CRS settings between
saves, that are being edited with 2.99 editions. However as the masters
are built nightly and so there are new versions coming out all the time,
it is difficult to keep track of which was the edition that was
previously
I just saw it with projects in some fairly recent builds of the master,
opening project files saved in earlier master builds.
On 09/10/17 00:00, Anita Graser wrote:
Thanks Patrick!
On Sun, Oct 8, 2017 at 1:46 AM, Patrick Dunford
>
Thanks Patrick!
On Sun, Oct 8, 2017 at 1:46 AM, Patrick Dunford
wrote:
> There are some circumstances in which you have to re-enter your CRS when
> opening a project in a development master, this is just an issue with
> importing project files with some of the
There are some circumstances in which you have to re-enter your CRS when
opening a project in a development master, this is just an issue with
importing project files with some of the development versions.
On 08/10/17 01:07, Anita Graser wrote:
I've now tested this on another machine and the
Thanks Matthias,
On Sat, Oct 7, 2017 at 2:40 PM, Matthias Kuhn wrote:
>
> Just reading through the tickets and without much context: they very much
> look like individual issues without any overlap, so I would go for
> different tickets.
>
>
> Here they are:
1. Wrong
Hi Anita,
Just reading through the tickets and without much context: they very
much look like individual issues without any overlap, so I would go for
different tickets.
Thanks
Matthias
On 10/07/2017 02:07 PM, Anita Graser wrote:
I've now tested this on another machine and the issues are
I've now tested this on another machine and the issues are same.
I open separate tickets or one with all three issues?
Regards,
Anita
On Fri, Oct 6, 2017 at 7:46 PM, Anita Graser wrote:
> Hi,
>
> I'm experiencing a couple of issues related to custom / generated CRS in
>
Hi,
I'm experiencing a couple of issues related to custom / generated CRS in
master (tested using OSGeo4W):
1. In Processing: If the input layer uses a generated / custom CRS, the
output layer is loaded in a wrong CRS. In my case, the layers were wrongly
assigned WGS84. (Note that, in settings,