Jochen Topf
Jochen Topf
@pnorman That's why I restarted this effort in the way I did. The move to flex is needed independently of any change in layout. What I am proposing here basically...
@woodpeck Your issue.
This issue was about the "water_lines" layer (and, in extension, the "water_lines_label" layer). I don't see that "avalanch_protector" fits in here. Of course we can generalize to the "street*" layers,...
We also need `weir` and `lock_gate` as polygons because they are used in the `water-barriers-poly` layer.
@mboeringa Good point. I checked the cases where this would make a difference, ie. non-closed ways tagged as `area=yes` and closed ways tagged as `area=no`. For `waterway=dam` there are 247...
See also https://postgis.net/docs/ST_QuantizeCoordinates.html
We should split the multipolygons first for the creation of expire tiles. But the current code is somewhat complex and doesn't allow that easily and we need to deal with...
As author of the flex backend code I welcome everybody who wants to try it out. Just be aware that it is still marked experimental and is not in a...
I am restarting this effort to switch to osm2pgsql flex. It is sufficiently different from what was discussed in this issue that I created a new isse, see #4977 for...
I could never understand why there are the `create`, `modify`, and `delete` actions in the osmChange format, or why there is an osmChange format at all. Why not use the...