Weird. Opened an issue in their repo: https://github.com/cyclosm/cyclosm-cartocss-style/issues/695

In any case, there is no harm in being explicit about it if you want.

FYI, cycleway=lane on a oneway road is by default the same as cycleway:right=lane and cycleway:left=no, so it doesn't need correcting

"Des Forêts Avenue" is an English name of this street. French name would be "avenue des Forêts". That's how we name things here. Reverting.

Also `Rock Beach=beach` is not a tag. Return `natural=beach` and give it a name if there is one.

You might want to add `man_made=crane` tag and remove `name=Crane` - such names are discouraged: man_made=crane

Hi, `traffic_signals:direction` is a useful tag on two-way roads. No need to delete it.
traffic_signals:direction=*

"bicycle_parking=bike_rack" tag does not exist. Refer to this page for details on how to map bicycle parking: bicycle_parking=*

OK, nevermind, the tag was removed.

What makes it impassable? Looks good on Bing imagery.

Hi, `highway=pedestrian` is not a good tag for a simple sidewalk. Normally it's used for wide pedestrian streets/squares, etc.

Consider using `area:highway=footway` instead. See more info: area:highway=footway

They should be already set.

Yes, it should be "bus=yes". Let me fix it.

Hi, as far as I understand tag "amenity=police" should be used for public-facing facilities (hence "amenity"): amenity=police

Which makes sense, i.e. someone mugged me, so I look up where is the nearest police station and head there. I don't think you can come to RCMP headquarters if you want to report something.

This looks more like `landuse=institutional` or `landuse=commercial` with maybe some `police`=* tags.

Yeah actually I just checked with the wiki and you are right, the name duplication should be avoided: osm.wiki/Talk:Tag:amenity%3Dschool

My concern was that if you build a route to that school in a routing app, it could route you to a landuse corner that's far away from the actual entrance. But I guess today's routing engines are smarter that that and adding "entraince=main" node should handle that.

As for mapping for the renderer, it's considered to be a bad practice and is frowned upon: osm.wiki/Tagging_for_the_renderer

OSM Data Working Group often reverts such edits.

Hi,

When improving existing features, like buildings, please don't delete existing data. Like in this case you deleted an existing school with address information. It's important for routing/geo location apps.

Also, if you want it to have various levels in one building, use`building:part` tag: building:part=*

Fixed it

Yeah probably you are right. Changed it to `man_made=mast`

It's a known vandal who keeps creating new accounts. Reverted and reported.

Yep, these desire paths should be tagged with "surface=ground/grass" and "path=desire" tags.

Have a look at our tagging guide for more details: https://github.com/BikeOttawa/OSM-Bike-Ottawa-Tagging-Guide#osm-bike-ottawa-tagging-guide

Hi,

Saw you tagging lots of pathways with `bicycle=no`. That's usually not the right tag, since it's supposed to be used on pathways where cycling is not allowed: bicycle=no

As an example, it could be used on sidewalks, or where there are specific signs that ban cycling.

If cycling is not convenient or desireable then it should be tagged with some other tag, for example,
- `bicycle=dismount` if dismount is required
- `smoothness=bad`
- `surface=ground`
Or combination of those. Any good router or map will recognize that and won't recommend taking a route through it.

By tagging a path with `bicycle=no` you are making routing impossible, even if someone could simply walk the bike a few meters, so that's a very bad idea.

If you could revisit some of you recent changesets and make changes that would be great.

Thanks.