Changes between Version 70 and Version 71 of Help/Action/Upload
- Timestamp:
- 2020-03-25T16:31:56+01:00 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Help/Action/Upload
v70 v71 1 [[TranslatedPages(outdated=This page covers too much context. The concept of changeset and upload might be better placed on an own page.)]] 1 [[TranslatedPages(outdated=This page covers too much context. The concept of changeset and upload might be better placed on an own page. Screenshots are outdated and obtain sources is not explained.)]] 2 2 [[PageOutline(1-10,Table of Contents)]] 3 3 4 4 = File > Upload data = 5 5 6 [[JOSMImage(upload, middle)]]''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}**6 [[JOSMImage(upload,48,link=,middle,margin-right=20)]] ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}** 7 7 8 8 **Upload new, modified, and deleted objects in the current data layer to the server.** … … 22 22 23 23 == Changesets, upload requests, and upload strategies == 24 Geo data contributed to the OSM server consists of [Concepts/Object nodes, ways, and relations]. Because there are hundreds of mappers publishing their geo data on the OSM server it is important to track who published what data in which context. It would be tedious for mappers to describe why every single node and every single way is published. A more convenient approach is to package a group of related objects and assign the package itself a comment, instead of the individual objects. 24 Geo data contributed to the OSM server consists of [wikitr:/Help/Concepts/Object nodes, ways, and relations]. Because there are hundreds of mappers publishing their geo data on the OSM server it is important to track who published what data in which context. It would be tedious for mappers to describe why every single node and every single way is published. A more convenient approach is to package a group of related objects and assign the package itself a comment, instead of the individual objects. 25 25 26 26 The OSM project calls such a package a **[wikitr:/Help/Concepts/Changeset changeset]**. A **changeset** is a collection of related changes (new objects, object modifications, or object deletions) applied to OSM data. … … 33 33 In the most simple case there is only one upload request into a changeset: 34 34 35 [[Image(one-changeset-one-upload-request.png)]] 35 [[Image(one-changeset-one-upload-request.png,link=)]] 36 36 37 37 This is the standard configuration used by JOSM. It is the preferred configuration … … 42 42 === Multiple uploads into one changeset ===#Multipleuploadsintoonechangeset 43 43 44 [[Image(one-changeset-multiple-upload-request.png)]] 44 [[Image(one-changeset-multiple-upload-request.png,link=)]] 45 45 46 46 This is an advanced configuration option which most users don't have to enable. It can be useful: … … 50 50 JOSM still supports to upload each object individually. 51 51 52 [[Image(one-changeset-individual-object-upload-request.png)]] 52 [[Image(one-changeset-individual-object-upload-request.png,link=)]] 53 53 54 54 Please 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. … … 57 57 JOSM also supports uploading large datasets that don't fit into a single changeset. 58 58 59 [[Image(multiple-changesets.png)]] 59 [[Image(multiple-changesets.png,link=)]] 60 60 61 61 This is an advanced option which is only useful for power users. They can select this configuration if they have to upload a dataset with more than 10,000 new, modified, or deleted objects. … … 75 75 76 76 * ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}** 77 * Menu item ''File->[[JOSMImage(upload ,middle)]] Upload''78 * Toolbar button [[JOSMImage(upload ,middle)]]77 * Menu item ''File->[[JOSMImage(upload)]] Upload'' 78 * Toolbar button [[JOSMImage(upload)]] 79 79 80 80 === Checks before the Upload Dialog is displayed === … … 91 91 === The Upload Dialog ===#UploadDialog 92 92 93 [[Image(upload-dialog-screenshot.png)]] 94 95 The upload dialog consists of two sections:93 [[Image(upload-dialog-screenshot.png,link=)]] 94 95 The Upload Dialog consists of two sections: 96 96 * the upper part displays a summary of the objects to be added, to be modified, and to be deleted on the server 97 97 * the lower part provides tabs for configuring various aspects of the upload process … … 102 102 the changeset source:: 103 103 Specify the date source for the changes, to allow other contributors to check them if needed. 104 Below there is a summary of the other upload parameters for this upload. And a checkbox which sets the review_requested=yes changeset tag. 104 Below there is a summary of the other upload parameters for this upload. And a checkbox which sets the `review_requested=yes` changeset tag. 105 105 106 106 === Running a simple upload === … … 115 115 In the Upload Dialog one can enter tags in the Tag Configuration Panel, see screenshot below: 116 116 117 [[Image(tags-config-panel-screenshot.png)]] 117 [[Image(tags-config-panel-screenshot.png,link=)]] 118 118 119 119 Hashtags within the changeset comment tag are recognized and are additionally added to the hashtags changeset tag. This behavior can be disabled by setting the key `upload.changeset.hashtags` in the [wikitr:/Help/Preferences/Advanced Advanced preferences] to `false`. … … 129 129 In the Changeset Configuration Panel you can select what [wikitr:/Help/Concepts/Changeset changeset] the data is uploaded to, see the screenshot below: 130 130 131 [[Image(changeset-config-panel.png)]] 131 [[Image(changeset-config-panel.png,link=)]] 132 132 133 133 JOSM uploads to a new changeset if **Upload to a new changeset** is selected. This is the standard setting. 134 134 135 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 ,middle)]] ''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.136 137 Click on [[JOSMImage(closechangeset,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. 135 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. 136 137 Click 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. 138 138 139 139 After a successful upload JOSM can either close the changeset used or leave it open for another upload. The default setting is to close it. You can configure whether JOSM should leave it open by unselecting the checkbox **Close changeset after upload**. … … 143 143 JOSM uploads geo data with one or more **upload requests** to a [wikitr:/Help/Concepts/Changeset changeset] on the OSM server. In the Advanced Configuration Panel you can decide about the number and the size of upload requests, see screenshot: 144 144 145 [[Image(advanced-config-panel.png)]] 145 [[Image(advanced-config-panel.png,link=)]] 146 146 147 147 Select **Upload data in one request** to upload all object in one request. If you're uploading a medium to large number of objects this might take some time and JOSM will not be able to inform you about the progress. There are only two outcomes of such an upload: the upload either succeeded or it didn't. In the former case everything is fine, in the later no objects at all have been uploaded. This kind of upload will never lead to a partial upload which is both its strength and its weakness. It can be its weakness if the entire upload fails because there is a problem in the very last object in the upload request. … … 159 159 An upload is considered to be very large if its size exceeds the maximum size of a changeset on the OSM server. Currently, the upper limit for the size of a changeset is 10,000 objects and if JOSM detects that your upload is bigger it displays the following information in the Upload Dialog: 160 160 161 [[Image(large-upload-basic-settings.png)]] 161 [[Image(large-upload-basic-settings.png,link=)]] 162 162 163 163 The warning message indicates that JOSM can't upload the data unless you configure some advanced settings. Either switch to the tab **Advanced** or click on the link in the message. The following configuration panel will be displayed: 164 164 165 [[Image(large-upload-advanced-settings.png)]] 165 [[Image(large-upload-advanced-settings.png,link=)]] 166 166 167 167 For very large uploads, uploading in one request isn't possible and the respective option is therefore disabled. Please select a chunk size to be used in the upload. It has to be smaller than 10,000, too, because the upper limit for the size of a changeset also applies to the chunk size. You can upload a very large dataset with an individual request per object but you're not recommended to do so. … … 180 180 JOSM displays the following error message: 181 181 182 [[Image(error-dialog-changeset-closed.png)]] 182 [[Image(error-dialog-changeset-closed.png,link=)]] 183 183 184 184 **How to resolve** … … 192 192 If JOSM detects that a changeset became full it displays the following warning message: 193 193 194 [[Image(error-dialog-changeset-full.png)]] 194 [[Image(error-dialog-changeset-full.png,link=)]] 195 195 196 196 **How to resolve** 197 197 * Click on **Continue Uploading** to continue the upload with as many new changesets as necessary. 198 * Click on **Go back to Upload Dialog** to go back to the upload dialog. There you can select another changeset to upload the remaining objects to.198 * Click on **Go back to Upload Dialog** to go back to the Upload Dialog. There you can select another changeset to upload the remaining objects to. 199 199 * Click on **Abort** to abort uploading and return to the main map editing interface. 200 200 … … 209 209 If the OSM server detects that the node is still in use it replies an error message which JOSM displays as follows: 210 210 211 [[Image(upload-412-node-still-in-use.png)]] 211 [[Image(upload-412-node-still-in-use.png,link=)]] 212 212 213 213 If you click on **Prepare conflict resolution** JOSM supports you in resolving the issue. First it downloads all ways in which the node is still used and merges them with your current dataset. In most cases, JOSM removes the deleted node from all parent ways automatically. If for some reason this isn't possible, JOSM creates a [wikitr:/Help/Concepts/Conflict conflict] which you have to [wikitr:/Help/Concepts/Conflict resolve] manually. … … 216 216 217 217 == See also == 218 * [[JOSMImage(uploadselection ,20,middle)]] [wikitr:/Help/Action/UploadSelection Upload Selection to OSM]218 * [[JOSMImage(uploadselection)]] [wikitr:/Help/Action/UploadSelection Upload Selection to OSM] 219 219 * [wikitr:/Help/Concepts/Conflict What is a conflict?] 220 220 221 221 ---- 222 Back to [wikitr:/Help/Menu/File Menu File] [[Br]]222 Back to [wikitr:/Help/Menu/File Menu File] \\ 223 223 Back to [wikitr:/Help Main Help]
