You are not logged in.

#1 2019-01-06 09:31:12

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Mapper needed for North Thailand

Hi All,

Colin, aka Captain Slash has been riding in Thailand 3-4 months every year since at least 2010. He has saved all his tracks and annotated them for us and Russ McD and I have been putting them into OSM for the last 8 years. Russ has abandoned this in order to help clean up the Facebook mess, a task that I am not willing to do, simply because there are not enough days left in my life. So, I have fallen behind by two seasons.

We need a volunteer to help with this. If we don't use his tracks he will probably stop posting and annotating them, a job that takes him about an hour per day. I will probably pick it up again when it gets too hot outside.

Check out his ride reports here: https://www.rideasia.net/motorcycle-for … .36/page-9

Thanks for your time,
Peter.

Offline

#2 2019-01-06 10:24:00

Mishari
Moderator
Registered: 2013-01-14
Posts: 137

Re: Mapper needed for North Thailand

What needs to be done?

Offline

#3 2019-01-06 12:05:41

Russ McD
Member
From: Hereford & Chiang Mai.
Registered: 2011-04-17
Posts: 289

Re: Mapper needed for North Thailand

There may be different methods, but basically the "full" process involves :

- Downloading the GPX file into Mapsource, one day at a time.
- Either upload to OSM on a daily basis, or consolidate to about 15-20 tracks then upload (which I prefer)
- Open the OSM editor and trace them, labelling as tracks, unless obviously different.
- Most tracks are dead ends, & as the trace doubles back, while you can split and join, its often easier to just manually trace the average of the two.
- Smooth jagged corners, straighten the straight sections, and connect nodes to the existing network.
- Open Colin's daily e-mail, and refine the input by adding POI's and surface changes where he indicates, most usually changes from paved to unpaved, and track to path.
- Make a note on the shared spreadsheet kept by Beddhist & myself, as a record of work accomplished

As of today, Colin has about 150 days of riding we have yet to add (but he is still providing more daily).  As a rough guide, it takes me about 10 hours to input & trace 15 days worth of tracks, and a probably 5 more hours to add the POI/surface details. There may be quicker ways but this is what it takes me, and even then, I omit some of the really short dead ends. 
To save you the math that equals 200 man hours.

A typical POI email from Colin, for one day would contain this info :

N18.57159 E100.72955 to N18.57159 E100.72688 was unpaved.
Track became unpaved at N18.57727 E100.71348 and met the paved surface at N18.58423 E100.70621, N18.57751 E100.71627 and N18.57724 E100.71811.
Tracks at N18.57576 E100.71124, N18.57550 E100.70741, N18.57542 E100.70488, N18.58654 E100.74056 and N18.59274 E100.74212 were unpaved
Track at N18.57558 E100.70274 was unpaved, it met the paved surface at N18.58245 E100.70375 and N18.58066 E100.70004.
N18.57946 E100.69914 to N18.58095 E100.69897 was unpaved.
Track became unpaved at N18.57096 E100.72472, it met the paved surface at N18.56587 E100.72604 and N18.56838 E100.71683.
Track at N18.57403 E100.71828 and N18.57350 E100.72072 is now fully paved, the bit from N18.57403 E100.71828 is a wide asphalt road until N18.55051 E100.70190 where it returns to unpaved until it meets the 101.
Along this asphalt section the tracks running NW and SE at N18.57069 E100.71696, NW at N18.56927 E100.71571 and NW at N18.56229 E100.70860 were unpaved

The Potlatch editor is not ideal for locating nodes by Lat/Long even with the co-ordinates displayed.

I hope this gives an idea of the work, and if we have any takers, I'm sure either me or Beddhist would gladly provide some initial help.

Russ.

Offline

#4 2019-01-06 15:37:13

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Mapper needed for North Thailand

We most certainly will be here to help, but an experienced mapper will find it quite easy. Actually, the above example is exceptionally long. Most contain only a few lines and 5-10 POIs.

I have to agree with Russ, uploading the tracks in bulk is easier and I will do that from now on. Until now I have usually uploaded them with the josm plugin.

My workflow is a little different: I load a track into Mapsource, delete the rubbish tracks (you know, the spaghetti you get from being inside, etc.). Then I create the POIs, where I use abbreviations to orient myself, like D for dirt section, DE for dirt ends, etc. Next, I follow the tracks from either end and wherever there is no road/track on the map I cut the track section out and colour it red for sealed, magenta for unsealed, green for single track.

I find Mapsource really convenient for this, because it has lots of keyboard shortcuts. I tried Basecamp briefly, but they stuffed up the keyboard commands.

When done I save the file to disk as gpx, temporarily remove all non-coloured tracks and save as t.gpx. I then load both into josm, download OSM data as needed and convert t.gpx to an OSM layer, from which I cut and paste the tracks.

I really do hope we can keep this going. Colin is now systematically riding any tracks he can find. This data is accurate and there is lots of it.

Regards,
Peter.

Offline

Board footer

Powered by FluxBB