Context Navigation

Upload

Timestamp:: 2012-02-24T13:47:27+01:00 (14 years ago)
Author:: skyper
Comment:: validator is in core

Legend:

: Unmodified
: Added
: Removed
: Modified

Help/Action/Upload

-              v41
+              v42
 == 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 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.
 The OSM project calls such a package a **[wiki:/Help/Concepts/Changeset changeset]**. A **changeset** is a collection of related changes (new objects, object modifications, or object deletions) applied to OSM data.
 Changesets are different from **upload requests**. A changeset is a **logical** grouping of [wiki:/Help/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.
+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.
+The OSM project calls such a package a **[Concepts/Changeset changeset]**. A **changeset** is a collection of related changes (new objects, object modifications, or object deletions) applied to OSM data.
+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.
 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.
 …
  * ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}**
  * Menu item ''File->[[Image(source:/trunk/images/upload.png)]] Upload''
  * Toolbar button [[Image(source:/trunk/images/upload.png)]]
+ * Menu item ''File->[[Image(source:trunk/images/upload.png)]] Upload''
+ * Toolbar button [[Image(source:trunk/images/upload.png)]]
 === Checks before the Upload Dialog is displayed ===
 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.
+Before the Upload Dialog is displayed, [Dialog/Validator validator] is run on all modified [Concepts/Objects objects]. 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 limitations imposed by the OSM server:
 …
 === Running a simple upload ===
 . [wiki:/Help/Action/Upload#LaunchUploadDialog Launch]  the Upload Dialog
+. [#LaunchUploadDialog Launch]  the Upload Dialog
 . Enter an upload comment. You **must** provide an upload comment of at least 3 characters.
 . Click on [[Image(source:/trunk/images/upload.png)]]**Upload Changes**
+. Click on [[Image(source:trunk/images/upload.png,16)]] **Upload Changes**
 === Running an upload with advanced options ===
 ==== Adding tags to the changeset ====
 Geo data uploaded to the OSM server is always uploaded to a [wiki:/Help/Concepts/Changeset changeset]. Similar to [wiki:/Help/Concepts/Object nodes, ways, and relations] one can assign [wiki:/Help/Concepts/Object tags] to a changeset.
+Geo data uploaded to the OSM server is always uploaded to a [Concepts/Changeset changeset]. Similar to [Concepts/Object nodes, ways, and relations] one can assign [Concepts/Object tags] to a changeset.
 In the Upload Dialog one can enter tags in the Tag Configuration Panel, see screenshot below:
 …
 [[Image(changeset-config-panel.png)]]
 JOSM uploads to a new changeset if '''Upload to a new changeset''' is selected. This is the standard setting.
 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.
 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.
 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'''.
+JOSM uploads to a new changeset if **Upload to a new changeset** is selected. This is the standard setting.
+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.
+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.
+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**.
 ==== Configuring the number and size of upload requests ====
 JOSM uploads geo data with one or more **upload requests** to a [wiki:/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:
+JOSM uploads geo data with one or more **upload requests** to a [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:
 [[Image(advanced-config-panel.png)]]
 …
 <a name="NodeStillInUseInWay">
 }}}
 If your upload includes a deleted [wiki:/Help/Concepts/Object node] the OSM server checks if the node is still used in one of the ways known to the server. You have to make sure that the node is ''isolated'' (not part of any way and not referred to by any relation) before it can be deleted.
+If your upload includes a deleted [Concepts/Object node] the OSM server checks if the node is still used in one of the ways known to the server. You have to make sure that the node is ''isolated'' (not part of any way and not referred to by any relation) before it can be deleted.
 If the OSM server detects that the node is still in use it replies an error message which JOSM displays as follows:
 …
 [[Image(upload-412-node-still-in-use.png)]]
 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 [wiki:/Help/Concepts/Conflict conflict] which you have to [wiki:/Help/Concepts/Conflict resolve] manually.
+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 [Concepts/Conflict conflict] which you have to [Concepts/Conflict resolve] manually.
 After that, just upload again. Your upload now includes all parent ways of the deleted node and the deleted node is removed from all of them. The upload should therefore succeed.
 == See also ==
  * [[Image(source:/trunk/images/uploadselection.png,20)]] [wiki:/Help/Action/UploadSelection Upload Selection to OSM]
  * [wiki:/Help/Concepts/Conflict What is a conflict?]
+ * [[Image(source:trunk/images/uploadselection.png,20)]] [Action/UploadSelection Upload Selection to OSM]
+ * [Concepts/Conflict What is a conflict?]
 ----
 Back to [wiki:/Help/Menu/File Menu File][[Br]]
+Back to [Menu/File Menu File][[Br]]
 Back to [wiki:/Help Main Help]