[HN Gopher] Every Door - OpenStreetMap editor for POIs and entra...
___________________________________________________________________
Every Door - OpenStreetMap editor for POIs and entrances
Author : PetitPrince
Score : 115 points
Date : 2022-10-24 16:17 UTC (6 hours ago)
(HTM) web link (every-door.app)
(TXT) w3m dump (every-door.app)
| donalhunt wrote:
| I suspect Every Door will become one of the top 3 editors for OSM
| in the near future.
|
| I've been using it a lot since State of the Map 2022 for data
| capture. There are some many low hanging fruit to capture that
| its really efficient to improve coverage with minimal effort.
|
| It does of course help to know the data model and tag guidance
| well for the amenities / data you are capturing. But there are
| opportunities for novice mappers too.
| ygra wrote:
| It helps that Every Door builds on the presets of iD, which are
| localized well and can often easily be found with searching,
| even by novice users. For me it has replaced OSM Go! as the app
| of choice for quickly adding details or changing a few things
| when outside.
|
| For very novice mappers that don't want/need to add new
| elements, StreetComplete is probably still the best way to
| start out, at least if you're on Android.
| berkes wrote:
| The OSM datamodel still revolves around a single datafile
| containing all data. At most it can be chopped up
| intogeographical bounded areas: the entire file for a country,
| state, city or neighborhood.
|
| So, while I applaud and love micromapping (every door, bench,
| manhole or street lamp) it no longer scales.
|
| There are great apps to map every single tree, speed bump, lamp,
| bycicle stand, surface, roof and such. All great apps. All data
| accumulating in a still rapidly growing datafile.
|
| OSM really could use a form of layering. Especially when great
| apps like these here take off. So that users of the data can
| extract relevant data without having to parse giga, or terabytes
| of XML or PBFs.
| SnooSux wrote:
| > terabytes of XML or PBFs.
|
| I have a snapshot of all of OSM for a given date (conveniently
| called planet-XXXXXX.osm.pbf) and the compressed version is
| 62GB. And the format is optimized for reading certain chunks
| (as well as updating with new data). Plus there are libraries
| that do the heavy lifting for you in little time at all.
|
| The size is really not as big of an issue as you think it is.
| simlevesque wrote:
| The planet file is currently 120GB for the plaintext.
|
| https://planet.osm.org/
| lukeqsee wrote:
| No one uses the plain text, though. Every tool I have used,
| uses the PBF. (I run a company built on OSM, so that's a
| lot of tools.)
| simlevesque wrote:
| I know. I was just saying that because the person before
| said the plaintext was "terabytes".
| teraflop wrote:
| > The OSM datamodel still revolves around a single datafile
| containing all data.
|
| You could make an argument that this is not true: at an
| implementation level, the more _fundamental_ OSM data model is
| a really big PostGIS database, which has the appropriate
| indexes to let you query whatever subsets you want.
|
| The big flat-file XML/PBF dumps are just one way that this data
| is exposed. You can also query the API for objects within a
| bounding box (and thereby benefit from the DB indexes), or you
| can use the daily/hourly/minutely incremental diffs to run your
| own database replica.
| pietervdvn wrote:
| No. OSM could _not_ have grown this big if we had layered
| everything. Far from it - the big power of OSM is the
| integration of all those 'layers'.
|
| Furhtermore, layering would needlessly complicate everything.
|
| Take a railway crossing for example. Should it go in the layer
| "railways", in the layer "roads" or in the layer "railway
| crossings"? Should we make a new layer for paths, so that they
| are separate from car-only roads? What if something changes?
| How should an object be moved from one layer to another?
|
| What with benches that double as a piece of artwork? What about
| this place that is a boardgame shop, a cafe and a social
| project for mentally disabled people?
|
| What if a river doubles as administrative boundary?
|
| If you want to extract data that is relevant for you, there is
| overpass-turbo.eu for this, where you can write a precise query
| and only get and download the data you need.
| bragr wrote:
| > 100% OpenStreetMap editor with no dependencies on third-party
| endpoints.
|
| Except the mandatory Android or iPhone you need to install the
| app.
|
| I was actually really excited to give this a try, maybe annotate
| some local areas, but I'm not switching over to my phone to try.
| I really don't understand this trend of making multi-platform
| apps that can't also be webapps. If you passed the Apple UI
| review for this to be approved for iPads, then from a UI
| perspective, why can't this run in a browser?
|
| <insert old man yelling at clouds>
| krzyk wrote:
| But this is an app to use when on foot, laptop or desktop is
| not that usable when you are walking - and doesn't have a GPS
| usually.
|
| If you want to edit OSM at home you have many other options.
| ezfe wrote:
| If you're on desktop, openstreetmap.org has a full editor that
| can do all of these things. That editor doesn't work on mobile
| (at least, not practically speaking) so there's only really a
| need on mobile.
| pietervdvn wrote:
| Feel free to try out mapcomplete.osm.be instead - you'll find
| some fun micromapping there as well!
| myself248 wrote:
| Aye. While plenty of desktop editors exist, having the same UI
| on desktop and mobile would be valuable, especially for someone
| learning before they set out on foot.
| teddyh wrote:
| How is this different from StreetComplete, which is on F-Droid,
| and seems to be the same thing, but for _everything_ instead of
| just "POIs and entrances"?
| xwx wrote:
| Every Door and StreetComplete seem to do different things, with
| a bit of overlap.
|
| StreetComplete works by asking you for more details about
| certain things that are already on the map. It seems like Every
| Door doesn't ask you specific questions but lets you add any
| details you like, and also add new points to the map, which
| StreetComplete doesn't let you do.
|
| StreetComplete is meant to be usable by a complete novice.
| Every Door looks like it's for mappers who already have a bit
| of an idea of what's going on and want more control over what
| they can add to the map.
| PetitPrince wrote:
| > StreetComplete is meant to be usable by a complete novice.
| Every Door looks like it's for mappers who already have a bit
| of an idea of what's going on and want more control over what
| they can add to the map.
|
| I just discovered this app today; that's my understanding as
| well. It's also easier to all kind of nodes; with
| StreetComplete we're limited to add shops with the dedicated
| overlay.
|
| Also, compared to my previous editor of choice to add nodes
| (OSM Go!), it seems to offer a better source of background
| imagery. I can actually my local government imagery source
| (swisstopo) instead of mapbox.
| mfsch wrote:
| StreetComplete has actually been adding a new feature called
| "overlays" recently, which let you switch the map to a
| special mode for editing a certain class of features. The
| upcoming version 48 has an overlay for shops and street
| addresses, which might cover much of what Every Door is
| aiming at:
| https://github.com/streetcomplete/StreetComplete/releases
| [deleted]
| habi wrote:
| It runs on iOS, too.
| myself248 wrote:
| Micro-mapping manholes and benches seems like something that
| would really benefit from the precision of RTK/PPP GPS. The
| built-in GPS provider in my phone is absolutely not up to the
| task.
|
| Suppose I have a bunch of hardware sitting around, a base/CORS
| reference, etc. Is there an accepted best-practice way to pipe it
| into my phone to let this app use it? Or to take logs in my
| backpack and post-align the data when I get home?
| AlphaWeaver wrote:
| On Android, in Developer Settings, it's possible to register an
| app as a Mock Location provider. I'm not sure the interface
| your app needs to surface to show up in that list for
| selection, but in theory that API existing means there's a
| potential path for this.
|
| Your app could interface with more accurate external sensors,
| and then set the phone's GPS fix to be what the sensors read.
| Assuming that the issue is lack of accuracy at the sensor level
| and not lack of precision at the software / API level.
___________________________________________________________________
(page generated 2022-10-24 23:00 UTC)