Changes between Version 74 and Version 78 of Help/Action/Upload


Ignore:
Timestamp:
(multiple changes)
Author:
(multiple changes)
Comment:
(multiple changes)

Legend:

Unmodified
Added
Removed
Modified

  • Help/Action/Upload

    v74 v78  
    1212
    1313== In simple words ==
    14 * (like online editors like iD or Potlatch) you need to upload your changes to OSM server. Make sure you connected to server :-)
     14* (like online editors like iD or Potlatch) you need to upload your changes to OSM server. Make sure you're connected to the server! :-)
    1515* you may encounter [wikitr:/Help/Concepts/Conflict conflicts] after you upload changes (in most cases this means you will have to [wikitr:/Help/Dialog/Conflict#Resolvingdifferencesbetweentags choose what tags to leave on your objects])
    16 * to reduce chance of conflict:
     16* to reduce the chance of conflict:
    1717 * don't edit data other mappers edit in same time window
    1818 * make your downloads-uploads quicker, so there no overlap between your time-window and theirs
    19 * (rough idea) to entirely avoid conflict, don't edit objects with same id and don't alter their parent relations (node-way and way-relation and relation-relation). If you (and other editor) are editing disjoint datasets (https://en.wikipedia.org/wiki/Disjoint_sets), then there won't be conflict at all. Please note that it also means that all parent ways and all parent relations should be respected (which is likely to change).
     19* (rough idea) to avoid conflicts entirely, don't edit objects with the same ID and don't alter their parent relations (node-way and way-relation and relation-relation). If you (and other editors) are editing disjoint datasets (https://en.wikipedia.org/wiki/Disjoint_sets), then there won't be a conflict at all. Please note that it also means that all parent ways and all parent relations should be respected (which is likely to change).
    2020* (unlike online editors like iD or Potlatch) you don't have to upload immediately (you may [wikitr:/Help/Action/Save save] file manually but [wikitr:/Help/Action/AutoSave auto save] will further assist you)
    2121* (unlike every other editor?) JOSM will let you upload changes to already opened (but not a closed) changeset (see [#Multipleuploadsintoonechangeset Multiple uploads into one changeset]). Every open changeset will "close" automatically by [osmwww: OSM server] after 1 hour.
    … …  
    4848* for users who are working in longer mapping session. For them it could be safer to upload intermediate results to the server than to upload the result of the complete session only. In the former case they can use multiple uploads into one changeset which helps them to safe their data without fragmenting them up in unrelated changesets.
    4949
    50 JOSM still supports to upload each object individually.
     50JOSM still supports the option to upload each object individually.
    5151
    5252[[Image(one-changeset-individual-object-upload-request.png,link=)]]
    … …  
    5454Please note that this is a legacy feature. Until recently, this was the only upload option in OSM.  Technically, it uses a slightly different approach to communicate with the OSM server. It is still available in JOSM although the OSM server now supports upload requests with up to 10,000 objects. For the casual and normal user it is almost obsolete. In rare cases, it could be useful for power users.
    5555
    56 === Uploading large datasets into multiple changeset ===
     56=== Uploading large datasets into multiple changesets ===
    5757JOSM also supports uploading large datasets that don't fit into a single changeset.
    5858
    … …  
    6767Here are some rules of thumb:
    6868
    69 * **Time required to upload**: the smaller the upload requests you choose the longer it takes to upload. It takes more time to upload 100 objects using 100 individual upload requests than to upload them in one request containing 100 objects.
    70 
    71 * **Collisions with other mappers**: if you upload 10,000 objects in one request and if the server encounters a problem on the 9,999th object the whole upload is rolled back. The problem has to be fixed first (i.e. by resolving a [wikitr:/Help/Concepts/Conflict conflict]). The whole 10,000 objects will then have to be uploaded again. On the other hand, if you upload 10,000 objects with 10 requests containing 1,000 objects each and the server encounters a problem on the 9,999th object then you only have to repeat the last upload request for the 9,001th to 10,000th objects. Objects 1-9,000 are already successfully uploaded. If you're mapping in areas where other mappers are active too you should therefore prefer smaller sizes for upload requests. 
     69* **Time required to upload**: the smaller the upload requests you choose, the longer it takes to upload. It takes more time to upload 100 objects using 100 individual upload requests than to upload them in one request containing 100 objects.
     70
     71* **Collisions with other mappers**: if you upload 10,000 objects in one request and the server encounters a problem on the 9,999th object, the whole upload is rolled back. The problem has to be fixed first (i.e. by resolving a [wikitr:/Help/Concepts/Conflict conflict]). The whole 10,000-object upload will then have to be uploaded again. On the other hand, if you upload 10,000 objects with 10 requests containing 1,000 objects each and the server encounters a problem on the 9,999th object then you only have to repeat the last upload request for the 9,001th to 10,000th objects. Objects 1-9,000 are already successfully uploaded. If you're mapping in areas where other mappers are active too you should therefore prefer smaller sizes for upload requests.
    7272
    7373
    … …  
    101101
    102102When the Upload Dialog is launched it always displays the ''Description''  tab which allows you to enter the most important information about your [wikitr:/Help/Concepts/Changeset changeset]:
    103  the changeset comment::
     103 The changeset comment::
    104104  It's important to provide a brief comment describing the changes you are uploading. This makes it easier for other contributors and for yourself to know what your changes are about and why you made the changes.
    105105  * if the comment is empty or too short: the text below the comment box warns you
    … …  
    107107  * if the comment is provided: the text below the comment thanks you
    108108[[Image(comment_present.png,link=)]]
    109  the changeset source::
     109 The changeset source::
    110110  Specify the date source for the changes, to allow other contributors to check them if needed.
    111111  * if the data source is not specified: the text below the comment box warns you
    … …  
    125125In the Changeset Configuration Panel you can select what [wikitr:/Help/Concepts/Changeset changeset] the data is uploaded to, see the screenshot below:
    126126
    127 [[Image(changeset-config-panel.png,link=)]]
    128 
    129 JOSM uploads to a new changeset if **Upload to a new changeset** is selected. This is the standard setting.
    130 
    131 If you want to upload to an existing changeset you have to select one of the available changesets from the drop down list. This list is only enabled if there are open changesets which you can upload data to because you own them. Click on [[JOSMImage(dialogs/refresh)]] ''Refresh'' to load the list of available open changesets from the server. If there is at least one open changeset available you can select the radio button **Upload to an existing changeset** and select a changeset.
     127[[Image(changeset-config-panel-1_JOSMr18303.png,link=)]]
     128
     129To upload your data, you can choose from the drop down list ''(since r18283)'':
     130* JOSM uploads to a new changeset if [[JOSMImage(dialogs/changesetdialog,24,link=,bottom)]] **New changeset** is selected in the drop down list. This is the standard setting.
     131* If you want to upload to an existing changeset you have to select one of the available changesets from the drop down list (they are only available, in the list, if there are open changesets which you can upload data because you own them). Click on [[JOSMImage(dialogs/refresh)]] ''Refresh'' to load the list of available open changesets from the server.
    132132
    133133Click on [[JOSMImage(closechangeset,24,link=,bottom)]] **Close Changeset** to close the currently selected open changeset. This is for convenience only. You don't have to close a changeset here in order to run a successful upload.
    … …  
    231231[[Image(error-dialog-large-bounding-box.png,link=)]]
    232232
     233**Note**: The size of the bounding box which is considered as very large can be set in advanced preferences (`upload.max-area` (default is `3.0`)).
    233234
    234235== See also ==