Context Navigation

Upload

Timestamp:: 2009-12-08T12:40:28+01:00 (16 years ago)
Author:: Gubaer
Comment:: extended

Legend:

: Unmodified
: Added
: Removed
: Modified

Help/Action/Upload

-              v15
+              v16
 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 integraded 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.org public maps] and can be used by other members of the OSM community.
+{{{
+#!html
+<p style="background-color:rgb(253,255,221);padding: 10pt; border-color:rgb(128,128,128);border-style: solid; border-width: 1px;">
+Please be careful with editing and uploading data. When in doubt that everything is ok, rather refrain from uploading and save the area locally on disk to check back to it later.
+</p>
+}}}
+== Changesets and upload requests ==
+== Changesets, upload requests, and upload strategies ==
 Geo data contributed to the OSM server consists of [wiki:/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 for every singe node and every single way why it is published. A more convenient approach is to package a group of related objects and assign the package a comment, not the individual objects.
 …
 === Uploading large datasets into multiple changeset ===
+JOSM also supports uploading large dataset which don't fit into one changset only.
 [[Image(multiple-changesets.png)]]
+''Keyboard shortcut:'' CTRL+SHIFT+U
+This is an advanced option which only useful for power users. They can select this configuration if they have to upload a dataset with more than 50'000 new, modified, or deleted objects.
+When you're happy with the data you generated and/or changed, you need it to upload to the OSM server to be available for everyone.
+== Choosing your upload strategy - when and how often  to upload ==
+There is no simple answer to the question when and how often to upload. You neither should edit the whole day and then upload everything at one nor upload every minute after adding a way.
+If the [http://wiki.openstreetmap.org/index.php/JOSM/Plugins/Validator Validator plugin] is installed, JOSM now performs a quick check on the data. If it finds warnings or errors you'll be presented with a list of them and get the chance to correct the problems and try again or upload anyway. It's not necessary to fix all of that, but please don't go over it easily, especially not the errors.
+Here are some rules of thumb:
+Finally JOSM will present you with a list of changed or newly created elements for reviewing it. You're also asked to provide a short freetext summary of your edits. This description will be saved with your data on the server and serves information purposes like for example the [http://openstreetmap.org/browse Recent Changes list]. If you fixed an error in the data by deleting a way not existing anymore in reality, this is something you should definitely mention.
+ * '''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 with 100 individual upload requests than to upload them in one request including 100 objects.
+With your final click on "Upload changes" your data will be uploaded and visible for everyone else.
+ * '''Collisions with others''': 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. One has to fix the problem (i.e. by resolving a [wiki:/Help/Concepts/Conflict conflict]) and restart uploading. The whole 30'000 objects will have to be uploaded again. On the other hand, if you upload 30'000 object with 10 request à 1000 objects and if the server encounters a problem on the 29'999th object then you only have to repeat the last upload request including the 29000th to the 30000 objects. Object 1-28999 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.
-Please be careful with editing and uploading data. When in doubt that everything is ok, rather refrain from uploading and save the area locally on disk to check back to it later.
+There is no simple answer to the question when and how often to upload. You neither should edit the whole day and then upload everything at one nor upload every minute after adding a way. The former to keep data in memory small, make uploads faster and minimize the risk of your edits colliding with someone else editing the same ways in the same area.
+The latter to minimize the overhead each upload poses on the server in means of CPU time and also database size since each change also means processing and saving some meta information.
+== The Upload Dialog ==
+If possible group your edits. In logical as well as in geographically units, this also makes it easier to give a good upload summary.
+=== Invoking ===
+FIXME: explain open changesets
+ * ''Keyboard shortcut:'' CTRL+SHIFT+U
+ * Menü item ''File->[[Image(source:/trunk/images/upload.png)]] Upload''
+ * Toolbar button [[Image(source:/trunk/images/upload.png)]]
+=== Checks before uploading ===
+If the [http://wiki.openstreetmap.org/index.php/JOSM/Plugins/Validator Validator plugin] is installed, JOSM performs a quick check on the data. If it finds warnings or errors you'll be presented with a list of them and get the chance to correct the problems and try again or upload anyway. It's not necessary to fix all of that, but please don't go over it easily, especially not the errors.
+JOSM also checks for limititations imposed by the OSM server:
+ * tag names and tag values must be shorter than 255 characters
+ * ways can't consist of too many nodes
+ * if the objects you upload 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. You have to break up these dependencies first.
 == Error and Warning messages ==