Coastline relation without type error

Posted by dsaneus on 24 January 2016 in English.

Hi everyone, I was about to upload some changes I had made in Saneus when I got an error saying relation without type, referring to Archanta coastline relation. I didn’t want to upload the changes in case I flooded the continent.

I was creating a beach using the existing coastline and a road.

When I started editing this morning, I downloaded an area of the map. Later on, I needed to download another part which coincided with the one I had already downloaded. Could this be the cause? Some sort of duplication?

This is what I was trying to do: JOSM

And these are the errors: Errors

Anyone can help with the error? I don’t want to lose the changes I’ve done. If you need the .osm file I can provide it to you.

Thanks!

Location: AR058a

Discussion

Comment from _zM on 24 January 2016 at 11:31

Side note: DO NOT CONNECT BEACHES OR OTHER SUCH AREAS TO ANYTHING THAT DOES NOT DEFINE THEM. You will have a problem if you try to change the shape of the beach.

Comment from Luciano on 24 January 2016 at 11:59

The coastline relations is non-standard, with respect to the OSM documentation. As such, it is set up in a way that JOSM doesn’t really like. It’s odd, though - when I use JOSM, I get “relation has no type” as a WARNING, rather than as an ERROR. And the WARNING can be safely ignored.

What version of JOSM are you using? Perhaps there is a setting that you have made that makes the error-checking more “strict”?

Anyway, these coastline relations are NOT part of the OSM standard. They’re useful because we’re in a world where there is a lot of high-level editing (large areas) by inexperienced users, and we don’t have the same “live” API’s that OSM has, so it helps us to find errors in the coastline.

Since the coastline relation is non-standard, we have been setting it to “ogf:type=multipolygon” instead of “type=multipolygon”. This prevents excessive trigger conditions for automated jobs that run on the server, but yes, technically it is an error. You can safely ignore it. I don’t know why your JOSM is telling you it’s and error, when my JOSM tells me it’s a warning.

Your duplication problem is something else. It seems to arise sometimes when people try to “save” an edit area for repeated edit sessions. JOSM doens’t always manage this well. I always download a “fresh” snapshot for each edit session, even though it is sometimes slow, because of this issue.

@_zM, I’m not sure what you mean… I connect my beaches to the coastline, always - as relations, however, not as duplicate ways. It seems to me a beach is defined by the coastline.

Comment from _zM on 24 January 2016 at 12:09

@Luciano: I meant the street.

Comment from dsaneus on 24 January 2016 at 12:17

Thanks for your answer Luciano! I’m so relieved now! I thought I would have redo everything I’d done. I am using version 9329. I have no clue what the problem might be with the warning messages. I haven’t changed anything in the validation settings. Perhaps it’s just a bug, who knows. Thanks again!

@_zM, I see what you mean, I’ll take it into account! Thanks!

Comment from Luciano on 24 January 2016 at 12:39

@_zM OK sorry - I wasn’t even looking at that. Sorry to misunderstand.

Leave a comment

Log in to leave a comment