OpenGeofiction

Failure uploading to OGF

Posted by Rhiney boi on 15 June 2019 in English (English)

Full text:

"

Uploading to the server failed because your current dataset violates a precondition. The error message is: ResponseCode=412, Error Header=<Precondition failed: Relation with id 80936 cannot be saved due to Way with id 9828077

"

After searching the OGF-data, I found that:

1.Relation 80936 is the FSA Land Area (which was changed in my dataset by splitting a way) 2.Way 9828077 was a coastline way in Arghenna.

Any help here?

Comment from Fluffr_Nuttr on 15 June 2019 at 23:35

I did have a JOSM conflict a few days ago involving the AR-120 relation, so it most likely has to do with that. I believe I just copied over my changes and uploaded. These changes did involve me splitting coastlines. I didn't download anything involved in Teenesccan, so I'm not sure how a conflict would emerge between our edits. Did you happen to download an area involving parts of Arghenna, Penquisset or Whitestone?

I'm sorry if I somehow screwed up your edits. The only thing I can recommend is just trying again.

Hide this comment

Comment from Rhiney boi on 15 June 2019 at 23:46

Uh, I have only downloaded Teenesccan and parts of Stanton, which I believe did not have Penquisset's coast in it.

I'll just do it again.

Hide this comment

Comment from Fluffr_Nuttr on 15 June 2019 at 23:58

P.S. Actually, you can probably fix this. Doing some research on error code 412, this is definitely a conflict problem. I'm still not sure how Arghenna is involved in this, since I haven't even uploaded today. On the right of the JOSM screen, there's a button to resolve any conflicts. You can get some help on the dialog screen here. Safest bet is just copying over all of your nodes to the merged version.

Hopefully this helps.

Hide this comment

Comment from Rhiney boi on 16 June 2019 at 00:01

Yesterday there were 4 conflicts, but I had resolved them. Something had happened to my PC overnight shutting down everything I had opened, so I'll just do it again.

Hide this comment

Comment from Fluffr_Nuttr on 16 June 2019 at 00:27

Yeah, that works.

Hide this comment

Comment from wangi on 16 June 2019 at 23:49

"Safest bet is just copying over all of your nodes to the merged version"

Please don't. Really, please don't.

Relations are complex, if your editor is telling you there is a conflict it is because it needs human thought to work out the version to keep. If it was easy, then the software would have done it.

I've just spent a bunch of time fixing the AR120 land area relation.

Best practice: always make sure you are editing within the area you have downloaded. Conflicts are ripe when you edit outside it. For relations always "download incomplete members". Consider conflicts, don't blindly accept yours or theirs. Separate your edits: do boundary & coastline edits in as small as batch as you can in order to reduce the opportunity for conflicts.

Hide this comment

Comment from Rhiney boi on 17 June 2019 at 00:12

Agreed.

Nothing is worse than finding out your coastline revisions were deleted because somebody overwritten your ways. Luckily, that hasn't happened to me (knocks on wood).

Hide this comment

Leave a comment

Parsed with Markdown

  • Headings

    # Heading
    ## Subheading

  • Unordered list

    * First item
    * Second item

  • Ordered list

    1. First item
    2. Second item

  • Link

    [Text](URL)
  • Image

    ![Alt text](URL)

Login to leave a comment