Hi Lester,
As 2.0 is due out soon, can you confirm if this happens in one of the
builds for that? (or wait for 2.0 to come out, though that could be a while
I guess)).
Regards,
Jonathan
On 25 June 2013 12:59, Lester Anderson wrote:
> Hi Jonathan,
>
> Not sure what the trigger number is, but I have one project with rasters
> covering the same area and in total there are about 15, with interpreted
> vector layers overlying them all (i.e. at the top of the list).
>
> I have attached a screen grab to show what I mean. Not all rasters are
> turned on either, just a few in the list. Note: the coastline is at the
> very top yet is hidden by a raster way below!
>
> If I get time I can test at what level it trips up.
>
> Cheers
> Lester
>
>
>
> On 25 June 2013 12:36, Jonathan Moules > wrote:
>
>> Hi Lester,
>> A couple of questions:
>> 1) How many raster layers are there required to make this happen? Don't
>> need the trigger amount as you don't know it, but are we talking dozens?
>> Hundreds? Thousands?
>> 2) Are all the rasters overlapping the same area or are they scattered
>> around (i.e. a mosaic).
>>
>> Cheers,
>> Jonathan
>>
>> On 22 June 2013 09:44, Lester Anderson wrote:
>>
>>> Hello,
>>>
>>> Found an odd problem, but if your project has a few vector layers and a
>>> large number of rasters covering the same area, then it seems that after a
>>> certain number, not sure how many, but the vector layers at the top of
>>> everything no longer remain visible.
>>>
>>> Put simply, if you have a coastline layer at the top, overlying
>>> everything, and add more and more rasters, eventually it gets "buried" by
>>> the rasters.
>>>
>>> I am using 1.8.0 and have seen this problem a number of times with the
>>> layers - tried re-ordering and putting the vector layer to the front again,
>>> but no joy. There does appear to be a bug with visibility if too many
>>> coincident rasters are loaded. I basically have to create separate projects
>>> for certain raster/vector structures now to get around this.
>>>
>>> Has anyone else seen this issue?
>>>
>>> Cheers
>>>
>>> Lester
>>>
>>> ___
>>> Qgis-user mailing list
>>> Qgis-user@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-user
>>>
>>>
>>
>> This transmission is intended for the named addressee(s) only and may
>> contain sensitive or protectively marked material up to RESTRICTED and
>> should be handled accordingly. Unless you are the named addressee (or
>> authorised to receive it for the addressee) you may not copy or use it, or
>> disclose it to anyone else. If you have received this transmission in error
>> please notify the sender immediately. All email traffic sent to or from us,
>> including without limitation all GCSX traffic, may be subject to recording
>> and/or monitoring in accordance with relevant legislation.
>
>
>
--
This transmission is intended for the named addressee(s) only and may
contain sensitive or protectively marked material up to RESTRICTED and
should be handled accordingly. Unless you are the named addressee (or
authorised to receive it for the addressee) you may not copy or use it, or
disclose it to anyone else. If you have received this transmission in error
please notify the sender immediately. All email traffic sent to or from us,
including without limitation all GCSX traffic, may be subject to recording
and/or monitoring in accordance with relevant legislation.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
