Osmose says `{{0.key}}={{0.value}} is unspecific`. Osmose's message is not understandable. There is no tag `{{0.key}}={{0.value}}` on the element.

[dreirund]

Ahoj,

Osmose gives me on ↗ this OSM object a note

{{0.key}}={{0.value}} is unspecific. Please replace '{{0.value}}' by a specific value.`

(↗ Osmose issue)

The tags on the object are:

label=EN 124 - B125
man_made=manhole
manhole:shape=quadratic
manhole=unknown

What does it mean, what should I do with it? The message is not understandable by me.
↗ Here in the OpenStreetMap forum it was suggested that this is an Osmose bug, so I report it here.

Screenshot:

---

---

This issue also appears at other items in the same area.

(manhole=unknown cannot be the issue, since there are other manhole=unknown where Osmose gives an understandable message:

Unspecific value
Concerns tag: manhole=unknown

e.g. this Osmose issue.)

Regards!

[matkoniecz]

I would say that it seems to be in fact complaining about manhole=unknown but this unfilled template really should not be shown to users, so it is still a bug

[Famlam]

Parsing placeholders in the title is difficult with the current implementation of mapcss, but perhaps we can make it a bit more readable

[frodrigo]

This come from MapCSS (and JOSM). The MapCSS does not has a title of class of issue, while Osmose require one.

So the raw string is used as class title. For each issue the string is completed with the extact tags values.

That is by design, it is not a bug.

Note MapCSS can be grouped using group. While group is declared the group is used as class title.

[dreirund]

This come from MapCSS (and JOSM).

So does JOSM in fact create the issues, and not the Osmose-Service by itself?

I am confused.

The thing is, that in the vicinity there are other Osmose-Issues also about manhole=unknown that do not show the title that does not make sense to the user.

[frodrigo]

El vie, 23 may 2025, 11:58, dreirund ***@***.***> escribió:

*dreirund* left a comment (osmose-qa/osmose-backend#2513) <#2513 (comment)> *This come from MapCSS (and JOSM).* So does JOSM in fact create the issues, and not the Osmose-Service by itself? I am confused.

When possible, JOSM validator rules are reused in Osmose-QA. Osmose-QA is able to run by it self the JOSM rules written in Map css format. The thing is, that in the vicinity there are other Osmose-Issues also about

manhole=unknown that do *not* show the title that does not make sense to the user.

Please give a link.

[matkoniecz]

So the raw string is used as class title. For each issue the string is completed with the extact tags values.
That is by design, it is not a bug.

what about empty/hidden class title? showing this in interface is simply confusing

[frodrigo]

The title is used in other place than the popup, and more over without the version where place holder are replaced El vie, 23 may 2025, 13:53, Mateusz Konieczny ***@***.***> escribió:

…

*matkoniecz* left a comment (osmose-qa/osmose-backend#2513) <#2513 (comment)> So the raw string is used as class title. For each issue the string is completed with the extact tags values. That is by design, it is not a bug. what about empty/hidden class title? showing this in interface is simply confusing — Reply to this email directly, view it on GitHub <#2513 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANT5DWRDGWA4NT5BI3O4KD274D4DAVCNFSM6AAAAAB5V7VH2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBUGE3TQNJYHE> . You are receiving this because you commented.Message ID: ***@***.***>

[matkoniecz]

then maybe it should be suppressed/hidden only in that part of interface?

[dreirund]

manhole=unknown that do not show the title that does not make sense to the user.
Please give a link.

I already gave in my initial issue report.

Here one again:

https://osmose.openstreetmap.fr/en/issue/c381227d-de47-7550-3834-f395b86ac6f2

---

---

[frodrigo]

• https://osmose.openstreetmap.fr/en/issue/c381227d-de47-7550-3834-f395b86ac6f2
• https://osmose.openstreetmap.fr/en/issue/e27b63e9-f8df-7025-3db6-2e35ae737fbf

Are two different issues

• item=9002, class=9002007 from JSOM MapCSS https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator/deprecated.mapcss
• item=406, class=40613 from Osmose-QA own rules https://github.com/osm-fr/osmose-backend/blob/master/plugins/TagFix_BadValue.py#L42

[dreirund]

Are two different issues

• [...] from JSOM MapCSS
• [...] from Osmose-QA own rules

I as a user have no idea how the services in the background work. I see the website (or use a third-party Osmose consumer like SCEE), and want to use it to get hints about what OSM objects to look at, and get on some issues the title which I cannot make sense of, on others a title which I can make sense of.

If you think that this issue is better places somewhere else, e.g. at osmose-frontend, feel free to move.

[frodrigo]

If you think that this issue is better places somewhere else, e.g. at osmose-frontend, feel free to move.

That on both side.

Feel free to propose an implementation.