Are there safeguards in place to prevent innundations? I am wondering if coastline modifications should be moderated to prevent this.
OpenGeofiction
Are there safeguards in place to prevent innundations? I am wondering if coastline modifications should be moderated to prevent this.
Log in to leave a comment
Discussion
Comment from Luciano on 16 April 2015 at 03:29
The Uletha coastline relation (relation id = 10071) is badly broken … does no one else know how to maintain this? It had been retagged (as a country called “Hav”), making it hard to identify, and has major discontinuities. I guess I’m the only person trying to maintain this.
The coastline relation is NOT necessary for coastline integrity… however, I have found it to be almost indispensible for easily and correctly fixing mistakes, when they occur.
I don’t think there is any way to “lock down” coastline edits. We have to count on the goodwill of users showing intent to improve their mapping abilities, with appropriate messages to those who are repeat violators.
Everyone makes mistakes starting out… and one or two mistakes are forgivable - I made a few floods myself starting out. However, people should show some will toward improving their ability and understanding the principles.
There is a write-up on coastline maintenance here. It should be required reading…
Comment from emkfra on 16 April 2015 at 14:24
Yes that was me sorry, ill try to make sure it won’t happen again
Comment from Easky30 on 16 April 2015 at 20:36
I need to find a few quiet hours and really study the the process of fixing the coastlines & boundary relationships.
I feel bad coming on OGF for an hour a day and not really making contributions to it’s maintenance. Thank you to whoever put Orinoco in the Area Table.
Comment from histor on 16 April 2015 at 21:09
O.k. - it is not easy with the coastline. But there are some clear rules:
No gap is allowed. The coastline always must be a closed way - may be around a great continent or an small island.
The way arond an continent can be very long. A way can have only 2000 nodes / knots. If your editor means, now this coastline-way has more, make two pieces of it with the scissor-tool. Then around this continent run two or more ways like a chain - always the last node of one way must be the first node of the next way. That is o.k.
The coastline must be only ONE line - no branches! Never let the coastline cross itself.
Every way has a direction. The direction is this direction, a way is drawn - from node # 1 via node # 2 to node # 3 and so on. Not only streets - the coastline-way too is saved so. Seen in the direction of the coastline-way water is right and land is left. Therefore an island is to draw counterclockwise.
Please have in mind, that the update of the changed coastline is not every 5 minutes as the other items, but only every four hours.
Comment from histor on 16 April 2015 at 23:02
O.k. - the 24:00 h flood. Uletha must be o.k. (coastline crosses itself), Antarephia I hope (way in wrong direction (?)
Comment from indyroads on 16 April 2015 at 23:17
It seems that all the time it’s the continent of Uletha they always gets flooded… it seems like there’s a problem right now with all of the different sections of coastline since it’s one of the largest continents and it’s difficult to keep track. I propose that the coastline relation be renamed Ultra coast. Maybe the coastline can be divided between 4 or 5 of us to police errors. Also I propose that country boundaries be moved to maritime boundaries like in many countries.
Comment from BelpheniaProject on 16 April 2015 at 23:23
@indyroads It’s flooded again for the second time…
Comment from tom_m7 on 17 April 2015 at 01:02
Click here to visit the coastline info page, which highlights coastline nodes that can potentially cause rendering problems, and click here to see Thilo’s diary entry about fixing coastlines. These two links will help in fixing “floods”.
Comment from histor on 17 April 2015 at 01:06
It is clear, that Uletha is more often under water as other continents. But for this time (tonight 24:00 middle european summer time) the reason was clear = selfcrossing of coastline. In one hour after next update it shall be o.k.
Indeed I think, that the coastline and the boundary should not be one way. So maritime boundaries is the better way. And more care, if complicated harbour-lines are drawn.
Direct to the coastline-way belongs only [natural = beach] and [natural = mud] for tidal-land. All other things can have an extra way some “meters” (or “feet”) away from the coastline as buildings, wood, park, meadow and so on. To draw a road at the same way as the coastline is idiotic.
Comment from Luciano on 17 April 2015 at 01:13
There is a good technical reason to keep the coastline relation as a SINGLE relation - in the JOSM editor it can tell you if the entire coastline relation is properly “closed” - if you change it to multiple relations, then you lose that functionality, which is one of the things that makes having a coastline relation useful. In fact, without that functionality, it doesn’t seem that useful at all except as a way to categorize the ways, which can be more easily be done with a tag on the ways, i.e. what is already there: source=”TS-Coastline-…”