Opened 2 months ago

Last modified 2 months ago

#20300 new enhancement

problem with Crossing railways validation

Reported by: mkoniecz Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: template_report Cc:

Description (last modified by mkoniecz)

What steps will reproduce the problem?

  1. encounter track ballast areas tagged as natural=scree
  2. retag blatant tagging for renderer to new tag railway=track_ballast
  3. run validator

What is the expected result?

No complaints

What happens instead?

Crossing railways warning where railway=rail crosses railway=track_ballast areas

Please provide any additional information below. Attach a screenshot if possible.

See for example

Yes, it is a completely brand-new tag. Should I switch to man_made=track_ballast or is it possible to get special-casing despite it is brand new tag and quite absurd one?

triggered by

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-12-23 08:02:18 +0100 (Wed, 23 Dec 2020)
Build-Date:2020-12-24 02:30:53

Identification: JOSM/1.5 (17425 en_GB) Linux Ubuntu 20.04.1 LTS
Memory Usage: 1513 MB / 3974 MB (341 MB allocated, but free)
Java version:, Ubuntu, OpenJDK 64-Bit Server VM
Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel
Screen: :0.0 1920×1080 (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→16×16, 32×32→32×32
Desktop environment: LXQt
Java package: openjdk-11-jre:amd64-
Java ATK Wrapper package: libatk-wrapper-java:all-0.37.1-1
Environment variable LANG: en_GB.UTF-8
libcommons-logging-java: libcommons-logging-java:all-1.2-2
fonts-noto: fonts-noto:-
Dataset consistency test: No problems found

Last errors/warnings:
- 00009.191 W: No route to host (Host unreachable)
- 00009.192 W: Failed to read MOTD. Exception was: No route to host (Host unreachable): No route to host (Host unreachable)
- 00542.837 W: Socket closed. Cause: Socket closed. Cause: Socket closed
- 00542.839 E: Socket closed. Cause: Socket closed. Cause: Socket closed
- 02914.252 W: Conflict in data - <html>This relation has been changed outside of the editor.<br>You cannot apply your changes and continue editing.<br><br>Do you want to create a conflict and close the editor?</html>
- 02916.708 W: Unsaved changes - <html>The relation has been changed.<br><br>Do you want to save your changes?</html>
- 03070.351 E: Error header: Version mismatch: Provided 5, server had: 6 of Relation 8878407
- 03070.507 E: Conflicts detected - <html>Uploading <strong>failed</strong> because the server has a newer version of one<br>of your nodes, ways, or relations.<br>The conflict is caused by the <strong>relation</strong> with id <strong>8 878 407</strong>,<br>the server has version 6, your version is 5.<br><br>Click <strong>Synchronise relation 8 878 407 only</strong> to synchronise the conflicting primitive only.<br>Click <strong>Synchronise entire dataset</strong> to synchronise the entire local dataset with the server.<br>Click <strong>Cancel</strong> to abort and continue editing.<br></html>

Attachments (0)

Change History (7)

comment:1 Changed 2 months ago by mkoniecz

Description: modified (diff)

comment:2 Changed 2 months ago by mkoniecz

I can make patch and/or wiki proposal for that tag if that would help

Last edited 2 months ago by mkoniecz (previous) (diff)

comment:3 Changed 2 months ago by mkoniecz

Description: modified (diff)

comment:4 Changed 2 months ago by GerdP

I think this bugtracker is not the right place to discuss new tags. It doesn't even appear in Taginfo yet.

comment:5 Changed 2 months ago by mkoniecz

I do not expect or want support in presets - I just wonder what is needed to get rule in validator that would remove this false positive.

Some usage? That will be just about 500 objects ( )

Active proposal? Accepted proposal? OSM wiki page documenting this tag?

I am not planning to map more of THAT, I just want to retag what was mapped into something that is not a blatant tagging for renderer.

And if railway=track_ballast is doomed to trigger validation warnings, then I will retag it into track_ballast=yes or man_made=track_ballast or something similar to avoid it.

Last edited 2 months ago by mkoniecz (previous) (diff)

comment:6 Changed 2 months ago by GerdP

I have no idea what exactly the tag means, I only know landuse=railway for the area next to rails.

comment:7 Changed 2 months ago by mkoniecz

Someone mapped areas with track ballast ( ), using natural=scree (tagging for the renderer).

I tried to look for suitable tag for that, but noone tagged it (except that would trigger vaidator complaint anyway).

So I tried using railway=track_ballast that caused crossing railways warning where railway=rail (and probably also railway=tram etc) crosses railway=track_ballast areas.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to mkoniecz
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.