If you click on a section of the generated route a dialog box will appear allowing you to rate that section's perceived safety on a scale of 1-7, this will affect future generated routes. Also the system tends to prefer residential streets and cycleways over major roads, and prefers roads with bike lanes or signed bicycle routes.

There's a minor technicality that means that the Toronto data is not compatible with OSM (for now):

http://lists.openstreetmap.org/pipermail/legal-talk/2009-November/003017.html

I hope that this gets fixed sooner or later.

I will normally unglue parks and landuse (because the edge of the park is NOT the centerline of the road, because the width of the road is positive), but I usually glue boundaries to the middle of roads/rivers if they follow them precisely.

Generally this is a result of misaligned Yahoo imagery. To align it to GPS press space+arrow keys (in Potlatch) or use the little move WMS button (in JOSM). Usually once the Yahoo imagery is aligned properly, you can rely on it for tracing. In some cases Yahoo is spot on, in other cases it needs a bit of manual adjusting.

I've been mapping sidewalks separately as ways in Toronto too (still many, many more sidewalks to be done though). Haven't got around to mapping them as areas yet though (would need more accurate aerial imagery to do this, such as the Nearmap aerial imagery in Australia). I'd be careful using the crosswalk tag for pedestrian crossings as I normally reserve this for pedestrian crossings with flashing lights activated by the pedestrian (which are very common here).

spam

In many areas Yahoo imagery is more accurate than GPS traces, if the area hasn't changed since the photo was taken and the photo is aligned properly (or is aligned manually to the GPS trace in the editor). Remember that consumer GPS isn't all that accurate. In general, I recommend comparing both sources with what is actually on the ground and using whichever is more accurate.

It would probably take far too much CPU power to be worth running on the tile server.

You can convert non-round roundabouts to round ones by selecting them and pressing "T" in Potlatch.

Since they are a temporary feature, I would be inclined to not bother mapping them.

Looking at the GPS traces there the Yahoo imagery appears to be spot on.

Deleted. OSM is for real data only. Perhaps we should create an unstreetmap.org for fictitious data?

(This is almost certainly copyrighted as well.)

I noticed that the area near Pembroke, Ontario in the northeast of the province is not imported. Is this part of a Quebec tile?

This is the import of the GeoBase National Road Network. Please see osm.wiki/GeoBase_Import for details.

The names on every block are an artifact of the process by which the data was imported. Please do not combine ways to get rid of this as this will delete data which will allow future updates to be added to the GeoBase data. Hopefully a future version of the renderers will be intelligent enough to not show names on every block like this.

Streets from the GeoBase data are not automatically connected to the existing data. This has to be fixed manually - I can start on this if you tell me what area you would like fixed. It is probably easier to do this in JOSM. Furthermore, the data is likely to contain errors, and one way streets are missing.

For more information you should talk to stevens who is doing the bulk of the GeoBase import.

SPAM

Presumably they mean cycleways?

LOL OpenStreetMap does need to "infect" other parts of the world a little bit more.

Just a note of caution - keys and tags are case sensitive, they should not be capitalized. Thus please use "name", not "Name", otherwise your lovely hard work will not show up on the renderer. I have fixed this for now.

Press "c" to add a comment with Potlatch.

I've been tagging hydro corridors (that is the area with the power lines underneath, owned by the electric utility) in Toronto with landuse=grass, name=Hydro corridor. This is probably not the best tagging, but it will do.