Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Map Features in OpenStreetMap with Computer Vision

blog.mozilla.ai

Post reply on HN
Print view View original

31–40 of 108 posts

Re: Map Features in OpenStreetMap with Computer Vision

#31

Post by mtmail »

qwertox wrote: post #29

Google would not allow this, but Mapbox seems to be OK with this, if it is used for non-commercial purposes or OSM, and only if their satellite data is used (not their vector data): 1.6. No Tracing, Deriving, or Extracting. Customer shall not trace or otherwise derive or extract content, data and/or information from the Service Offerings except that Customer may use Studio or third-party software to trace Mapbox Maps…

Bing also allows OpenStreetMap mappers to use their aerial imagery for tracing. https://wiki.openstreetmap.org/wiki/Bing_Maps#Aerial_imagery

Re: Map Features in OpenStreetMap with Computer Vision

#32

Post by hgomersall »

halosghost wrote: post #11
daavoo wrote: post #6

Earlier quoted context omitted.

> But we still need human intervention to make sure the detected objects are drawn correctly. Hi, I am the author. The demo app and any provided code example includes a step asking a human to verify the detected features. You can't upload them automatically unless you modify the source code. I reiterate the human verification across the docs, linked post, and any code samples. I haven't ever uploaded features automat…

I am afraid your “human in the loop” isn't [0]. You acknowledge the problem of AI slop up-front, but seem to have chosen to plow forward anyway. Please do consider your actions and their effects carefully [1]. You are in a position of potential influence; try not to squander it. All the best, -HG [0]: https://pluralistic.net/2024/10/30/a-neck-in-a-noose/ [1]: https://web.cs.ucdavis.edu/~rogaway/papers/radical.pdf

Tracing satellite data is really boring to do but easy to check. I would describe AI acting as a centaur here, or perhaps a pairing of equals.

Re: Map Features in OpenStreetMap with Computer Vision

#33

Post by stereo »

boredpudding wrote: post #15
stereo wrote: post #13

Earlier quoted context omitted.

Hi! The Data Working Group had a look at the data, and decided to revert the two pool changesets. 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.

Can you link the (now reverted) changesets? I can't seem to find them.

https://www.openstreetmap.org/changeset/163855992 and https://www.openstreetmap.org/changeset/163863954 are the ones I've reverted. There are more in daavoo's changeset history.

Re: Map Features in OpenStreetMap with Computer Vision

#34

Post by [deleted] »

daavoo wrote: post #27
boredpudding wrote: post #21

Earlier quoted context omitted.

I don't understand the 'human verification' aspect. Your docs show a simple image where the user can choose to keep a new object or not. [0] Afterwards it says: "The ones you chose to keep will be uploaded to OpenStreetMap using upload_osm.". This is uploading features automatically. The fact that it asks 'are you sure' is just silly. We all know if humans have to click yes 90% of the time, and no 10% of the time, th…

> 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)

[deleted]

Re: Map Features in OpenStreetMap with Computer Vision

#35

Post by benatkin »

Vinnl wrote: post #12
halosghost wrote: post #11

Earlier quoted context omitted.

I am afraid your “human in the loop” isn't [0]. You acknowledge the problem of AI slop up-front, but seem to have chosen to plow forward anyway. Please do consider your actions and their effects carefully [1]. You are in a position of potential influence; try not to squander it. All the best, -HG [0]: https://pluralistic.net/2024/10/30/a-neck-in-a-noose/ [1]: https://web.cs.ucdavis.edu/~rogaway/papers/radical.pdf

"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

#37

Post by K2h »

yorwba wrote: post #18
daavoo wrote: post #6

Earlier quoted context omitted.

> But we still need human intervention to make sure the detected objects are drawn correctly. Hi, I am the author. The demo app and any provided code example includes a step asking a human to verify the detected features. You can't upload them automatically unless you modify the source code. I reiterate the human verification across the docs, linked post, and any code samples. I haven't ever uploaded features automat…

> Happy to hear and implement any ideas on how to improve the process to prevent automated features to be uploaded. Idea: do not automatically create features that a human can simply approve, instead require them to draw the polygon themselves.

long time editor of osm here. what you describe is what the rapid [1] editor from meta does where user is forced to manually select objects overlayed sat imagery. is limited to 50 objects before user must push. a great method i think

[1] https://rapideditor.org/

Re: Map Features in OpenStreetMap with Computer Vision

#40

Post by banana_dick_1 »

stereo wrote: post #4

Hi from the OpenStreetMap Foundation. Please don't add AI-detected features directly to the database. The algorithms have problems with false positives, and with mapping straight or rectangular objects as wobbly, as shown in the second-to-last screenshot. As a helper to detect missing features, this is a precious tool. But we still need human intervention to make sure the detected objects are drawn correctly. See als…

[flagged]
Post reply on HN