Nadere info (staat in het issue):
[quote] We don’t save surface information over the ways yet. So the first step would be to get additional way attributes into this way table. I don’t remember the details right now but I think that requires a custom derived class instead of RelationWayTable. It might be a good idea to be future proof here and simple keep a full copy of the tags jsonb with each way.
The only time we look at the relation members is when creating the geometry. So this is probably the best place to also compute the surface information. I was considering if we simple should create a full geojson and save that in a jsonb or text column instead of using a GEOMETRY. This would meant we could add properties to geometry segments. This would also be useful for properties like “oneway”. [/quote]
Mij zegt het weinig… ik snap dat je de informatie binnen moet halen en pre-processen voordat het getoond kan worden, maar de uitwerking daarvan, dat gaat mij boven de pet.
