Those recent format changes don't work, IMO. I was liking how we had sections for things you'd ride on, obstacles you'd encounter, etc. Now it seems all split up... things you'd ride on are showing up all over the place (it starts with MUPs, for example, then there's some stuff about parking, signs, obstacles, and then we're back to another thing you'd ride on - a paved shoulder). Is there some logic to this flow that I'm not getting? I'd really like to see this put back how it was, or maybe I'm just catching this midway through some re-arranging?

Contraflow lane no separation

should have also oneway:bicycle=no tag to mark not only infrastructure type but also one-way status.

Hi! We are currently tagging cycling paths in the Montreal area and we use a width in meters for the cycleway:buffer tag.
In your guide, you tell users it should be a yes/no value instead, but the openstreetmap wiki suggest it would be better to use the actual width. Do you accept both yes or a float for the buffer width in meter?

👍 @heatshear & @zzptichka for contributing so much.

I've been looking at the Markdown document and it's becoming more and more complex as we grow this.

My suggestion would be to move towards a more "human-friendly" format which will compile our defined schemas into a website and README.md.

Using this approach will also allow us to track changes easier since everything will be on multiple lines instead of the single line Markdown approach.

All the "special" formatting like linking the OSM wiki & Mapillary websites can be done in the same process, no need to add the websites directly to in the document.

Using YAML

YAML is a .yml extension which can easily convert to JSON however it's a bit more flexible as a format (JSON is very strict and cannot include comments).

YAML example of schema

For an example of Lanes, we would build these .yml or .json files into the schema folder, another process would grab all of these files and build a website and update the README.md with the changes (we can have a bot do that).

Lanes.yml

MUP:
  title:
    Paved Multi-Use Path (MUP)
  description:
    - Typically 3m wide, may be wider.
    - Intended for mixed bike and foot traffic.
  osm:
    - highway=path
    - surface=asphalt
  mapillary:
    - xvX6Bexu1gEE_H9KlfodLQ

Twinned_Path:
  title:
    Twinned Path
  description:
    - Typically >4.5 m wide.
    - Intended for separated bike and foot traffic
  osm:
    - highway=path
    - surface=asphalt
    - segregated=yes
  mapillary:
    - J5eakBF0yAOttLLsGtnkcg

JSON

Similar to the YAML config, however more quotes and the JSON format is not as friendly to manually edit.

Lanes.json

{
  "MUP": {
    "title": "Paved Multi-Use Path (MUP)",
    "description": [
      "Typically 3m wide, may be wider.",
      "Intended for mixed bike and foot traffic."
    ],
    "osm": [
      "highway=path",
      "surface=asphalt"
    ],
    "mapillary": [
      "xvX6Bexu1gEE_H9KlfodLQ"
    ]
  },
  "Twinned_Path": {
    "title": "Twinned Path",
    "description": [
      "Typically >4.5 m wide.",
      "Intended for separated bike and foot traffic"
    ],
    "osm": [
      "highway=path",
      "surface=asphalt",
      "segregated=yes"
    ],
    "mapillary": [
      "J5eakBF0yAOttLLsGtnkcg"
    ]
  }
}

Seems confusing.
Can be tagged as highway=path with certain surface and smoothness.

This is an excellent guideline! Thank you for sharing.

The only issue (2020-11-29, while I write this ticket), and this is important, is that you are encouraging people to refer to Google Streetview which is disallowed in OpenStreetMap.

The Google Maps/Google Earth (including Streetview) Terms of Service disallows users from using their imagery and data for creating or augmenting any mapping-related dataset. I'll quote the relevant section below:

When using Google Maps/Google Earth, you may not […] use Google Maps/Google Earth to create or augment any other mapping-related dataset (including a mapping or navigation dataset, business listings database, mailing list or telemarketing list)

Checkout the OpenStreeMap FAQ for more information, or refer to What images and maps may I use to make maps from? for details.

Some service strips are pretty good for riding:

• https://www.mapillary.com/app/?lat=45.331216666666705&lng=-75.78252222222221&z=17&pKey=5waNjMfvVUUo44ka4_qjQQ&focus=photo
• https://www.mapillary.com/app/?lat=45.296566900000016&lng=-75.90046540000003&z=17.330991478114377&pKey=lnUCU2is9t5OSznRO7KPFg&focus=photo&x=0.49396536427076826&y=0.5731991480670061&zoom=0

On one hand we shouldn't accept those as legitimate infrastructure so they bump up LTS for that road, on the other hand we should at least tag such segments as an opportunity for the city to convert them to cycletracks like they do now on Heron. Are there any tags we can use?

@heatshear I've included a document how to build the YAML based schema documentation.

https://github.com/osmottawa/OSM-Bike-Ottawa-Tagging-Guide/blob/master/README-build-docs.md

Let me know if you have any issues building the documentation, also let me know if building the YAML schema approach is easier (I think so...).

OSM Bike Ottawa Tagging Guide

How to build Documentation

Install

• Install the LTS or current version of NodeJS.
• Clone/Download Repo to local computer via Clone with SSH or Download Zip.
• Install library's dependencies using npm install.
• Build docs via npm run docs.

Install via CLI

$ git clone [email protected]:osmottawa/OSM-Bike-Ottawa-Tagging-Guide.git
$ cd OSM-Bike-Ottawa-Tagging-Guide
$ npm install
$ npm run docs

I've been editing the readme... index and also contents, trying to put them into a logical order. But, it keeps reverting. I don't know what to do.