tordans's Comments
| Post | When | Comment | ||
|---|---|---|---|---|
| Divide and map. Now. | Hi qeef, just in case … do you know https://mappingnorthkorea.com/map / https://github.com/MRVDH/mapping-north-korea which is also a kind of Tasking Manager Tool, but just for north korea. Also a quick feedback: Personally, I am not a fan of the name. It sound negative, which is a bad starting point for something good IMO :-) Best, Tobias |
|||
| Making a simple textual change to the "switch2osm.org" site | Thanks @mmd. The quick-edit-fork-and-PR-flow is really awesome and easy and I was surprised to see it’s a feature since 2011 https://github.blog/2011-04-26-forking-with-the-edit-button/ (but was improved a lot since those screenshots). |
|||
| A Local Mappers API | @mvexel Thanks for this discussion, tool and writeup. I wonder if we are getting at this from the wrong side. OSM already has plenty of tooling to ask for feedback by the local community. But we have next to no tooling to trigger notifications for those questions. As a result, most of the existing feedback goes unanswered. Some examples: Notes on the map I write a note on the map somewhere. Right now no one will notice except by accident or some power user who actively look for it. So ATM, my node will likely be un answered for ages if ever. What is missing? Notifications. Mappers that know the area where I placed the node should get a notification and be able to react to it. There are several ways to solve this – one idea is below. Fixme keys and changeset comments and changeset-review-requested-keys. Same as notes above. I can write them, but no one will notice. We need tooling to get people to notice. Or to make it easier for people to discover them.
So instead of looking for a way to contact “nearby mapper”, why not look for a way to make it easier for mappers to see what is discussed nearby? Contacting nearby mapper has two disadvantages: It’s only 1on1. Or, if you add groups, it’s another layer of communication; which OSM already has too many of (telegram, mail, forum, changesets, nodes, 1on1). Related: I wrote about this as a proposal for a GSOC project. The idea is buried in the changelog ATM, so I will copy it here for reference:
|
|||
| Parking lanes viewer | @acsd I just came across this commercial curb project and though it has similarities to your great micro editor. So FYI some links: - https://coord.co/curbs - https://coord.co/explorer/sf#37.79330700003739,-122.40008303292501@16 - https://medium.com/coord/behind-the-curbs-building-the-curb-map-883bab281feb |
|||
| So how does the Facebook's AI Assisted Road Import Process work? | Thank you for sharing all this details. I found it very nice to read - especially with all those good illustrations/examples. This looks like a great process and great contribution to me. |
|||
| Towards a dedicated public issue tracking/project management system for OSM | This comic sums it up pretty nicely: https://xkcd.com/927/ IMO, the OSM community has more important projects that are closer to its core then replacing Github … |