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

61–70 of 108 posts

Re: Map Features in OpenStreetMap with Computer Vision

#61

Post by karlgkk »

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)

adding a "created_by" tag is not opt in. it's opt out. you are de facto choosing how OSM volunteers must approach their work, without their consent.

Re: Map Features in OpenStreetMap with Computer Vision

#62

Post by AyyEye »

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)

Can I suggest also adding a tag for ML originated features that's not specific to your demo/app? Maybe this can help put extra eyes on them and/or help prevent them from polluting the DB wholesale. Maybe client apps could have a toggle to allow/reject them.

Re: Map Features in OpenStreetMap with Computer Vision

#63

Post by AyyEye »

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…

Replied to daavoo, can I suggest adding a tag for ML originated features? As other comments have stated, it is likely that these tools are already being used (potentially semi-automatically) and this could help prevent them from polluting the DB wholesale.

Re: Map Features in OpenStreetMap with Computer Vision

#64

Post by timewizard »

IshKebab wrote: post #22
yorwba wrote: post #18

Earlier quoted context omitted.

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

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

#65

Post by stereo »

daavoo wrote: post #16
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.

Hi, thanks for the feedback. I have disabled the hosted demo for now, and will remove the uploading part from the code in favor of showing an URL that will open the editor at the location. If its of any help, you can find any contributed polygon with the tag `created_by= https://github.com/mozilla-ai/osm-ai-helper `. Feel free to remove all of them (or I can do it myself once I access a PC). I will be happy to contin…

Hi, thanks for replying! I was looking at your source code, and wondering how easy it would be to create a .osm file instead of uploading the data. The JOSM editor’s todo list plugin would make it easy to plough through all the polygons or centroids, and do any refinement necessary. For example, I’m curious to try this out to detect crosswalks, and those need to be glued to the highway being crossed.

Re: Map Features in OpenStreetMap with Computer Vision

#66

Post by anakaine »

Id love to see a bit more detail on fine tuning SAM/2 to do things like detect pools or solar arrays. Both these are fantastic things to have mapped for community resilience projects, but I've not been able to follow along with SAM2 fine tuning at all.

I've got a Yolov8 model which does quite a good job of finding and segmenting out solar, but the edges are absolutely horrible and require an insane amount t of work to clean up. I've seen results from SAM2 that has been trained, and the results look massively better.

Wouldn't put these in OSM due to stereo6 comment about accuracy, but I could sure use them elsewhere.

Re: Map Features in OpenStreetMap with Computer Vision

#67

Post by joshvm »

lmc wrote: post #26
daavoo wrote: post #16

Earlier quoted context omitted.

Hi, thanks for the feedback. I have disabled the hosted demo for now, and will remove the uploading part from the code in favor of showing an URL that will open the editor at the location. If its of any help, you can find any contributed polygon with the tag `created_by= https://github.com/mozilla-ai/osm-ai-helper `. Feel free to remove all of them (or I can do it myself once I access a PC). I will be happy to contin…

> I will be happy to continue the discussion on what is a good prediction or not. I have mapped a lot of swimming pools myself and edited and removed a lot of (presumably) human contributed polygons that looked worse (too my eyes) than the predictions I approved to be uploaded. Something else you need to be mindful of is that the mapbox imagery may be out of date, especially for the super zoomed in stuff (which comes…

This is a general problem when trying to compare OSM data with aerial imagery. I've worked a lot with orthos from Open Aerial Map, whose stated goal is to provide high quality imagery that's licensed for mapping. If you try and take OSM labels from the bounding boxes of those images and use them for segmentation labels, they're often misaligned or not detailed enough. In theory those images ought to have the best corresponding data, but OAM allows people to upload open imagery generally and not all of it is mapped.

I've spent a lot of time building models for tree mapping. In theory you could use that as a pipeline with OAM to generate forest regions for OSM and it would probably be better than human labels which tend to be very coarse. I wouldn't discount AI labeling entirely, but it does need oversight and you probably want a high confidence threshold. One other thought is you could compare overlap between predicted polygons and human polygons and use that as a prompt to review for refinement. This would be helpful for things like individual buildings which tend to not be mapped particularly well (i.e. tight to the structure), but a modern segmentation model can probably provide very tight polygons.

Re: Map Features in OpenStreetMap with Computer Vision

#69

Post by cratermoon »

daavoo wrote: post #6
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…

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

[flagged]

Re: Map Features in OpenStreetMap with Computer Vision

#70

Post by throwaway346434 »

Oh, great re swimming pools - solar detection is another one on my list to have a go at.

I feel like a lot of the pushback here is an idea that OSM can grow from hand mapping; but as someone with 60k changesets over a decade... no amount of human volunteer enthusiasm is to the point that it can "solve" mapping at a global scale to the standards that make the map data overwhelmingly useful.

I feel we need a scalable framework for importing and maintaining data: ways to annotate the quality, sources, where to report bugs in the data source, and guidance to consumers. Ie if I want to query "businesses of type X" "mapped by humans within the last year", I can sort of do that with "check date".

But who knows how many of those attributes are accurate, or if the mapper who checked only checked one aspect (name/location)? Would it be better to ingest alltheplaces opening hours to maintain this data automatically, every month?

Would it be better as a data consumer if I could filter to only certain sources I trust? Or I could use data - even if the polygons aren't perfect or similar, even with known limitations like "poi inferred by AI".

Post reply on HN