Enable tagging unspecific crossing

[matkoniecz]

fixes #834

[github-actions]

🍱 Preview the tagging presets of this pull request here: https://pr-837--ideditor-presets-preview.netlify.app/id/dist/#locale=en.

[matkoniecz]

#834 (comment) points out serious issue - it is also correct for cases where cycleway crosses road and maybe even where footway crosses cycleway

[tyrasd]

Yeah… just calling it "Crossing" should be better here, as that accommodates both foot and bike crossings. I've adapted the PR accordingly. I've also added a few additional search terms and enabled the crossing fields as optional moreFields (such that if a crossing is mapped with, e.g. a crossing:island tag, but without crossing=*, the information is not hidden from the mapper).

What do you think?

[matkoniecz]

crossing:signals tag seems to be not shown

optional moreFields (such that if a crossing is mapped with, e.g. a crossing:island tag, but without crossing=*, the information is not hidden from the mapper).

What about making them appear already when not tagged (at least crossing signals one) to encourage mapper to answer them?