The source pbf use osmium -s smart option to keep geometry of way crossing the border and it's needed for another project on vector tile.
That cause crossing way and kerbs are not inclued in the pbf, while the crossing node part of the way concerned is conserved.
That generate false positive on tactile paving issues process. (and probably on sidewalk gap/side too)
Cutting by reprocessing the pbf without smart strategy will just move the problem on the exact border (or on the buffer zone).
Implement a check for theses case and exlude this false positive from the reporting.
The source pbf use osmium -s smart option to keep geometry of way crossing the border and it's needed for another project on vector tile.
That cause crossing way and kerbs are not inclued in the pbf, while the crossing node part of the way concerned is conserved.
That generate false positive on tactile paving issues process. (and probably on sidewalk gap/side too)
Cutting by reprocessing the pbf without smart strategy will just move the problem on the exact border (or on the buffer zone).
Implement a check for theses case and exlude this false positive from the reporting.