I have many POIs, but in garmin format .gdb, .shp, .gpx. How to load the files data? |
You can load GPX files into most OSM editors, however we don't encourage people to simply upload data to OSM because it might clash with existing data! You would normally load your GPX data into an editor, then load the existing OSM data for the same area, and only where the POI is not present in OSM would you manually create a POI at the correct location. It is not a big problem if automatically loaded POI clashes with already existent old POI. It can be fixed later by hands or automatically (by finding POIs with similar names). But option to have up to date POIs database is more useful. I believe must be a program to automatically create and maintain POIs.
(01 Jan '13, 18:57)
Dmytro Ovdii...
5
I'd strongly disagree with that comment - it would be a big problem if lots of people were to import lots of duplicates. Thankfully it doesn't happen much - any such imports either fail at the discussion stage or are reverted due to lack of discussion.
(01 Jan '13, 21:05)
SomeoneElse ♦
|
(I'll assume that, if you're relatively new to OSM, you'll be wanting to use "Potlatch" the online editor) Your GPX files can be uploaded to OSM, and GPX files from Garmin devices can contain "wpt" information. In order to upload the trace you'll need to ensure that there's at a small track in the file as well.
For each waypoint that you've uploaded, you'll need to review what's already in OSM for it. You might just need to correct a name, add some other tags, or you might want to convert your waypoint to a node in OSM. To do that:
One big caveat though - you should only upload information that you've created yourself. If you've gone somewhere, saved a waypoint and entered all details against it yourself, then that's OK. If you've saved a feature from a non-OSM Garmin map as a waypoint, then that's NOT OK, because there's information that's come from other than your own work. |
When I have to import POI from GPX data I collected during holidays I do the following:
|