Changes between Version 42 and Version 43 of Help/Action/Upload
- Timestamp:
- 2014-10-23T20:48:57+02:00 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Help/Action/Upload
v42 v43 1 1 [[TranslatedPages]] 2 [[PageOutline(1-10,Table of Contents)]] 2 3 3 4 = File > Upload to OSM = 4 5 5 [[Image(source:trunk/images/upload.png)]] ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}** 6 [[Image(source:trunk/images/upload.png,middle)]] ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}** 6 7 7 8 **Upload new, modified, and deleted objects in the current data layer to the server.** 8 9 9 Geo data edited in JOSM is only available locally and only usable by the user who entered the data unless the user decides to make it available to the community too. In order to publish data the user has to **upload** it. Uploading means that the geo data is transferred to a central server run by the OSM community where it is integrated with geo data from other mappers in a central database. It's by uploading data that locally edited geo data both becomes part of the [ http://www.openstreetmap.orgpublic maps] and can be used by other members of the OSM community.10 Geo data edited in JOSM is only available locally and only usable by the user who entered the data unless the user decides to make it available to the community too. In order to publish data the user has to **upload** it. Uploading means that the geo data is transferred to a central server run by the OSM community where it is integrated with geo data from other mappers in a central database. It's by uploading data that locally edited geo data both becomes part of the [osmwww: public maps] and can be used by other members of the OSM community. 10 11 11 12 {{{ … … 16 17 }}} 17 18 18 [[TOC(inline)]]19 20 19 == Changesets, upload requests, and upload strategies == 21 20 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. … … 25 24 Changesets are different from **upload requests**. A changeset is a **logical** grouping of [Concepts/Object objects], whereas an upload request is a **technical grouping** for transferring geo data to the central OSM server only. In JOSM we say, that objects are uploaded **using** upload requests **to** a changeset. The JOSM Upload Dialog allows aspects of the upload requests and changeset objects to be configured. Some of the settings are compulsory (i.e. the user has to configure them before geo data can be uploaded) but most of them are optional and JOSM works with reasonable default values. 26 25 27 Geo data can be retrieved later via the changeset it was uploaded to, though it can't be retrieved by the upload request used. Changesets have a unique identifier, upload requests have not. For instance, [ http://www.openstreetmap.org/browse/changeset/3274448 this changeset] includes geo data from tracing over orthofotos of the city of Bern, Switzerland. It isn't possible, though, to see the upload requests that were used to fill it.26 Geo data can be retrieved later via the changeset it was uploaded to, though it can't be retrieved by the upload request used. Changesets have a unique identifier, upload requests have not. For instance, [osmwww:browse/changeset/3274448 this changeset] includes geo data from tracing over orthofotos of the city of Bern, Switzerland. It isn't possible, though, to see the upload requests that were used to fill it. 28 27 29 28 === One upload request into one changeset === … … 33 32 34 33 This is the standard configuration used by JOSM. It is the preferred configuration 35 36 37 34 * for users uploading the result of converting a few GPS traces to OSM geo data 35 * for users uploading the result of tracing a few hours over aerial photos 36 * for users uploading the result of entering local knowledge about street names, points of interests, etc. 38 37 39 38 === Multiple uploads into one changeset === … … 42 41 43 42 This is an advanced configuration option which most users don't have to enable. It can be useful: 44 45 43 * for users who map using multiple data layer in JOSM and who want to upload the result of their work into one changeset 44 * 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. 46 45 47 46 JOSM still supports to upload each object individually. … … 63 62 Here are some rules of thumb: 64 63 65 66 67 64 * **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. 65 66 * **Collisions with other mappers**: if you upload 30,000 objects in one request and if the server encounters a problem on the 29,999th object the whole upload is rolled back. The problem has to be fixed first (i.e. by resolving a [wiki:/Help/Concepts/Conflict conflict]). The whole 30,000 objects will then have to be uploaded again. On the other hand, if you upload 30,000 objects with 10 requests containing 1,000 objects each and the server encounters a problem on the 29,999th object then you only have to repeat the last upload request for the 29,000th to 30,000th objects. Objects 1-28,999 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. 68 67 69 68 == Uploading data == … … 71 70 === Launching the Upload Dialog ===#LaunchUploadDialog 72 71 73 74 75 72 * ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}** 73 * Menu item ''File->[[Image(source:trunk/images/upload.png,middle)]] Upload'' 74 * Toolbar button [[Image(source:trunk/images/upload.png,middle)]] 76 75 77 76 === Checks before the Upload Dialog is displayed === … … 79 78 80 79 JOSM also checks for limitations imposed by the OSM server: 81 82 80 * tag names and tag values must be shorter than 255 characters 81 * ways can't consist of too many nodes 83 82 84 83 If the objects you're uploading have cyclic dependencies (relation 1 refers to relation 2, relation 2 refers to relation 3, relation 3 refers to relation 1) JOSM can't upload them. JOSM will ask you to break up these dependencies first. … … 91 90 92 91 The upload dialog consists of two sections: 93 94 92 * the upper half displays a summary of the objects to be added, to be modified, and to be deleted on the server 93 * the lower part provides panels for configuring various aspects of the upload process 95 94 96 95 When the Upload Dialog is launched it always displays the basic configuration panel which includes a text box for entering an upload comment and a summary of the other upload parameters for this upload. … … 98 97 === Running a simple upload === 99 98 100 101 2. Enter an upload comment. You **must** provide an upload comment of at least 3 characters.102 3. Click on [[Image(source:trunk/images/upload.png,16)]] **Upload Changes**99 1. [#LaunchUploadDialog Launch] the Upload Dialog 100 1. Enter an upload comment. You **must** provide an upload comment of at least 3 characters. 101 1. Click on [[Image(source:trunk/images/upload.png,middle)]] **Upload Changes** 103 102 104 103 === Running an upload with advanced options === … … 112 111 113 112 **Do's and Don'ts** 114 115 116 113 * Tags are your friends. Use them to describe the geo data you are uploading to the OSM server. 114 * Use the tag {{{source}}} to describe the source of your geo data (examples: {{{traced from Yahoo Imagery}}}, {{{based on GPS traces and surveyed by bike}}}). 115 * You don't have to add your user name to the tags. The link between the changeset and your OSM user account is maintained automatically. 117 116 118 117 Note that the required upload comment is also a tag. You can either enter it in the Tag Configuration Panel with the key {{{comment}}} or in the Basic Settings Panel in the text input field provided there. … … 125 124 JOSM uploads to a new changeset if **Upload to a new changeset** is selected. This is the standard setting. 126 125 127 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 [[Image(source:trunk/images/dialogs/refresh.png)]] ''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. 128 129 Click on [[Image(source:trunk/images/closechangeset.png)]] **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. 126 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 [[Image(source:trunk/images/dialogs/refresh.png,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. 127 128 Click on [[Image(source:trunk/images/closechangeset.png,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. 130 129 131 130 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**. … … 144 143 145 144 **Recommendations** 146 147 148 145 * For small (<1,000 objects) to medium upload sizes (<5,000 objects), choose **Upload data in one request** 146 * For medium to large upload sizes (> 5,000 objects) choose **Upload data in chunks of objects**. A chunk size of 1,000 is a good value to start with. 147 * Don't use **Upload each object individually** unless you have a specific reason to do so. This is basically a legacy strategy from former versions of the OSM server. 149 148 150 149 === Running a very large upload === … … 161 160 A very large upload doesn't fit within a single changeset. Please select 162 161 163 164 165 162 * whether JOSM should automatically open as many new changesets as required to upload the data. Select this option if you want to run a very large upload without user intervention. 163 164 * whether JOSM should fill up one changeset and return to the Upload Dialog. Select this option if you want to have full control over the changesets created for the upload. 166 165 167 166 == Error and Warning messages == … … 175 174 176 175 **How to resolve** 177 178 179 176 * Launch the Upload Dialog again 177 * Select another open changeset or select to upload to a new changeset 178 * Upload again 180 179 181 180 === Changeset becomes full during upload ===#ChangesetFull … … 187 186 188 187 **How to resolve** 189 190 191 188 * Click on **Continue Uploading** to continue the upload with as many new changesets as necessary. 189 * 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. 190 * Click on **Abort** to abort uploading and return to the main map editing interface. 192 191 193 192 … … 208 207 209 208 == See also == 210 211 209 * [[Image(source:trunk/images/uploadselection.png,20,middle)]] [Action/UploadSelection Upload Selection to OSM] 210 * [Concepts/Conflict What is a conflict?] 212 211 213 212 ----
