Feature request #3706

improve loading of qml to load source layer

Added by Duarte Carreira almost 6 years ago. Updated over 1 year ago.

Status:Closed Start Date:
Priority:Low Due date:
Assigned to:- % Done:

100%

Category:Map Legend
Target version:Future Release - Nice to have
Platform: Resolution:fixed/implemented
Platform version: Pull Request or Patch supplied:No
Status info:0 Tag:

Description

This is an improvement to allow QGIS to load pre-symbolized layers, in one step, data source and symbology. This is different (better) from what is available today: load layer, apply .qml, or load layer with .qml with the same name in a particular folder.

This would ideally work with 2 new options in the layer context menu, like "save styled layer" and "load styled layer", that would save and load a layer as is in the project.

Advantages to the present capability:

i) we can have a single data source with several .qml allowing multiple representations of the same data, prepared and made available to users in an organization by a GIS team

ii) user don't need to know about data structure, this is in fact abstracted. Users work with "themed data", like population by county, or income by county, regardless if the data comes from a shapefile or PostGIS

iii) this will allow a GIS dept. in an organization to prepare a shared folder with a set of layers that the users can load, in fact creating a standard for their GIS, regarding the data used, and the symbology applied.

This is common practice in other GIS software, like ArcGIS (.lyr files) and AutoCAD Map (don't know the file extension).

As it stands now, using QGIS a user has to i) know which data to load; ii) know which attribute holds the needed data; iii) know how to symbolize the layer. And the reusability of this work is very limited (to a project?).

The ability to automatically apply a .qml that has the same name as the the data source has several limitations: i)it works based on a a single PC configuration, depending on the user; ii) it is limited to 1 .qml per data source; iii) it is difficult to scale to several users in a managed context.

Duarte

History

Updated by Giovanni Manghi almost 6 years ago

Hi Duarte, let's come to the dev meeting in Lisbon to propose and hack this enhancement! ;)

abraços

Updated by Duarte Carreira almost 6 years ago

I'll do all I can to be there! Hoping one of the gurus will pick this up!

Duarte

Replying to [comment:1 lutra]:

Hi Duarte, let's come to the dev meeting in Lisbon to propose and hack this enhancement! ;)

abraços

Updated by Giovanni Manghi over 5 years ago

  • Target version changed from Version 1.7.0 to Version 1.7.4

Updated by Giovanni Manghi almost 5 years ago

  • Target version changed from Version 1.7.4 to Version 2.0.0

Updated by Pirmin Kalberer over 4 years ago

  • Target version changed from Version 2.0.0 to Future Release - Nice to have

Updated by Médéric RIBREUX over 1 year ago

  • Status changed from Open to Closed
  • Assigned to deleted (nobody -)
  • % Done changed from 0 to 100
  • Platform deleted (Debian)
  • Resolution set to fixed/implemented
  • Pull Request or Patch supplied set to No

Hello, bug triage...

this feature request is covered by Layer Definition Files (.qlr) which do exactly what .lyr in ArcGIS do.

I am closing this feature request.

Also available in: Atom