To speak to Malcolm's point, there is a "default" rendering strategy for
unknown bridge tags. Unfortunately, because there's an ill-defined group of
values used to indicate that a bridge is closed, damaged, gone, etc., the
default rendering is not to render an undefined "bridge" value as a bridge.
On Mon, May 13, 2013 at 7:58 AM, Steve Bennett wrote:
> On Fri, May 10, 2013 at 8:24 PM, Richard Fairhurst
> wrote:
>
> > So for the tiny number of renderers/routers which want to show bridge
> types
> > differently - and my canal renderer will be one of them! -
> differentiating
> > based on a
On Wed, May 8, 2013 at 5:39 PM, Martin Koppenhoefer
wrote:
>
> I think we could also keep typology in bridge=* like we do for buildings,
> but if there was a majority for bridge:type I had no problem either.
>
>
>From comments so far, I think I'm happy to go with this for simplicity.
[...snipped.
