Changes between Version 28 and Version 29 of Help/Action/Upload


Ignore:
Timestamp:
2009-12-12T15:49:48+01:00 (16 years ago)
Author:
Gubaer
Comment:

typos

Legend:

Unmodified
Added
Removed
Modified

  • Help/Action/Upload

    v28 v29  
    1515
    1616== Changesets, upload requests, and upload strategies ==
    17 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.
     17Geo 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 single 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.
    1818
    1919The 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.
    2020
    21 Changesets 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.
    22 
    23 Geo 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.
     21Changesets 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 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 aspects of the upload requests to be used and aspects 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.
     22
     23Geo 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 from 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.
    2424
    2525=== One upload request into one changeset ===
    … …  
    3333 * for users uploading the result of entering local knowledge about street names, points of interests, etc.
    3434
    35 
    3635=== Multiple uploads into one changeset ===
    3736
    … …  
    4039This is an advanced configuration option which most users don't have to enable. It can be useful:
    4140 * for users who map using multiple data layer in JOSM and who want to upload the result of their work into one changeset
    42  * 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.
     41 * 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 complete 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.
    4342
    4443JOSM still supports to upload each object individually.
    … …  
    4948
    5049=== Uploading large datasets into multiple changeset ===
    51 JOSM also supports uploading large dataset which don't fit into one changset only.
     50JOSM also supports uploading large datasets which don't fit into one changeset only.
    5251
    5352[[Image(multiple-changesets.png)]]
    5453
    55 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.
     54This is an advanced option which only is 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.
    5655
    5756== Choosing your upload strategy - when and how often  to upload ==
    58 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.
     57There 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 once nor upload every minute after adding a way.
    5958
    6059Here are some rules of thumb:
    … …  
    6261 * '''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.
    6362
    64  * '''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.
    65 
     63 * '''Collisions with other mappers''': 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]). 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 30000th 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.
    6664
    6765== Uploading data  ==
    … …  
    7068
    7169 * ''Keyboard shortcut:'' CTRL+SHIFT+U
    72  * Menü item ''File->[[Image(source:/trunk/images/upload.png)]] Upload''
     70 * Menu item ''File->[[Image(source:/trunk/images/upload.png)]] Upload''
    7371 * Toolbar button [[Image(source:/trunk/images/upload.png)]]
    7472
    … …  
    8987
    9088The upload dialog consists of two sections:
    91  * the upper half displays a summary of the objects to be added, to be modified and to be deleted on the server
     89 * the upper half displays a summary of the objects to be added, to be modified, and to be deleted on the server
    9290 * the lower part provides panels for configuring various aspects of the upload process
    9391
    … …  
    111109'''Do's and Don'ts'''
    112110 * Tags are your friends. Use them to describe the geo data you are uploading to the OSM server.
    113  * Use the tag {{{source}}} to describe the source of your geo data (examples: {{{traced from Yahoo Imagery}}}, {{{based on GPS traces and surveys by bike}}}).
     111 * Use the tag {{{source}}} to describe the source of your geo data (examples: {{{traced from Yahoo Imagery}}}, {{{based on GPS traces and surveyed by bike}}}).
    114112 * You don't have to add your user name to the tags. The link between the changeset and your OSM user account is maintained automatically.
    115113
    … …  
    123121JOSM uploads to a new changeset if '''Upload to a new changeset''' is selected. This is the standard setting.
    124122
    125 If you want to upload to an existing changeset you have to select one 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.
     123If 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.
    126124
    127125Click 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 succesful upload.
    … …  
    131129
    132130==== Configuring the number and size of upload requests ====
    133 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 size of upload requests, see screenshot:
     131JOSM 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:
    134132
    135133[[Image(advanced-config-panel.png)]]
    136134
    137 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 works or it doesn't work. 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 because the entire upload can fail because there is a problem in the last object in the upload request.
    138 
    139 Select '''Upload data in chunks of object''' 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 request (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 information because JOSM will inform you when an individual chunk was uploaded successfully or when its upload has failed. Uploading in chunks is in most cases slower than uploading in one requests, though.
    140 
    141 Select '''Upload each object individually''' to to upload each object with an individual upload request. You will get very fine grained progress information 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.
     135Select '''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.
     136
     137Select '''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 request (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.
     138
     139Select '''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.
    142140
    143141'''Recommendations'''
    … …  
    151149[[Image(large-upload-basic-settings.png)]]
    152150
    153 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:
     151The 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 link in the message. The following configuration panel will be displayed:
    154152
    155153[[Image(large-upload-advanced-settings.png)]]
    156154
    157 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.
     155For 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, too, 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.
    158156
    159157A very large upload doesn't fit within a single changeset. Please select
    160158
    161  * 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.
     159 * whether JOSM should automatically open as many new changesets as required to upload the data. Select this option if you want to run a very large upload without user intervention.
    162160
    163161 * 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.
    164 
    165162
    166163== Error and Warning messages ==
    … …  
    178175 * Upload again
    179176
    180 
    181177=== Changeset becomes full during upload ===#ChangesetFull
    182 There is an upper limit for the size of changesets. On the OSM server it's currently set to 50'000 objects per changeset. An upload may exceed this limit while uploading, mainly if you are filling up a changeset with a sequence of upload requests.
     178There is an upper limit for the size of changesets. On the OSM server it's currently set to 50'000 objects per changeset. An upload may exceed this limit while uploading, mainly if you are uploading a sequence of upload requests to the same changeset.
    183179
    184180If JOSM detects that a changeset became full it displays the following warning message:
    … …  
    188184'''How to resolve'''
    189185 * Click on '''Continue Uploading''' to continue the upload with as many new changesets as necessary.
    190  * Click on '''Go back to Upload Dialog''' to go back to the upload dialog. There you can select another changeset to upload the remaining object to.
     186 * Click on '''Go back to Upload Dialog''' to go back to the upload dialog. There you can select another changeset to upload the remaining objects to.
    191187 * Click on '''Abort''' to abort uploading and return to the main map editing interface.
    192188