Feature request #19790

Handle Bad Layers - DISABLE instead of DELETE

Added by Worth Lutz about 1 year ago. Updated 12 months ago.

Status:Closed
Priority:Normal
Assignee:-
Category:Unknown
Pull Request or Patch supplied:No Resolution:fixed/implemented
Easy fix?:No Copied to github as #:27615

Description

This is a request for a change to the "Handle Bad Layers" dialog. This should be a change to the QGIS core.

The scenario is working offline and loading a project with WMS or other unreachable layers defined. As the WMS is unreachable, the layers are marked as "bad". Since the layers are not fixable while offline, they get deleted from the project. This also happens when working remotely and not connected to network shares at the office.

It would be nice to be able to edit the layers locally stored on my laptop and not lose the definitions of the WMS or other "bad" layers in the the project.

I propose that the "bad" layers be somehow marked as "DISABLED" only for the duration of the current session working on the project. By not deleting these "bad" layers, they will be available the next time the project is opened where the source is actually reachable.

Further ideas are:

  • "bad" layers which are disabled could also be marked with an exclamation point
  • for the "disabled" layers, have the right click context menu have the options: delete, fix, hide(for this session only), ... *

Related issues

Duplicates QGIS Application - Feature request #8718: Do not remove unavailable layers when opening project Closed 2013-09-29

History

#1 Updated by Regis Haubourg about 1 year ago

+1 Much needed

#2 Updated by Roberto Uhlig about 1 year ago

Correlated or same as nearly fife years old #8718 https://issues.qgis.org/issues/8718
+1 Much needed

#3 Updated by Nyall Dawson about 1 year ago

FYI - if this remains unfixed for the 3.6 cycle, North Road are planning a crowd funding effort to implement this change.

#4 Updated by Roberto Uhlig about 1 year ago

Thanks for information and keeping on track.
May be, there could be some ideas from the maintainer of the "changeDataSource" plugin enrico ferreguti (enricofer).

https://github.com/enricofer/changeDataSource/issues/10

#5 Updated by Knut Berg about 1 year ago

+1 Much needed.

#6 Updated by Harrissou Santanna 12 months ago

#7 Updated by Harrissou Santanna 12 months ago

  • Resolution set to fixed/implemented
  • Status changed from Open to Closed

Also available in: Atom PDF