Look for tactile paving on kerbs, not (just) on crossing nodes

[KTibow]

I was auditing the OSM ecosystem for apps that only look at tactile paving information on crossing nodes (problematic if we switch to something like tactile_paving=separate) and I noticed Soundscape seems to be one of them. My agents have all sorts of crazy ideas for how to best handle this and warnings about indirection from the tile generation server, but I'll just state the problem:

Currently
"whether or not to announce an unmarked crossing" is determined by "is tactile_paving=yes on the crossing node"

When it should be
determined by (or at least combined with) "are there kerb nodes with tactile_paving=yes connected"

[davecraig]

Thanks for filing this - I've been off on vacation, so apologies for the delay. The use of crossing info in Soundscape is very much placeholder at present, but this is a good reminder that there's more that we want to do. I'll take a look at the kerb tag.