Live data from Hacker News

Map Features in OpenStreetMap with Computer Vision

blog.mozilla.ai

91–100 of 108 posts

Re: Map Features in OpenStreetMap with Computer Vision

#91
post #84
post #27

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…

Mozilla engineers think they are way better than the rest of us though. Don’t need to follow the same rules.

Re: Map Features in OpenStreetMap with Computer Vision

#93
post #12

Earlier 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

That too seems an ungenerous characterisation, and the GP could not have deduced that from the OP. I'm glad the author is constructively incorporating criticism and working to turn this into a useful tool that OSM users will benefit from, because they wouldn't have been the first to get overly defensive after their work was interpreted in the worst light possible.

Re: Map Features in OpenStreetMap with Computer Vision

#94

Earlier 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?

Adding missing features. I'm pretty sure if users are searching for swimming pools they'd rather have a swimming pool with slightly bent sides than none at all.

Re: Map Features in OpenStreetMap with Computer Vision

#95
post #84
post #27

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…

[flagged]

Re: Map Features in OpenStreetMap with Computer Vision

#96
post #84

Earlier 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]

The "good reason" is that OSM is supposed to contain real data, not wobbly AI guesswork data.

Re: Map Features in OpenStreetMap with Computer Vision

#99
post #84

Earlier 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]

The OSM community has had extremely clear rules around automated edits for most of its existence. Every experienced mapper has seen first-hand the sorts of problems they can cause. The fact that it's using AI in this instance does not give any sort of exception to these rules. To emphasize, there are already AI-assisted tools that are allowed,[0] this isn't a blanket application of "no AI ever," it's about doing so properly with the right community vetting.

[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.

Post reply on HN