Automatic upload to OpenStreetMap

[GoogleCodeExporter]

I suggest making the program able to automatically upload the gpx-tracks to 
OSM. The username and password could be set in the settings.
The other OSM-upload settings such as track privacy etc could also be set.

Uploads could be fully automatic or one could be prompted after saving each 
track.
Fully automatic upload would prevent me from having to connect my HTC via the 
data cabel to the pc and upload files individually.

This issue should be Enhancement not Defect (as it seems the issues start out 
as).

Original issue reported on code.google.com by jesperfj...@gmail.com on 27 Jun 2010 at 8:22

[GoogleCodeExporter]

Original comment by nguillau...@gmail.com on 28 Jun 2010 at 9:32

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Just to add to this - the program OpenSatNav has this functionality.
http://launchpad.net/opensatnav/
if further inspiration is needed.
The prompt could be "Track saved. Do you want to upload to OSM?" or something 
similar.
The one could at a later time, log in to OSM and edit the tracks. 

Original comment by jesperfj...@gmail.com on 28 Jun 2010 at 9:46

[GoogleCodeExporter]

When implementing this we'd need to also be asked for descriptions, tags and 
privacy level, as show at: http://www.openstreetmap.org/trace/create
Perhaps also having a configurable default privacy level and tags would be an 
interesting feature.

Original comment by magic...@gmail.com on 19 Aug 2010 at 4:15

[GoogleCodeExporter]

FYI documentation about uploading GPX tracks to OSM: 
http://wiki.openstreetmap.org/wiki/Api06#Uploading_Traces

Original comment by emilien.klein on 29 Sep 2010 at 1:58

[GoogleCodeExporter]

Open GPS Tracker (open source) also has this functionality:
http://code.google.com/p/open-gpstracker/

Rather than storing username and password, you should use the API to connect 
the app to OSM and get a authentication token (or whatever it is called).

Original comment by dittaeva on 17 Feb 2012 at 12:35

[GoogleCodeExporter]

Agreed. Using til auth API is preferred. For now I use a file manager to 
transfer the file to the Dropbox folder on my HTC and dropbox then sends this 
to cyberspace and my office pc. Via the office pc I then upload to OSM. But 
this is all very cumbersome.

Original comment by jesperfj...@gmail.com on 18 Feb 2012 at 7:53

[GoogleCodeExporter]

I had a look at doing that using OAuth, but currently the OSM OAuth servers 
returns an error 500 when trying to get a request token. Will retry later.

Original comment by nicolas@guillaumin.me on 29 Jul 2012 at 8:06

[GoogleCodeExporter]

GPSLogger for Android has both Oauth and (perhaps automatic) upload of traces 
to OpenStreetMap. It is open source.

http://mendhak.github.com/gpslogger/

Original comment by dittaeva on 29 Jul 2012 at 9:16

[GoogleCodeExporter]

Thanks that was useful, I got the upload working now.

Original comment by nicolas@guillaumin.me on 31 Jul 2012 at 1:44

[GoogleCodeExporter]

Great to hear. Will try it out as soon as updated is available. 

Original comment by b.lind...@gmail.com on 31 Jul 2012 at 1:58

[GoogleCodeExporter]

Just released v0.6.0 that implements OSM upload.

Original comment by nicolas@guillaumin.me on 13 Aug 2012 at 8:56

• Changed state: Fixed
• Added labels: v0.6.0

[GoogleCodeExporter]

There's problem with this feature. Should I comment it here or add a new issue 
for the bug?

Original comment by b.lind...@gmail.com on 13 Aug 2012 at 12:04

[GoogleCodeExporter]

Hi, you can re-open this one if you want.

Original comment by nicolas@guillaumin.me on 13 Aug 2012 at 12:11

[GoogleCodeExporter]

In the latest release (0.6.1) which is a really nice update with lots of nice 
details btw, the upload of a track to OSM fail on me though.

First issue:
When uploading a track with the exported name 
15_aug_2012_09;03;03-Walking,Händelövägen,Bråviksvägen,Lindö,Norrköping,S
weden_2012-08-15_09-03-03.gpx

The filename when uploaded to openstreetmap.org is changed to, in this case:
osm_upload_151816904.gpx

I find it more logical that it's the same as the exported filename.

The description I set was this:
Walking,Händelövägen,Bråviksvägen,Lindö,Norrköping,Sweden

There seem to be some encoding problem with the description though after I 
uploaded it:
Walking,H?ndel?v?gen,Br?viksv?gen,Lind?,Norrk?ping,Sweden

Also, if the tags have åäö in them I get an error message when trying to 
upload the track. See: http://imgur.com/45ToB

Original comment by b.lind...@gmail.com on 16 Aug 2012 at 5:17

[GoogleCodeExporter]

Hi,

For the file name I did it like that because it was easier in the code and I 
didn't think the file name matters too much since you have a description and 
tags.

I'll have a look for the tags issue, shouldn't be hard to fix.

Original comment by nicolas@guillaumin.me on 19 Aug 2012 at 1:49

[GoogleCodeExporter]

The character enconding is now fixed fixed, will be available on the next 
market release.

Original comment by nicolas@guillaumin.me on 19 Aug 2012 at 2:03

• Added labels: v0.6.3

[GoogleCodeExporter]

I also found a solution to use the correct filename, however the OSM server 
seems to do some cleanup for non-ASCII characters as well and there's nothing I 
can do to prevent that :(

Original comment by nicolas@guillaumin.me on 19 Aug 2012 at 6:31

[GoogleCodeExporter]

i use OSMtracker on jelly bean on google Nexus and when uploading to 
Openstreetmap i get the following eror message

Unable to authenitcate to 
OSM:oauth.signpost.exception.OAuthCommunicationException:Communication wilt the 
service provider failed: null

Original comment by edmund.h...@gmail.com on 8 Sep 2012 at 3:48

[GoogleCodeExporter]

Same as issue #206 I guess. Could you comment on #206 and confirm if it's a 
Galaxy Nexus or an older model ? Thanks. It works for me on Jelly Bean on a 
Galaxy Nexus.

Original comment by nicolas@guillaumin.me on 9 Sep 2012 at 3:04