Systematic false positive: Roller coaster tracks

[Hiausirg]

Hello,
the check "Untagged named object" (2110) highlights objects which are (correctly) tagged with "roller_coaster=track" as being "untagged". This should be fixed.
I assume that roller coasters which have no name are probably also catched as untagged by another filter/check, but I don't know which one.
I noticed this issue here.

Note that those roller coasters are also highlighted as being self-intersecting polygons. I'm unsure if this is an issue (but I think that it is very common that roller coasters overlap)

Greetings

[Famlam]

the check "Untagged named object" (2110) highlights objects which are (correctly) tagged with "roller_coaster=track" as being "untagged". This should be fixed.

I'm not sure.. is the track itself named (like a highway) or should the name tag be on the surrounding area ( https://wiki.openstreetmap.org/wiki/Tag:attraction%3Droller_coaster ) that also includes i.e. the buildings etc that belong to it. It seems to be used quite... randomly if I just peak around some attraction parks.
There's 3317 ways worldwide with roller_coaster=track + name=*, out of 6649 ways with the same tags, e.g. 50%. And there's 2231 out of 3094 ways/nodes worldwide with attraction=roller_coaster + name=* (72%).

---

Note that those roller coasters are also highlighted as being self-intersecting polygons. I'm unsure if this is an issue (but I think that it is very common that roller coasters overlap)

Oops, when fixing #1960 I forgot to update https://github.com/osm-fr/osmose-backend/blob/08b919d02c0c0e8c7729261e88886fd92d9b554c/analysers/analyser_osmosis_polygon.py#L35
However, I suspect that roller coasters should have different layers where they overlap. So I guess it's better to split the way in ways with different layers anyway.

[Famlam]

@frodrigo your call, allow name on rollercoaster tracks or not? I have no strong opinion, and it is pretty common

[frodrigo]

As say on the wiki, for me the name should be on with attraction=roller_coaster key.

attraction=roller_coaster + roller_coaster=track Could be on same object, with the name ? That may solve the issue

[Famlam]

attraction=roller_coaster + roller_coaster=track Could be on same object [...]

No, the related wikis explicitly mention that those two tags are incompatible. (Even though it occurs relatively frequently)

[Famlam]

@Hiausirg do you have a strong opinion about this? Maybe it was discussed in a mailing list that we're not aware of, for instance, that discusses whether names should be on the track or the attraction=* object

[Hiausirg]

Not at all. Track, attraction or both?, no idea.
I've never mapped any such theme parks or similar, the primary problem I saw was that those roller coaster tracks were highlighted as being "untagged" objects, but "roller_coaster=track" is a 'primary' descriptive tag (so they're not actually "untagged"). Hope thats understandable.

No idea where the name should be.

[Famlam]

How about simply Unexpected name on element instead of Untagged named object?

[frodrigo]

How about simply Unexpected name on element instead of Untagged named object?

I think, the issue is more about missing tags than the name tag.

[Famlam]

True, I was primarily thinking of something that would also cover existing objects (like the roller coaster track) that are tagged, but not expected to have a name on it. untagged named object is misleading for such cases.