Why is that when I try to draw up more elaborate rivers the islands seem to disappear on OGF? They show up in JOSM. Does anyone know how to get the islands to render?
OpenGeofiction
Why is that when I try to draw up more elaborate rivers the islands seem to disappear on OGF? They show up in JOSM. Does anyone know how to get the islands to render?
Log in to leave a comment
Discussion
Comment from bhj867 on 4 June 2016 at 03:27
Yes, not just that, but the entirety of INARA, and the Croxton River disappeared after I edited it last night, and I can’t fix it.
http://opengeofiction.net/#map=10/53.1558/59.2506 http://opengeofiction.net/#map=14/54.6178/71.9749
Comment from Luciano on 4 June 2016 at 06:28
As far as the problem at Beason River, Commonia, raised by user No Way…
The issue is that the islands only work if the multipolygon water relations are created and tagged correctly. Rather than try to explain in detail, note that I have just now created a pair of fully functional, correct relations for the Beason River area. My recommendation is to study them to try to be able to replicate them in other areas.
Also, the use of “natural=coastline” tags on ANYTHING “inland” (i.e. “inside” the actual coastline of a given island or continent) is VERY inadvisable, as at best it confuses the render and leads to “lost islands” and at worst creates continental floods.
Because various coastline tags were used on inland objects, the render will take a while to update - coastline renders are slow relative to other renders, and this includes coastline deletions as I have done here. But in the next few hours hopefully the result of my edits will show up.
I’ll look at Inara later, if I have a chance.
Comment from Ūdilugbulgidħū on 4 June 2016 at 16:29
As Luciano says, its not advisable to tag your inland objects (i.e. objects not directly linked to oceans) with natural=coastline. You don’t need to tag these islands with anything, in fact. The Pretanic Lake should just be a multi-polygon natural=water, water=lake, the islands should have the role ‘inner’ within this multipolygon. In theory, that should sort it. If you haven’t been able to fix it - or Luciano hasn’t - I’ll have a look late tonight.
Comment from isleño on 4 June 2016 at 16:45
In fact the Pretanic Lake (and about half a dozen of the world’s largest lakes) were deliberately tagged with natural=coastline a while back because of their enormous size — we just thought the map looked strange at low zoom levels without showing these lakes. It worked fine (until today?) but absolutely we wouldn’t want the tag used for anything smaller.
Comment from Ūdilugbulgidħū on 4 June 2016 at 20:13
I’m sure its possible to use natural=coastline for inland waterbodies - OSM does it - and it does look better at the low zooms. Its likely to be something else that’s causing the failure to render? It looks like there are a few errors in the multipolygon relations for Pretanic Lake. Firstly, there are 2 relations - one with 12 members, one with 16. The relation with 12 members is missing the outer way of the Lake as one of its members. The relation with 16 members has the shoreline of the lake triplicated. Removing those triplicates and deleting the other relation might sort out this problem.
Comment from Luciano on 4 June 2016 at 23:01
The use of natural=coastline for inland lakes and seas in OSM is deprecated. This means that although you can find many noticeable examples of it (including North America’s great lakes and the Caspian Sea, among many others), in theory it will not always be supported. The existence of these examples can be attributed to the consequences of evolution of the standard over time, where the current multipolygon solution took time to take shape.
As isleño said, the experiment was tried of tagging some major inland bodies of water with natural=coastline mostly due to the desire to see the lakes render at low zooms. Personally, I’d prefer to just wait for the standard layer render to catch up to the current tagging best practice, but I understand the impulse to “tag for the renderer” - I’m guilty of it many times over.
However, when problems arise (as in Inara), my first and formost recommendation would be to get rid of the coastline tags, and get the multipolygon working correctly. Once you have a nice, well-behaved lake in the multipolygon style, you can go back later and re-add the coastline if you’re wanting to support the render at low zooms.
Comment from bhj867 on 5 June 2016 at 00:57
Great tips guys. I will check it out and try to remove some of those triplicates. I’m not exactly sure how that happened, but I am sure it happened around the same time All of my other roads and highways double rendered. I removed several spot in the center of Pretany that were rendered twice. One highway over the other, one forest over the other.
Comment from Luciano on 5 June 2016 at 01:11
@bhj867 - I have had this “doubling” problem too. It seems to arise in the context of my efforts to keep an “offline copy” of my current working area for JOSM. Somehow, it seems that JOSM occasionally forgets what it’s already uploaded/download, and ends up uploading the same things more than once. My way of avoiding this problem is to never save “working areas” over more than single edit sessions. The drawback, of course, is that each time I start a new edit session, I have to re-download my working area (or do an extract on the backup, if I’m confident there has been no work in the area since the last backup). Fortunately most of the time I have very fast broadband and the tubes connecting to Europe are wide.
Comment from bhj867 on 5 June 2016 at 02:08
The problem is fixed. Thank you so much for the advice. I was really lost there for a second.