| 1 |
Projects
|
| 2 |
--------
|
| 3 |
|
| 4 |
OSM2Go uses projects to organize the work. This happens for
|
| 5 |
mainly two reasons:
|
| 6 |
|
| 7 |
1. The world is too large to be handled by a handheld device, so the
|
| 8 |
concept of projects breaks the world down into little pieces a user
|
| 9 |
is working on.
|
| 10 |
|
| 11 |
2. A handheld device is likely not always online. Thus changes are done
|
| 12 |
locally, stored in the project and uploaded/synched at a later time.
|
| 13 |
|
| 14 |
|
| 15 |
A project consists of several parts:
|
| 16 |
|
| 17 |
- The project file itself containing the projects name, the geographic
|
| 18 |
area it refers to and information required to up- and download data.
|
| 19 |
|
| 20 |
- The osm file being the information downloaded from the openstreetmap
|
| 21 |
servers and containing a snapshot of the state of geographic area
|
| 22 |
specified in the project file at the time of download. The osm file
|
| 23 |
is never touched by osm2go unless it is overwritten by a newer version.
|
| 24 |
|
| 25 |
- A diff file containing the changes the user has made to the data in the
|
| 26 |
osm file and which has not yet been uploaded to the osm server.
|
| 27 |
|
| 28 |
Uploading
|
| 29 |
---------
|
| 30 |
|
| 31 |
The upload is a delicate step as this actually alters the openstreetmap
|
| 32 |
main database. This also is the only step that alters it, so unless you
|
| 33 |
perform an update you can play around with the map as you want without
|
| 34 |
risking to destroy anything.
|
| 35 |
|
| 36 |
So you actually have decided to perform an upload. You've changed some
|
| 37 |
ways or nodes. These changes are currently in the project diff file
|
| 38 |
and you may actually leave and restart osm2go without leaving those
|
| 39 |
changes. Selecting upload from the menu will first give you a raw overview
|
| 40 |
of what will happen. You'll be told how many way and nodes you've changed,
|
| 41 |
how many have been deleted and how many have been created newly. Currently
|
| 42 |
the "relation" row will always contain zeros as osm2go does not support
|
| 43 |
relations yet. But please take a short look at the numbers presented for
|
| 44 |
ways and nodes. Do they make sense? Do they e.g. indicate that something is
|
| 45 |
to be deleted, but you didn't delete anything? Please don't go ahead then,
|
| 46 |
but try to figure out what happened.
|
| 47 |
|
| 48 |
If everything looks reasonable, then enter your openstreetmap account
|
| 49 |
data into the username and password fields and click ok. A new window will
|
| 50 |
open containing a text buffer. This is the upload log. It will record
|
| 51 |
basic information about your upload and may be especially useful if something
|
| 52 |
goes wrong. Lets hope you entered your username and the password correctly.
|
| 53 |
Then the upload should succeed. This usually only takes a few seconds.
|
| 54 |
If your upload went fine and you actually changed data on the servers
|
| 55 |
database, osm2go will then re-download the entire project area from the
|
| 56 |
server. It will free the map and redraw it on basis of the newly downloaded
|
| 57 |
data which now hopefully includes the changes you just uploaded. You should
|
| 58 |
see the same map as before, but this time it comes entirely from data stored
|
| 59 |
on the main server. Congratulations, you just contributed to the openstreetmap
|
| 60 |
project!
|
| 61 |
|
| 62 |
You can go ahead and continue editing and uploading. OSM2Go will take care of
|
| 63 |
your changes and make sure everything is stored until you upload it to the
|
| 64 |
server so the server takes over the maintenance of your contributions.
|
| 65 |
|
| 66 |
Getting started
|
| 67 |
---------------
|
| 68 |
|
| 69 |
Getting started with osm2go is not dangerous since osm2go works offline
|
| 70 |
most of the time and does not touch any data stored in the openstreetmap
|
| 71 |
database unless being asked to do so.
|
Parent Directory
| 
Revision Log