Changes between Version 13 and Version 14 of Help/Action/Upload


Ignore:
Timestamp:
2009-12-08T12:10:38+01:00 (16 years ago)
Author:
Gubaer
Comment:

extended

Legend:

Unmodified
Added
Removed
Modified

  • Help/Action/Upload

    v13 v14  
    99Geo 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.
    1010
    11 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 deletings) applied to OSM data.
     11The 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 deletings) applied to OSM data.
    1212
    1313Changesets are not equal to '''upload requests''', though. A changeset is a '''logical''' grouping of [wiki:/Help/Concepts/Object objects] whereas an upload request is a '''technical grouping''' for the purpose of 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 one to configure both aspects of the upload requests to be used and of the changeset objects are uploaded to. Some of the settings are compulsory (i.e. the user has to configure them before he or she can upload geo data) but most of them are optional and JOSM works with reasonable default values.
     14
     15Geo data can be retrieved later by the changeset it was uploaded to, it can't be retrieved by the upload request used. Changesets have a unique id, upload requests have not. For instance, [http://www.openstreetmap.org/browse/changeset/3274448 this changeset] includes geo data gained by tracing over orthofotos of the city of Bern, Switzerland. It isn't possible, though, to see which and how many upload requests have be used to fill it in.
    1416
    1517=== One upload request into one changeset ===
    … …  
    2426
    2527
    26 === Multiple upload request into one changeset ===
    27 
     28=== Uploading large dataset into multiple changeset ===
     29As described above there are
    2830
    2931[[Image(one-changeset-multiple-upload-request.png)]]
    3032
    31 This is an advanced configuration option which most users want have to enable. It can be useful:
     33This is an advanced configuration option which most users don't have to enable. It can be useful:
    3234 * for users who map using multiple data layer in JOSM and who want to upload the result of their work into one changeset
    3335 * 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 whole 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.
    3436
     37JOSM still supports to upload each object individually.
    3538
     39[[Image(one-changeset-individual-object-upload-request.png)]]
     40
     41Please note that this is a legacy feature. Until recently, this was the only upload option in OSM.  Technically, it uses a slightly different approach to communicate with the OSM server. It is still available in JOSM although the OSM server now supports upload requests with up to 50'000 objects. For the casual and normal user it is almost obsolete. In rare cases, it could be useful for power users.
     42
     43=== Multiple upload request into one changeset ===
    3644
    3745''Keyboard shortcut:'' CTRL+SHIFT+U