labels consisting of multiple field should be possible

[qgib]

Author Name: Gerhard Spieles (Gerhard Spieles)
Original Redmine Issue: 1419

Redmine category:vectors

---

In practice, often more then one field is necessary to be labeld in multilines
Is it possible to realize this function?

For idea:
In Layer properities, Symbology, [[LegendType]], youu can choose "Uniqe value" an then you can add classes to show different styles depend of the content of fields

The same classification should be good for the labeling.

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

see also #12184

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

see also #12147

[qgib]

Author Name: Sandro Santilli (@strk)

---

Could "multiple labels" as described in ticket #13854 be a solution for this as well ?

[qgib]

Author Name: Alister Hood (@AlisterH)

---

No. That is for situations where you want to put different labels in different places. This is for situations where you want to create one label from several fields, e.g. you might want to create a label for a manhole that lists its name, diameter, lid level, and invert level:

MH2
1050Ø
LL 6.8
IL 4.2

You certainly wouldn't want to have these as four different labels around the same point, and you wouldn't want to use four different labels with fixed offsets (especially if some of the information is missing sometimes), and it would be annoying having to set up four sets of labels anyway.

[qgib]

Author Name: Alister Hood (@AlisterH)

---

That should have looked something like this :)

MH2
1050Ø
LL 6.8
IL 4.2

[qgib]

Author Name: Sandro Santilli (@strk)

---

agreed, this one has its own merit (I just had one such use case)

[qgib]

Author Name: Borys Jurgiel (@borysiasty)

---

see also #13548 (and #13901 )

---

• assigned_to_id removed nobody

[qgib]

Author Name: Aren Cambre (Aren Cambre)

---

I'm gonna be bold and say that #13548 is an elegant solution to this issue. As #13548 is more specific and has actual progress, it may be best to go with that one.

---

• pull_request_patch_supplied was configured as 0
• status_id was changed from Open to Closed
• resolution was changed from to duplicate