Changes between Initial Version and Version 1 of Nl:Help/Action/Upload

Timestamp:

2016-01-24T17:00:25+01:00 (10 years ago)

Author:

DiGro

Comment:

translated into Dutch

Nl:Help/Action/Upload

@@ +1 @@
+[[TranslatedPages(revision=43]]
+[[PageOutline(1-10,Table of Contents)]]
+
+= Bestand > Uploaden naar OSM =
+
+[[Image(source:trunk/images/upload.png,middle)]]  ''Toetsenbord sneltoets:'' **{{{Ctrl+Shift+↑}}}**
+
+**Nieuwe, gewijzigde en verwijderde objecten op de huidige gegevenslaag naar de server uploaden.**
+
+Geo-gegevens die worden bewerkt in JOSM zijn alleen lokaal beschikbaar en alleen te gebruiken door de gebruiker die die gegevens heeft ingevoerd, tenzij die gebruiker besluit om ze ook voor de gemeenschap beschikbaar te stellen. De gebruiker moet ze **uploaden** om de gegevens te publiceren. Uploaden betekent dat de geo-gegevens worden overgebracht naar een centrale server die wordt beheerd door de gemeenschap van OSM, waar het wordt geïntegreerd met geo-gegevens van andere mappers in één centrale database. Door het uploaden van gegevens die lokaal zijn bewerkt worden geo-gegevens zowel deel van de [osmwww: public maps] en dat zij kunnen worden gebruikt door andere leden van de gemeenschap van OSM.
+
+{{{
+#!html
+<p style="background-color:rgb(253,255,221);padding: 10pt; border-color:rgb(128,128,128);border-style: solid; border-width: 1px;">
+Wees alstublieft voorzichtig met het bewerken en uploaden van gegevens. Indien u twijfelt of alles wel OK is, laat het uploaden dan achterwege en sla het gebied lokaal op op de harde schijf, controleer wat u nodig vindt en probeer het later nog eens.
+</p>
+}}}
+
+== Wijzigingensets, verzoeken om te uploaden en strategieën voor uploaden ==
+Geo-gegevens die zijn bijgedragen aan de server van OSM bestaan uit [wiki:/Nl:Concepts/Object knopen, wegen en relaties]. Omdat er honderden mappers zijn die hun geo-gegevens publiceren op de server van OSM server is het belangrijk om na te kunnen gaan wie welke gegevens publiceerde en in welke context. Het zou voor mappers ontzettend veel tijd vergen om te beschrijven waarom elke enkele knoop en elke enkele weg is gepubliceerd. Een meer bruikbare benadering is om een groep gerelateerde objecten bij elkaar te verpakken en aan het pakket zelf een opmerking toe te wijzen, in plaats van aan de individuele objecten. 
+
+Het project OSM noemt een dergelijk pakket een **[wiki:/Nl:Concepts/Changeset wijzigingenset]**. Een **wijzigingenset** is een collectie gerelateerde wijzigingen (nieuwe objecten, aanpassingen aan objecten, of verwijderingen van objecten) toegepast op gegevens van OSM. 
+
+Wijzigingensets verschillen van **verzoeken voor uploaden**. Een wijzigingenset is een **logische** groepering van [wiki:/Nl:Concepts/Object objecten], waar een verzoek voor uploaden een **technische groepering** is om geo-gegevens over te brengen naar alleen de centrale server van OSM. In JOSM zeggen we dat objecten worden geüpload **met behulp van** verzoeken voor uploaden **naar** een wijzigingenset. Het dialoogvenster Uploaden in JOSM maakt het mogelijk aspecten van de objecten voor verzoeken voor uploaden en wijzigingenset te configureren. Sommige van de instellingen zijn verplicht (d.i. de gebruiker moet ze configureren vóórdat geo-gegevens kunnen worden geüpload) maar de meeste ervan zijn optioneel en JOSM werkt met redelijke standaardwaarden. 
+
+Geo-gegevens kunnen later worden opgehaald via de wijzigingenset waarmee ze werden geüpload, maar ze kunnen niet worden opgehaald met behulp van het gebruikte verzoek voor uploaden. Wijzigingensets hebben een unieke identificatie, verzoeken voor uploaden hebben dat niet. Bijvoorbeeld: [osmwww:browse/changeset/3274448 deze wijzigingenset] bevat geo-gegevens van het traceren van luchtfoto's van de stad Bern, Zwitserland. Het is echter niet mogelijk om de verzoeken voor uploaden te zien waarmee het werd gevuld. 
+
+=== Eén verzoek voor uploaden in één wijzigingenset ===
+In het meest eenvoudige geval zit er slechts één verzoek voor uploaden in een wijzigingenset:
+
+[[Image(wiki:Help/Action/Upload:one-changeset-one-upload-request.png)]]
+
+Dit is de standaard configuratie die wordt gebruikt door JOSM. Het is de voorkeursconfiguratie
+* voor gebruikers die het resultaat van het converteren van een aantal GPS-sporen uploaden naar de geo-gegevens van OSM 
+* voor gebruikers die het resultaat van het traceren van een aantal uren van luchtfoto's uploaden 
+* voor gebruikers die het resultaat van het invoeren van lokale kennis over straatnamen, points of interests, etc. uploaden
+
+=== Meerdere uploads in één wijzigingenset ===
+
+[[Image(wiki:Help/Action/Upload:one-changeset-multiple-upload-request.png)]]
+
+Dit is een gevorderde optie voor configuratie die de meeste gebruikers niet hoeven in te schakelen. Het kan handig zijn:
+* voor gebruikers die in kaart brengen met meerdere gegevenslagen in JOSM en die het resultaat van hun werk in één wijzigingenset willen uploaden 
+* voor gebruikers die werken aan een lange sessie van in kaart brengen. Voor hen zou het veiliger zijn om tussenliggende resultaten naar de server te uploaden dan om alleen het resultaat van de volledige sessie te uploaden. In het eerste geval kunnen zijn meerdere verzoeken voor uploaden in één wijzigingenset gebruiken, wat hen helpt hun gegevens veilig te behouden zonder ze te fragmenteren in niet aan elkaar gerelateerde wijzigingensets. 
+
+JOSM ondersteunt nog steeds het individueel uploaden van elk object.
+
+[[Image(wiki:Help/Action/Upload:one-changeset-individual-object-upload-request.png)]]
+
+Please 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. 
+
+=== Uploading large datasets into multiple changeset ===
+JOSM also supports uploading large datasets that don't fit into a single changeset. 
+
+[[Image(multiple-changesets.png)]]
+
+This is an advanced option which is 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. 
+
+== 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 once nor upload every minute after adding a way. 
+
+Here are some rules of thumb:
+
+* **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 using 100 individual upload requests than to upload them in one request containing 100 objects. 
+
+* **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. The problem has to be fixed first (i.e. by resolving a [wiki:/Help/Concepts/Conflict conflict]). The whole 30,000 objects will then have to be uploaded again. On the other hand, if you upload 30,000 objects with 10 requests containing 1,000 objects each and the server encounters a problem on the 29,999th object then you only have to repeat the last upload request for the 29,000th to 30,000th objects. Objects 1-28,999 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. 
+
+== Uploading data  ==
+
+=== Launching the Upload Dialog ===#LaunchUploadDialog
+
+* ''Keyboard shortcut:'' **{{{Ctrl+Shift+↑}}}**
+* Menu item ''File->[[Image(source:trunk/images/upload.png,middle)]] Upload''
+* Toolbar button [[Image(source:trunk/images/upload.png,middle)]] 
+
+=== Checks before the Upload Dialog is displayed ===
+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:
+* tag names and tag values must be shorter than 255 characters
+* ways can't consist of too many nodes 
+
+If the objects you're uploading 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. JOSM will ask you to break up these dependencies first. 
+
+**Note**: On large datasets these checks can take some time and for the time being they don't provide user feedback. Please be patient if it takes a couple of seconds to launch the Upload Dialog on large datasets. This will be fixed soon.
+
+=== The Upload Dialog ===
+
+[[Image(upload-dialog-screenshot.png)]]
+
+The upload dialog consists of two sections:
+* the upper half displays a summary of the objects to be added, to be modified, and to be deleted on the server
+* the lower part provides panels for configuring various aspects of the upload process
+
+When the Upload Dialog is launched it always displays the basic configuration panel which includes a text box for entering an upload comment and a summary of the other upload parameters for this upload. 
+
+=== Running a simple upload ===
+
+1. [#LaunchUploadDialog Launch]  the Upload Dialog
+1. Enter an upload comment. You **must** provide an upload comment of at least 3 characters. 
+1. Click on [[Image(source:trunk/images/upload.png,middle)]] **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 [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(tags-config-panel-screenshot.png)]]
+
+**Do's and Don'ts**
+* Tags are your friends. Use them to describe the geo data you are uploading to the OSM server.
+* 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}}}).
+* 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.
+
+Note that the required upload comment is also a tag. You can either enter it in the Tag Configuration Panel with the key {{{comment}}} or in the Basic Settings Panel in the text input field provided there. 
+
+==== Choosing the changeset to upload to ====
+In the Changeset Configuration Panel you can select what [wiki:/Help/Concepts/Changeset changeset] the data is uploaded to, see the 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,middle)]] ''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,bottom)]] **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 [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)]]
+
+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 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.
+
+Select **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 requests (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. 
+
+Select **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. 
+
+**Recommendations**
+* For small (<1,000 objects) to medium upload sizes (<5,000 objects), choose **Upload data in one request**
+* For medium to large upload sizes (> 5,000 objects) choose **Upload data in chunks of objects**. A chunk size of 1,000 is a good value to start with.
+* 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 detects that your upload is bigger it displays the following information in the Upload Dialog: 
+
+[[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 link in the message. The following configuration panel will be displayed:
+
+[[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, 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. 
+
+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 a 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. 
+
+== Error and Warning messages ==
+
+=== Uploading to a closed changeset ===#ChangesetClosed
+If you upload to an open changeset, the upload may fail because the changeset has been closed in the meantime. It could have been closed by the server because of a timeout (changesets don't stay open for more than 24 hours and are also closed after an hour of inactivity) or because you closed it explicitly in another JOSM instance. 
+
+JOSM displays the following error message:
+
+[[Image(error-dialog-changeset-closed.png)]]
+
+**How to resolve**
+* Launch the Upload Dialog again
+* Select another open changeset or select to upload to a new changeset
+* Upload again 
+
+=== Changeset becomes full during upload ===#ChangesetFull
+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 uploading a sequence of upload requests to the same changeset.
+
+If JOSM detects that a changeset became full it displays the following warning message:
+
+[[Image(error-dialog-changeset-full.png)]]
+
+**How to resolve**
+* Click on **Continue Uploading** to continue the upload with as many new changesets as necessary.
+* 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.
+* Click on **Abort** to abort uploading and return to the main map editing interface. 
+
+
+=== Deleting nodes that are still in use ===
+{{{
+#!html
+<a name="NodeStillInUseInWay">
+}}}
+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 [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,middle)]] [Action/UploadSelection Upload Selection to OSM]
+* [Concepts/Conflict What is a conflict?]
+
+----
+Back to [Menu/File Menu File][[Br]]
+Back to [wiki:/Help Main Help]