CUculi·Mar 4, 2026
Everydoor's UI is also quite nice for this. it even lets you enter in the orientation quite easily
https://every-door.app/
https://github.com/Zverik/every_door
In An interactive map of Flock CamsZverik
every_door
Dart2022–2026
Zverik / every_door
every_door
A dedicated app for collecting thousands of POI for OpenStreetMap
4Distinct people
7Mentions
0Explicit recommenders
568GitHub stars
What to know before exploring
What it is
A dedicated app for collecting thousands of POI for OpenStreetMap
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2022-10-25 06:39:40 UTC to 2026-03-04 21:56:45 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesThanks for the great answer. Based on what I'm reading scraping a business website is probably fine in general but using data from Google Maps/Yelp/etc is generally not gonna fly.
What I think could work is if everydoor allows you to create notes with photos (https://github.com/Zverik/every_door/issues/184) then it would be pretty easy to later go back and drop those photos into an AI tool and extra websites and try to create some tags for review. Could also work with Streetcomplete but there it's not easy to see if a POI already exists.
In any case, I might experiment with this idea further.
Some very basic testing shows me that Claude 3.5 Sonnet is pretty great at taking a photo of a menu turning it into decent tags.
So if I could run around taking photos of menus and the outside of businesses then quickly turn them into tags later that
Read the rest
would be a nice workflow for me (and hopefully others).
Every Door 4.0 is released with improved GPS and Mapbox Imagery
34 points · Open discussionYes, I agree that data balkanization represents a significant hindrance for further development of openstreetmap. Fifteen or so years ago I was experimenting with importing DEM files from the US into Blender for landscaping, and finding the data was frustrating. Sometimes the data was available at a state website, other times at a federal website, sometimes also available on the website of some mapping program/project. Surveys within a given geopolitical constraint would be found on the website of whichever department provided the funding. I understanding that, even if ignoring legal realities, merging this data into a single "ground" (heh) truth would be a herculean task, scientifically. But there was no common database or delivery method. Some departments would link to FTP sites, other would provide arcgis downloads via an interactive w
Read the rest
eb tool. I'd have to depend on user-maintained blog posts to even find the data. And the best data was always locked away behind secure portals that I couldn't get access to.
Nowadays openstreetmap is running into the same problem at the municipality level. In the US, if I understand correctly, publicly-funded geographic surveys are under copyright to whichever governing entity and not eligible for import into openstreetmap.
Take for example the excellent app Every Door (https://github.com/Zverik/every_door) with a focus on easily adding building information. In the US, openstreetmap has no address information. Either that or very little address information - but none in my area. So it'd be easy for me to add building nodes with house numbers but I won't be doing that. Not only is it a massive commitment, but the data is already available at openaddresses.io. The catch? It's "probably" license-compatible with openstreetmap. Before merging, all that data would have to be reviewed by a team of lawyers. That's not something a software developer can help with.
In existing threads here, a top complaint about OsmAnd is that lack of address information. Try planning a route without addresses, and without constantly switching to Google Maps to convert addresses to coordinates. Not very user friendly! Opensupermaps (https://github.com/pnoll1/osmand_map_creation) is a user-maintained merge of openstreetmaps and openaddresses.io, but it doesn't integrate with OsmAnd's data update system.
And that's how data balkanization is breaking openstreetmap, right now.
You can download APKs from GitHub, and they're working on F-Droid inclusion: https://github.com/Zverik/every_door/releases
In Every Door – OpenStreetMap editor for POIs and entrancesBecause it's relatively new, so still being worked on: https://github.com/Zverik/every_door/issues/167
In Every Door – OpenStreetMap editor for POIs and entrancesNote also that Every Door is relatively new, so they're still working on adding it to F-Droid: https://github.com/Zverik/every_door/issues/167
It's been submitted though: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/11955
In Every Door – OpenStreetMap editor for POIs and entrances