| 96 | | * the upper part displays a summary of the objects to be added, to be modified, and to be deleted on the server |
| 97 | | * the lower part provides tabs for configuring various aspects of the upload process |
| 98 | | |
| 99 | | When the Upload Dialog is launched it always displays the Settings tab which allows you to enter the most important information about your [wikitr:/Help/Concepts/Changeset changeset]: |
| | 99 | * the left side displays a summary of the objects to be added, to be modified, and to be deleted on the server |
| | 100 | * the right side provides tabs for configuring various aspects of the upload process |
| | 101 | |
| | 102 | When 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]: |
| 119 | | === Running an upload with advanced options ===#AdvancedOptions |
| | 122 | === Running an upload with advanced options (Settings tab) ===#AdvancedOptions |
| | 123 | |
| | 124 | ==== Choosing the changeset to upload to ==== |
| | 125 | In the Changeset Configuration Panel you can select what [wikitr:/Help/Concepts/Changeset changeset] the data is uploaded to, see the screenshot below: |
| | 126 | |
| | 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. |
| | 132 | |
| | 133 | 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. |
| | 134 | |
| | 135 | 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**. |
| | 136 | |
| | 137 | ==== Configuring the number and size of upload requests ==== |
| | 138 | 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: |
| | 139 | |
| | 140 | [[Image(advanced-config-panel.png,link=)]] |
| | 141 | |
| | 142 | 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. |
| | 143 | |
| | 144 | Select **Upload data in chunks of objects** to upload the objects in a sequence of requests with a predefined size. You can enter a preferred size for an upload request (called the "chunk size"). Depending on its value JOSM will submit a number of upload requests (the number is displayed on the right of the input field for the "chunk size"). In contrast to the former option, every upload of a chunk can either succeed or fail. You will get some coarse grained progress feedback because JOSM will inform you when an individual chunk has been uploaded successfully or when its upload has failed. Uploading in chunks is in most cases slower than uploading in one requests, though. |
| | 145 | |
| | 146 | Select **Upload each object individually** to upload each object with an individual upload request. You will get very fine grained progress feedback because JOSM will inform you when an individual object was uploaded successfully or when its upload has failed. Note that this option is in most cases the slowest option. |
| | 147 | |
| | 148 | **Recommendations** |
| | 149 | * For small (<1,000 objects) to medium upload sizes (<5,000 objects), choose **Upload data in one request** |
| | 150 | * 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. |
| | 151 | * 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. |
| 137 | | ==== Choosing the changeset to upload to ==== |
| 138 | | In the Changeset Configuration Panel you can select what [wikitr:/Help/Concepts/Changeset changeset] the data is uploaded to, see the screenshot below: |
| 139 | | |
| 140 | | [[Image(changeset-config-panel.png,link=)]] |
| 141 | | |
| 142 | | JOSM uploads to a new changeset if **Upload to a new changeset** is selected. This is the standard setting. |
| 143 | | |
| 144 | | 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. |
| 145 | | |
| 146 | | 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. |
| 147 | | |
| 148 | | 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**. |
| 149 | | |
| 150 | | |
| 151 | | ==== Configuring the number and size of upload requests ==== |
| 152 | | 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: |
| 153 | | |
| 154 | | [[Image(advanced-config-panel.png,link=)]] |
| 155 | | |
| 156 | | 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. |
| 157 | | |
| 158 | | Select **Upload data in chunks of objects** to upload the objects in a sequence of requests with a predefined size. You can enter a preferred size for an upload request (called the "chunk size"). Depending on its value JOSM will submit a number of upload requests (the number is displayed on the right of the input field for the "chunk size"). In contrast to the former option, every upload of a chunk can either succeed or fail. You will get some coarse grained progress feedback because JOSM will inform you when an individual chunk has been uploaded successfully or when its upload has failed. Uploading in chunks is in most cases slower than uploading in one requests, though. |
| 159 | | |
| 160 | | Select **Upload each object individually** to upload each object with an individual upload request. You will get very fine grained progress feedback because JOSM will inform you when an individual object was uploaded successfully or when its upload has failed. Note that this option is in most cases the slowest option. |
| 161 | | |
| 162 | | **Recommendations** |
| 163 | | * For small (<1,000 objects) to medium upload sizes (<5,000 objects), choose **Upload data in one request** |
| 164 | | * 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. |
| 165 | | * 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. |
| 166 | | |
