ChaireMobiliteKaligrafy's Comments
| Changeset | When | Comment |
|---|---|---|
| 165605152 | Hi! Can you explain the rationale for this change? What is the source of the change? Also, please add meaningful changeset messages. Thanks! |
|
| 165571298 | Also, you removed bicycle connectors (small segments to make sur bicycle can access the footpaths to the train station and park there (using bicycle=dismount footways) |
|
| 165571298 | In Quebec, it is legal to cross the street at any intersection, except when there is a no pedestrian sign. There are none here, so I will need to revert. The fact that it is dangerous or not is not taken into account unfortunately in osm for now and is the respondibility of other tools. Thanks! |
|
| 165564676 | The small segment on Avenue des Bois in Laval should indeed be placement=left_of:3 aligned with geodesic data. I fixed it. |
|
| 165565413 | J'ai mis gift shop (sur leur site, c'est écrit boutique cadeaux) |
|
| 165565413 | shop=yes seems a bit generic. Can we adjust it to something more precise? |
|
| 165296142 | Je comprends, mais il n'y avait aucune norme et ça causait beaucopu de problèmes pour la modélisation, qui utilise OSM de façon soutenue, et souvent pour des projets réels qui sont véritablement construits. Au moins, ici on a une méthode précise et systématique. Je suis ouvert à la discussion, mais pour l'instant, c'est tout ce qu'on a sur le wiki, alors j'ai implanté ce qui était présenté. Si vous voulez en discuter, vous pouvez ajouter vos commentaires dans le wiki/proposal, ou sur le forum: https://community.openstreetmap.org/ |
|
| 165296142 | SVP prendre le temps de bien lire la proposition complète:
|
|
| 165296142 | La section avec un ligne double doit être une seule ligne comme ceci: https://ibb.co/GfxghC8N
Et pour la section du bas, le gore théorique se termine exactement à la jonction, ce qui est exactement comme expliqué dans le wiki: https://ibb.co/wZHN1vXK |
|
| 165296142 | these transitions were following the official wiki on placement=transition. I reverted back the modified mergings. See placement=transition |
|
| 165281639 | This building was already aligned with precise aerial imagery. I will revert. Thanks for your understanding. |
|
| 164753745 | Hi! Please do not realign streets except if you use precise aligned aerial imagery (Bing, ESRI and Mapbox photos are not correctly aligned) |
|
| 164379084 | Hi! In Quebec, we need to use the french name as default (by law). I added the name:en to these nodes to include both languages. Thanks! |
|
| 164104194 | Thanks for your contributions! Please add access=private to private pools. Thanks! |
|
| 164014675 | Hi! Thanks for your contribution! Please add access=private to private pools. Thanks! |
|
| 163643869 | Hi! Thanks for your contributions! Please add the tag access=rpivate to private pool so they are no considered publicly accessible. Thanks! |
|
| 163357607 | Hi! Thanks for your contributions! Please add the tag access=private to private pool since these are not publicly accessible. Thanks! |
|
| 163302643 | Hi! Please write meaningful changset comments so we can understand what this edit was for. Thanks! |
|
| 163262020 | Hi! Thanks for your contribution! However, in Quebec, we prefer having POIs as nodes since it is easier to update and visualize the POIs near their actual entrance instead of on the building centroid. Thanks! |
|
| 162551282 | OK, I agree. However, please help me starting the discussion by stating what issues are to be asked to the community. The use of JOSM instead of the iD editor seems hard to enforce because iD is the official editor, for better and for worse, and it is way easier to use for this kind of work (we can easily change the offset on the fly, and use custom aerial imagery urls and switch between them, which does not always work in JOSM (believe me, a lot of imagery are not loaded correctly in JOSM). I think the main issue here is keeping the history of the ways. However, I do not see how we can fix that or discuss this with the community. Adding a placement=transition to the merging segments will always create a new segment and will delete the existing segment since we need to cut before and after the merging, as well as at each change of number of lanes. I'll let you start the discussion as I am not sure how to introduce the problem exactly. Also, I would like Pierzen to discuss the issue in a videoconference with me because most of the issues would be solved/explained in a matter of minutes when I show the work we do and the reasons why we do it. I willl explain the relation we have with the ministry of transportation, the ministry of natural resources (they manage the aerial photos) and with the transit agencies in Quebec. After that private discussion, we can then create a common introduction for the public discussion. I would like to emphasis here that I did not get any issue from the community regarding this issue in the past except from PierZen (which by the way is a great contributor of OSM in the region), so I am a bit stunned by this... I'm trying to be as efficient and productive as possible. Thanks! |