Changes between Version 24 and Version 25 of Help/Action/Upload

Timestamp:

2009-12-09T16:43:48+01:00 (16 years ago)

Author:

Gubaer

Comment:

extended

Help/Action/Upload

@@ -154 +154 @@
  * 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. 
 
+=== Running a very large upload === 
+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 50'000 objects and if JOSM detectes that your upload is bigger it displays the following information in the Upload Dialog: 
 
-=== Running a very large upload === 
+[[Image(large-upload-basic-settings.png)]]
 
+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 linnk in the message. This will lead you to the following configuration panel:
+
+[[Image(large-upload-advanced-settings.png)]]
+
+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 50'000, though, 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. 
+
+A very large upload doesn't fit within a single changeset. Please select 
+
+ * whether JOSM should automatically open as many new changesets as required to upload the data. Select this option if you want to run the very large upload without user intervention. 
+
+ * 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.