Earlier quoted context omitted.
> This will generate a lot of data that volunteers will have to check and revert. This is just not true. The data can be easily identified with the `created_by` tag. And I have been reviewing myself any data uploaded with the demo (with a clear different criteria on what is good enough)
If the upstream project thinks there may be a potential problem with this, that is a problem in itself. Try not to get defensive about it, just pull the project and have another go at the problem in collaboration with upstream. Perhaps parts of the project and be useful for upstream? Perhaps another workflow could make the project better? We all strive for better open data. I upstream feel there is a risk that automa…
Map Features in OpenStreetMap with Computer Vision
91–100 of 108 posts
Re: Map Features in OpenStreetMap with Computer Vision
#92Re: Map Features in OpenStreetMap with Computer Vision
#93Earlier quoted context omitted.
"plow forward" and implying they didn't consider their actions and their effects seem ungenerous, given the list of precautions in the comment you're replying to. You can disagree on whether the measures are effective, of course, but they're clearly not thoughtless.
It was the equivalent of vibe coding: > The polygons the algorithm had drawn were consistently of poor quality with stray nodes and nodes far outside the pool boundaries, and the imports hadn't been discussed with local communities. https://news.ycombinator.com/item?id=43448498
Re: Map Features in OpenStreetMap with Computer Vision
#94Earlier quoted context omitted.
That kind of defeats the point surely?
The point of what? Slamming a bunch of contributions in? Or actually improving the product for end users?
Re: Map Features in OpenStreetMap with Computer Vision
#95Earlier quoted context omitted.
> This will generate a lot of data that volunteers will have to check and revert. This is just not true. The data can be easily identified with the `created_by` tag. And I have been reviewing myself any data uploaded with the demo (with a clear different criteria on what is good enough)
If the upstream project thinks there may be a potential problem with this, that is a problem in itself. Try not to get defensive about it, just pull the project and have another go at the problem in collaboration with upstream. Perhaps parts of the project and be useful for upstream? Perhaps another workflow could make the project better? We all strive for better open data. I upstream feel there is a risk that automa…
Re: Map Features in OpenStreetMap with Computer Vision
#96Earlier quoted context omitted.
If the upstream project thinks there may be a potential problem with this, that is a problem in itself. Try not to get defensive about it, just pull the project and have another go at the problem in collaboration with upstream. Perhaps parts of the project and be useful for upstream? Perhaps another workflow could make the project better? We all strive for better open data. I upstream feel there is a risk that automa…
[flagged]
Re: Map Features in OpenStreetMap with Computer Vision
#97Re: Map Features in OpenStreetMap with Computer Vision
#98Re: Map Features in OpenStreetMap with Computer Vision
#99Earlier quoted context omitted.
If the upstream project thinks there may be a potential problem with this, that is a problem in itself. Try not to get defensive about it, just pull the project and have another go at the problem in collaboration with upstream. Perhaps parts of the project and be useful for upstream? Perhaps another workflow could make the project better? We all strive for better open data. I upstream feel there is a risk that automa…
[flagged]
[0] Most notably: https://wiki.openstreetmap.org/wiki/Rapid
Edit to add: To be clear, they have since taken steps to try to resolve the concerns in question, the discussion is ongoing. I suspect at the end of this we will get a useful tool, it's just off to a rocky start.