For some locations, the OSM preprocessor is (correctly) outputting a large number of unlabelled segments like "footpath". Although technically correct, these make the renderings extremely long, and with the current handler, are not very useful. We should be filtering some of this out in the current handler so that it is tractable in terms of making a useful rendering.
@samueljohnsegun148 Note that this content should not be filtered out of the preprocessor entirely, since it is conceivable that another renderer might find a use for it.
@JRegimbal when filtering, suggest making the code easily usable by other handlers that may want the same thing. (for now, just copied/pasted, but potentially in the future could be moved to an additional preprocessor that tags the output in some way so that this type of content is more easily filtered, if we come up with such use cases in the future).
For some locations, the OSM preprocessor is (correctly) outputting a large number of unlabelled segments like "footpath". Although technically correct, these make the renderings extremely long, and with the current handler, are not very useful. We should be filtering some of this out in the current handler so that it is tractable in terms of making a useful rendering.
@samueljohnsegun148 Note that this content should not be filtered out of the preprocessor entirely, since it is conceivable that another renderer might find a use for it.
@JRegimbal when filtering, suggest making the code easily usable by other handlers that may want the same thing. (for now, just copied/pasted, but potentially in the future could be moved to an additional preprocessor that tags the output in some way so that this type of content is more easily filtered, if we come up with such use cases in the future).