Hi Scocasso,

You might be interested in www.cyclestreets.co.uk - it's a site that combines maps and routing for bicycles and covers many of the ideas you have discussed. I think even in your discussion you show that there's too many different types of bicycle path to show every type differently on the map - it would be a confusing mess! Still, as Chillly suggested, you can experiment yourself to see what works or not.

Hi Scocasso,

Refreshing the legend on gravitystorm is on my personal todo list. If you would like to see the legend improved on the main www.openstreetmap.org web site, then please add a ticket to trac.openstreetmap.org and someone may get around to it.

As for why it hasn't been done in all the last two years, it's because I'm often busy with my day job, and there are usually more urgent tasks like trying to keep the cyclemap server running!

If you haven't done so already, you could join the Philippines mailing list ("talk-ph") and ask there too - it's nice keeping in touch with other mappers in the same part of the world.

osm.wiki/Mailing_lists

Go for it, I've always believed that the park boundary is at position A, and the middle of the road is over there a few metres away. It's especially true in London where the parks have walls around them - things get a bit more fuzzy when the "park" hasn't got a physical edge to it.

I cleared a few doubled-up roads just north of there when I added the addressing up NW of Paddington, I'm not sure what the history is around there but looks like someone made a mistake a few years ago. They had Queensway appearing all over the place.

Have a look into http://trac.openstreetmap.org/browser/applications/utils/export/garmincyclemap/preprocess that might help

It's a problem with the coastlines shapefile, I'll have a look at making another one.

Good work David! A brave and hopefully successful decision for you and your company.

osm.wiki/Good_practice says "Don't remove tags that you don't understand". That applies equally well to the warnings from validators - just because they don't understand the tags, doesn't mean they are wrong!

Hi there, I use my digital camera and a Garmin eTrex for mapping - fits on my handlebars, does routing, and shows OSM on the screen. If you're looking for a recommendation of models to buy here is mine: http://www.gravitystorm.co.uk/shine/gps-recommendations

I don't have any recommendations for car sat navs though, I don't have any experience with them.

Guys, it's fine to tag for the renderer, the problem is to not tag incorrectly just because you like the colours. See osm.wiki/Tagging_for_the_renderer

Sounds like you need to add yourself to osm.wiki/Mapping_accidents !

As Richard says, please don't import data based on locations in Wikipedia. It's a pretty well known policy that these are not suitable for OSM.

Or you can do what many of the rest of us do - just draw it by hand! Fairly laborious but the end result is a gold-star quality road.

Hey there - some of us are working on connecting the Interstates across the whole US - properly fixing them up (making them dual carriageways, fixing junctions etc). There's a grid of connected cities at osm.wiki/TIGER_fixup/250_cities - maybe you'd be interested in working on more of them?

Good choice - that's my recommendation at http://www.gravitystorm.co.uk/shine/gps-recommendations !

In TIGER there was only one classification for link roads, and so they all ended up as motorway_link. If you look all around the USA you'll see them sprinkled around all over the place.

Flash isn't a requirement to use OSM - it's just one option, and for most people it's the easiest. I think the only technologies that are required are HTTP and XML, and beyond that you can take your pick of implementations. We've got flash (Potlatch), Java (JOSM), C (osm2go), C++/Qt (merkaator), perl (bulkuploader.pl).......

osm.wiki/Key:phone

Congratulations, well done on achieving this.

Yep, it's easy enough that I can do it!