Re: [OSM-talk] Converting Polish/.MP to OSM?
On Tue, May 6, 2008 at 6:20 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > Hi all, > Is anyone working on any tools to facilitate the conversion of '.mp' to > '.osm'? > Type=0x16 > Label=Yamnuska West Ascent > RoadID=1176 > RouteParam=1,0,0,0,1,1,1,1,1,0,0,1 Do you know what these means? grep -e ^Type Calgary_Area_Trail\ Map_1_13\ 2.mp |sort|uniq -c |sort -gr |head 1617 Type=0x16 257 Type=0x5a00 179 Type=0x6 126 Type=0x4d00 125 Type=0xa 108 Type=0x18 69 Type=0x4 48 Type=0x6401 46 Type=0x6412 36 Type=0x4c removed.. grep -e ^RouteParam Calgary_Area_Trail\ Map_1_13\ 2.mp |sort|uniq -c |sort -gr 1594 RouteParam=1,0,0,0,1,1,1,1,1,0,0,1 172 RouteParam=3,0,0,0,0,0,0,0,0,0,0,0 67 RouteParam=4,0,0,0,0,0,0,0,0,0,0,0 62 RouteParam=4,2,0,0,0,0,0,0,0,0,0,0 53 RouteParam=2,0,0,0,0,0,0,0,0,0,0,0 10 RouteParam=5,3,0,0,0,0,0,0,0,0,0,0 6 RouteParam=0,0,0,0,1,1,1,1,1,0,0,1 5 RouteParam=3,0,1,0,0,0,0,0,0,0,0,0 2 RouteParam=5,2,0,0,0,0,0,0,0,0,0,0 1 RouteParam=3,1,0,0,0,0,0,0,0,0,0,0 1 RouteParam=3,0,0,0,0,0,1,1,1,0,0,1 1 RouteParam=0,0,0,0,0,0,1,1,1,0,0,1 -- /emj ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Mon, May 5, 2008 at 9:20 PM, Simon Wood <[EMAIL PROTECTED]> wrote: > Hi all, > Is anyone working on any tools to facilitate the conversion of '.mp' to > '.osm'? > > I have permission to import some footpaths/trails from this site: > http://www.calgarycachers.net/trailmaps/maps.htm > > I found this, but it seems limited to places and POI's. > http://svn.openstreetmap.org/applications/utils/import/mp2osm/ > > The file I have to work with contains POLYLINES and PIO's, for example. > --- > [POLYLINE] > Type=0x16 > Label=Yamnuska West Ascent > RoadID=1176 > RouteParam=1,0,0,0,1,1,1,1,1,0,0,1 > > Data0=(51.12277,-115.10575),(51.12282,-115.10608),(51.12282,-115.10638),(51.12286,-115.10646),(51.12286,-115.10698),(51.12282,-115.10733),(51.12290,-115.10746),(51.12282,-115.10794),(51.12282,-115.10844),(51.12286,-115.10861),(51.12295,-115.10865),(51.12295,-115.10884),(51.12308,-115.10878),(51.12316,-115.10891),(51.12324,-115.10878),(51.12342,-115.10871),(51.12337,-115.10904),(51.12346,-115.10900),(51.12350,-115.10910),(51.12350,-115.10904),(51.12380,-115.10897),(51.12389,-115.10930),(51.12398,-115.10947),(51.12411,-115.10942),(51.12415,-115.10951),(51.12415,-115.10968),(51.12427,-115.10981),(51.12427,-115.11007),(51.12432,-115.11011),(51.12427,-115.11024),(51.12445,-115.11063),(51.12440,-115.11084),(51.12440,-115.11136),(51.12432,-115.11153),(51.12440,-115.11157),(51.12436,-115.11170),(51.12440,-115.11174),(51.12449,-115.11206),(51.12445,-115.11209),(51.12449,-115.11213),(51.12458,-115.11303),(51.12411,-115.11412),(51.12393,-115.11470),(51.12393,-115.11531),(51.12389,-115.11548),(51.12380,-115.11548),(51.12368,-115.11565),(51.12359,-115.11582),(51.12355,-115.11618),(51.12282,-115.11734) > Nod1=0,2876,0 > Nod2=49,2839,0 > [END] > -- > > Cheers, > Simon > Check out the newest GlobalMapper--it's supposed to have added support for OSM in the newest version, and it already had support for Polish format files (.mp). Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
Nope... it might as well be in Polish ;-) The guy uses this source to make Garmin format GPS maps, so I guess that it's ways of flagging what each polyline represents. If I could just convert the co-ords to something usable I'd be happy, if nobody has any code I'll have an attempt at parsing each poly like into a '.GPX' (or something) and import them that way. Simon On Tue, 6 May 2008 06:32:50 +0200 "Erik Johansson" <[EMAIL PROTECTED]> wrote: > > Do you know what these means? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Mon, May 5, 2008 at 9:32 PM, Erik Johansson <[EMAIL PROTECTED]> wrote: > On Tue, May 6, 2008 at 6:20 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > > Hi all, > > Is anyone working on any tools to facilitate the conversion of '.mp' to > '.osm'? > > > Type=0x16 > > Label=Yamnuska West Ascent > > RoadID=1176 > > RouteParam=1,0,0,0,1,1,1,1,1,0,0,1 > > Do you know what these means? > > > grep -e ^Type Calgary_Area_Trail\ Map_1_13\ 2.mp |sort|uniq -c |sort -gr > |head > 1617 Type=0x16 > 257 Type=0x5a00 > 179 Type=0x6 > 126 Type=0x4d00 > 125 Type=0xa > 108 Type=0x18 > 69 Type=0x4 > 48 Type=0x6401 > 46 Type=0x6412 > 36 Type=0x4c > removed.. > Type is the Garmin GPS object type. See the manual at www.cgpsmapper.com > grep -e ^RouteParam Calgary_Area_Trail\ Map_1_13\ 2.mp |sort|uniq -c > |sort -gr > 1594 RouteParam=1,0,0,0,1,1,1,1,1,0,0,1 > 172 RouteParam=3,0,0,0,0,0,0,0,0,0,0,0 > 67 RouteParam=4,0,0,0,0,0,0,0,0,0,0,0 > 62 RouteParam=4,2,0,0,0,0,0,0,0,0,0,0 > 53 RouteParam=2,0,0,0,0,0,0,0,0,0,0,0 > 10 RouteParam=5,3,0,0,0,0,0,0,0,0,0,0 > 6 RouteParam=0,0,0,0,1,1,1,1,1,0,0,1 > 5 RouteParam=3,0,1,0,0,0,0,0,0,0,0,0 > 2 RouteParam=5,2,0,0,0,0,0,0,0,0,0,0 > 1 RouteParam=3,1,0,0,0,0,0,0,0,0,0,0 > 1 RouteParam=3,0,0,0,0,0,1,1,1,0,0,1 > 1 RouteParam=0,0,0,0,0,0,1,1,1,0,0,1 > -- > /emj > RouteParam is an encoding of attributes of the routable lines. The fields are: Speed (a number from 0-7 for 8 to 128 km/h), Road class (0-4 for "importance" of the road), One way (0 or 1), Toll (0 or 1), and then a series of vehicle restrictions (1 if restricted): emergency, delivery, car/motorcycle, bus, taxi, pedestrian, bicycle, truck. This is actually quite good, that probably means the files are topological and routable, but parsing them is more complicated. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Mon, 5 May 2008 22:20:04 -0600 Simon Wood <[EMAIL PROTECTED]> wrote: > Hi all, > Is anyone working on any tools to facilitate the conversion of '.mp' to > '.osm'? > > I have permission to import some footpaths/trails from this site: > http://www.calgarycachers.net/trailmaps/maps.htm > By the way, I created a user account 'catmp' for the purpose of uploading this data (and as a way of keeping track of it). I also thought it would be polite to add a URL field with a link to his website. He says that he updates about every 3 months, so whatever we do to import it should be able to handle/track changes. Simon. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
Well I've had a stab at this, probably the worlds worst python script but it does work I included 'name', 'attribution', 'catmp-RoadRef', 'Garmin-Type' and 'Garmin-RouteParam' tags where they exist in an attempt to make the nodes/ways trackable/managable with future updates. Is there anything else I should include before uploading any of this? Attached is a small sample (if not email if you're interested in reviewing), Cheers, Mungewell. On Mon, 5 May 2008 22:20:04 -0600 Simon Wood <[EMAIL PROTECTED]> wrote: > Hi all, > Is anyone working on any tools to facilitate the conversion of '.mp' to > '.osm'? > > I have permission to import some footpaths/trails from this site: > http://www.calgarycachers.net/trailmaps/maps.htm > > I found this, but it seems limited to places and POI's. > http://svn.openstreetmap.org/applications/utils/import/mp2osm/ > out.osm.gz Description: GNU Zip compressed data ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Fri, 9 May 2008 00:24:11 -0600 Simon Wood <[EMAIL PROTECTED]> wrote: > Well I've had a stab at this, probably the worlds worst python script but it > does work Cleaned up version added to SVN, browsable here: http://trac.openstreetmap.org/browser/applications/utils/import/mp2osm/mp2osm_catmp.py Supports POI, POLYLINE and POLYGON. Can parse the CATMP stuff without error, but have not uploaded resultant data to OSM yet. Doesn't do anything with the 'Nod[1..]' bits as I couldn't see how to re-open an element in ElementTree to modify it/add the appropriate tag. Cheers, Mungewell. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Tue, May 13, 2008 at 12:08 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > On Fri, 9 May 2008 00:24:11 -0600 > Simon Wood <[EMAIL PROTECTED]> wrote: > > > Well I've had a stab at this, probably the worlds worst python script > but it does work > > Cleaned up version added to SVN, browsable here: > > http://trac.openstreetmap.org/browser/applications/utils/import/mp2osm/mp2osm_catmp.py > > Supports POI, POLYLINE and POLYGON. Can parse the CATMP stuff without > error, but have not uploaded resultant data to OSM yet. Doesn't do anything > with the 'Nod[1..]' bits as I couldn't see how to re-open an element in > ElementTree to modify it/add the appropriate tag. > > Cheers, > Mungewell. > Hey, I haven't had a chance to look at this yet, but I just opened up the input file in a text editor and saw: Copyright=THIS MAP CANNOT BE SOLD I think this is incompatible with our license (commercial use is okay). Is the author/maintainer that gave you permission aware of this? The Nod[1...] bits define the routing nodes--i.e., which points in the Data0 linestring connect to other ways. The first and last points of a way always have these, and more if there are any intersecting points in the middle. For this map, though, it's probably safe to say if the points are at the same spot, they're routing nodes (i.e., it should be represented by only one node in OSM, shared between the intersecting ways). Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
> Hey, I haven't had a chance to look at this yet, but I just opened up the > input file in a text editor and saw: > Copyright=THIS MAP CANNOT BE SOLD > I think this is incompatible with our license (commercial use is okay). Is > the author/maintainer that gave you permission aware of this? I did make it clear that the OSM stuff is CC-SA which allows commerical reproduction, he was happy enough to give permission. Full email exchange is here: http://wiki.openstreetmap.org/index.php/User:Catmp Simon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Tue, May 13, 2008 at 5:36 PM, <[EMAIL PROTECTED]> wrote: > > > Hey, I haven't had a chance to look at this yet, but I just opened up > the > > input file in a text editor and saw: > > Copyright=THIS MAP CANNOT BE SOLD > > I think this is incompatible with our license (commercial use is okay). > Is > > the author/maintainer that gave you permission aware of this? > > I did make it clear that the OSM stuff is CC-SA which allows commerical > reproduction, he was happy enough to give permission. > > Full email exchange is here: > http://wiki.openstreetmap.org/index.php/User:Catmp > > Simon > > Cool, glad you checked that. I assume the maintainer you're working with goes by the user name Ibycus on the Groundspeak forums (I try to do my part to promote OSM there). Or maybe it's Red90? Anyway, I hope I can get my OSM-to-Routable Garmin map converter going soon so we can get these guys to put their efforts into OSM instead! (Geocachers are crazy about free maps.) I'll try to take a look at your file to see if anything else can be added to round it out. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Tue, May 13, 2008 at 12:08 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > On Fri, 9 May 2008 00:24:11 -0600 > Simon Wood <[EMAIL PROTECTED]> wrote: > > > Well I've had a stab at this, probably the worlds worst python script but > it does work > > Cleaned up version added to SVN, browsable here: > > http://trac.openstreetmap.org/browser/applications/utils/import/mp2osm/mp2osm_catmp.py > > Supports POI, POLYLINE and POLYGON. Can parse the CATMP stuff without > error, but have not uploaded resultant data to OSM yet. Doesn't do anything > with the 'Nod[1..]' bits as I couldn't see how to re-open an element in > ElementTree to modify it/add the appropriate tag. > > Cheers, > Mungewell. > Simon, Okay, I finally got around to taking a quick look at your script and your converted data. I don't really know python, but I have a few comments: 1. This import doesn't keep track of the topology (i.e., nodes are duplicated instead of shared between ways which connect). For a nice, routable dataset such as what we're getting here, it would be a shame to lose that. Maybe you could create a hashtable with a mapping from the routing nodes (Nod[1...]) to the OSM node ids, and then refer to that as you're creating the ways (and re-use the OSM ids when you encounter a routing Node ID you've seen before). You might want to just read the entire Data0 line into a string variable and then defer parsing it until you hit the [END] line for that section. 2. You should only be reading the Data0 info, because it has the highest-resolution data (what we want to import). The higher numbers just have lower-resolution data for farther-out zoom. If I'm reading it right, it looks like you're appending all the linestrings from each Data0, Data1, etc. together, which will create a repeated, overlapping series, which is not what you want. 3. It wouldn't take much to explode the "RouteParam" line and assign access, oneway and maxspeed tags to the ways based on that information. I gave you the explanation of the encoding of the RouteParam fields in an earlier email. 4. Similarly, there should be only a few Garmin map types used in this map--it wouldn't take much to translate those to OSM "highway" or whatever tags. There are a bunch of map datasets out there being maintained in the MP or Polish map format, so spending some time to get this script improved could have a great impact later if we get to import some of those other ones. If I get a chance this weekend (not very likely), I'll see if I can improve the script, but if you get to it first, so much the better. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
What a coincidence. Early this week I worked on a python script that converts some mp files to osm. It's simple, but works, and (I think) can be easily extended to support more tags (just add more ifs before processing Data0). It also reuses a node if it already exists. I know you already have a working one, but I hope it's still useful rather than just staying in my harddisk. http://www.nabble.com/file/p17420678/mp2osm_indomapper_20080523.zip mp2osm_indomapper_20080523.zip -- View this message in context: http://www.nabble.com/Converting-Polish-.MP-to-OSM--tp17075621p17420678.html Sent from the OpenStreetMap - General mailing list archive at Nabble.com. ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Fri, May 23, 2008 at 1:29 AM, indomapper <[EMAIL PROTECTED]> wrote: > > What a coincidence. Early this week I worked on a python script that > converts > some mp files to osm. It's simple, but works, and (I think) can be easily > extended to support more tags (just add more ifs before processing Data0). > It also reuses a node if it already exists. > > I know you already have a working one, but I hope it's still useful rather > than just staying in my harddisk. > > http://www.nabble.com/file/p17420678/mp2osm_indomapper_20080523.zip > mp2osm_indomapper_20080523.zip > I didn't reply to the list (I sent it only to Simon), but I committed my updates into SVN. It now preserves the routing graph and interprets the RouteParam and Type into OSM tags. It's here: http://trac.openstreetmap.org/browser/applications/utils/import/mp2osm/mp2osm_catmp.py I don't really have time to work on this anymore, but maybe someone could take the best of both scripts and have one really good version. If nothing else, your version should be committed into SVN so it's available in a central location for future use. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
Hi, I have finally gotten around to uploading some of the Calgary Trails Project data... under the username 'catmp'. I made a slight mod the converter to remove attribution/RoadID on nodes within a way as this was making/will make cleaning up of traces difficult. I think there is a bug with the POLYGON stuff. Look in the Calgary area (BOW RIVER polygons), they are mostly right but 'jump' to nodes not in the original polygon. So it looks like something is up with the 'previously used' node stuff. For example (frigged the name to make it findable in output) --- [POLYGON] Type=0x48 Label=BLOW RIVER Data0=(50.93128,-113.99972),(50.93116,-113.99959),(50.93172,-113.99959),(50.93214,-113.8),(50.93279,-114.00093),(50.93288,-114.00122),(50.93270,-114.00196),(50.93262,-114.00212),(50.93253,-114.00199),(50.93227,-114.00067),(50.93163,-113.0),(50.93150,-113.3) [END]RoadID=1459 --- ends up with nodes --- - yes - yes - no comes from RoadID 1458 - yes - yes - yes - yes - yes - yes - no comes from RoadID=1459 - no comes from RoadID=1459 - yes --- I am not 100% convinced of the tags, apparently the route up Turtle Mountain is 'bicycle=yes'... this is definately NOT the case Don't know whether this is source data problem, or with the parsing of the garmin attributes. Places uploaded: http://www.openstreetmap.org/?lat=49.5908&lon=-114.4056&zoom=14&layers=B00FT http://www.openstreetmap.org/?lat=49.5846&lon=-114.5279&zoom=13&layers=B00FT http://www.openstreetmap.org/?lat=49.3548&lon=-114.2812&zoom=13&layers=B00FT http://www.openstreetmap.org/?lat=49.0474&lon=-113.9209&zoom=13&layers=B00FT (these are revertable/removable quite easily as there are isolated on their own) Way too late to do much more on this tonight (errr.. this morning). Cheers, Simon. blow_river.osm Description: Binary data ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Wed, Jun 11, 2008 at 12:35 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > Hi, > I have finally gotten around to uploading some of the Calgary Trails > Project data... under the username 'catmp'. I made a slight mod the > converter to remove attribution/RoadID on nodes within a way as this was > making/will make cleaning up of traces difficult. > > I think there is a bug with the POLYGON stuff. Look in the Calgary area > (BOW RIVER polygons), they are mostly right but 'jump' to nodes not in the > original polygon. So it looks like something is up with the 'previously > used' node stuff. > > For example (frigged the name to make it findable in output) > --- > [POLYGON] > Type=0x48 > Label=BLOW RIVER > > Data0=(50.93128,-113.99972),(50.93116,-113.99959),(50.93172,-113.99959),(50.93214,-113.8),(50.93279,-114.00093),(50.93288,-114.00122),(50.93270,-114.00196),(50.93262,-114.00212),(50.93253,-114.00199),(50.93227,-114.00067),(50.93163,-113.0),(50.93150,-113.3) > [END]RoadID=1459 > --- > ends up with nodes > --- > - yes > - yes > - no > comes from RoadID 1458 > - yes > - yes > - yes > - yes > - yes > - yes > - no > comes from RoadID=1459 > - no > comes from RoadID=1459 > - yes > --- > > > > I am not 100% convinced of the tags, apparently the route up Turtle > Mountain is 'bicycle=yes'... this is definately NOT the case Don't > know whether this is source data problem, or with the parsing of the > garmin attributes. > > Places uploaded: > > http://www.openstreetmap.org/?lat=49.5908&lon=-114.4056&zoom=14&layers=B00FT > > http://www.openstreetmap.org/?lat=49.5846&lon=-114.5279&zoom=13&layers=B00FT > > http://www.openstreetmap.org/?lat=49.3548&lon=-114.2812&zoom=13&layers=B00FT > > http://www.openstreetmap.org/?lat=49.0474&lon=-113.9209&zoom=13&layers=B00FT > > (these are revertable/removable quite easily as there are isolated on their > own) > > Way too late to do much more on this tonight (errr.. this morning). Cheers, > Simon. I don't think I did much of anything with the polygon part--I mostly focused on the polylines. I'll look into it but I'm not sure that I'll be able to get to it right away. As for the bicycle=yes, I'll double-check the parsing but I suspect it's a problem with the source data. Part of the issue is that if it's not marked as restricted/forbidden in the .mp file, then I had to assume that meant "yes". Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] Converting Polish/.MP to OSM?
On Wed, Jun 11, 2008 at 6:44 AM, Karl Newman <[EMAIL PROTECTED]> wrote: > On Wed, Jun 11, 2008 at 12:35 AM, Simon Wood <[EMAIL PROTECTED]> wrote: > >> Hi, >> I have finally gotten around to uploading some of the Calgary Trails >> Project data... under the username 'catmp'. I made a slight mod the >> converter to remove attribution/RoadID on nodes within a way as this was >> making/will make cleaning up of traces difficult. >> >> I think there is a bug with the POLYGON stuff. Look in the Calgary area >> (BOW RIVER polygons), they are mostly right but 'jump' to nodes not in the >> original polygon. So it looks like something is up with the 'previously >> used' node stuff. >> >> For example (frigged the name to make it findable in output) >> --- >> [POLYGON] >> Type=0x48 >> Label=BLOW RIVER >> >> Data0=(50.93128,-113.99972),(50.93116,-113.99959),(50.93172,-113.99959),(50.93214,-113.8),(50.93279,-114.00093),(50.93288,-114.00122),(50.93270,-114.00196),(50.93262,-114.00212),(50.93253,-114.00199),(50.93227,-114.00067),(50.93163,-113.0),(50.93150,-113.3) >> [END]RoadID=1459 >> --- >> ends up with nodes >> --- >> - yes >> - yes >> - no >> comes from RoadID 1458 >> - yes >> - yes >> - yes >> - yes >> - yes >> - yes >> - no >> comes from RoadID=1459 >> - no >> comes from RoadID=1459 >> - yes >> --- >> >> >> >> I am not 100% convinced of the tags, apparently the route up Turtle >> Mountain is 'bicycle=yes'... this is definately NOT the case Don't >> know whether this is source data problem, or with the parsing of the >> garmin attributes. >> >> Places uploaded: >> >> http://www.openstreetmap.org/?lat=49.5908&lon=-114.4056&zoom=14&layers=B00FT >> >> http://www.openstreetmap.org/?lat=49.5846&lon=-114.5279&zoom=13&layers=B00FT >> >> http://www.openstreetmap.org/?lat=49.3548&lon=-114.2812&zoom=13&layers=B00FT >> >> http://www.openstreetmap.org/?lat=49.0474&lon=-113.9209&zoom=13&layers=B00FT >> >> (these are revertable/removable quite easily as there are isolated on >> their own) >> >> Way too late to do much more on this tonight (errr.. this morning). >> Cheers, >> Simon. > > > I don't think I did much of anything with the polygon part--I mostly > focused on the polylines. I'll look into it but I'm not sure that I'll be > able to get to it right away. As for the bicycle=yes, I'll double-check the > parsing but I suspect it's a problem with the source data. Part of the issue > is that if it's not marked as restricted/forbidden in the .mp file, then I > had to assume that meant "yes". > > Karl > Okay, it was a one-line fix. I wasn't clearing out the routing nodes so the polygons were trying to reuse nodes from previously parsed roads. It's checked in to SVN. As far as Turtle Mountain, it's in the source data, so apparently someone thought bicycles were okay (at least not restricted). Don't forget bicycle can include mountain bike, too. I think there may be some proposals about distinguishing between them, but in any case there's not enough information in the source data to make that distinction. Karl ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
