mboeringa

> Single line tagging provides asymmetric rendering of symmetric feature, suggesting it is narrow, like a path or edge. **Dual line mapping of top of the dyke results in ,,messy''...

> So as a mapper: If you want to map a dyke then map the dyke in the form you find best to represent the observable geographic reality. **** So...

> I believe you've misunderstood Christoph's comment. I think he is saying that he would like mappers to draw dykes (or Levees, or embankments) in a way that represents their...

> @mboeringa, isn't a dyke essentially an embankment? So, replacing the dyke tag with embankments isn't technically wrong is it? Yes, and I am actually fine with the current practice...

> * developing a consensus strategy on administrative boundary rendering. Background is that we currently render administrative boundaries from the _polygons as linestrings_ representation in the `planet_osm_roads` table. https://github.com/gravitystorm/openstreetmap-carto/pull/4431 **demonstrated...

I think this whole issue is superseded by @pnorman's work on the [new flex style](https://github.com/gravitystorm/openstreetmap-carto/pull/4431), that includes a new de-duplicated 'planet_osm_admin' table (created and updated at the osm2pgsql import stage),...

> To give a few concerns, mostly because I haven't studied the solution well, and don't know how clean the data is: Can #4431 handle it when two borders have...

> @pnorman #4431 might also fix this, but would this PR make sense in the meantime? I have been using my own variant of Paul's work in #4431 for quite...