Export to osm file type

[GoogleCodeExporter]

A feature that would make the usage of data made with OSMTracker much easier, 
is the ability to export the track as an osm file.

Then POIs could be exported with tags corresponding to the buttons used, and 
the processing and uploading of the data would take much less time.

I understand that this would require a lot more work than the current 
maintainer is up for, so this is more of a place holder bug where we can 
discuss possibilities.

One alternative that I see as feasable is that values of the current POI names 
were made in such a way that the resulting gpx file could easily be converted 
to osm. A custom button layout could be made to try this out.

Have anyone tried converting the output gpx to osm, so that a toilet POI became 
amenity=toilets for example?

Original issue reported on code.google.com by dittaeva on 17 Feb 2012 at 12:50

[GoogleCodeExporter]

Original comment by nicolas@guillaumin.me on 29 Jul 2012 at 5:49

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It sounds easy for first time but could by problematic with ways.
If you don't add any highway types, what kind of way should the way be in the 
exported OSM file?
It could work only with nodes but it can be difficult, too, for example if you 
add a traffic light or a pedestrian crossing you don't want to add a new node 
somewhere near to the given highway but exactly on the way. It doesn't possible 
to add nodes to existsing ways in offline mode.

Original comment by pluto...@gmail.com on 18 Aug 2012 at 9:41