Hacker News

I was curious what they're currently sponsoring; here's another neat OSM project: https://osm2world.org/demo/?lat=52.5239396&lon=13.4104859&ra...

The current demo doesn't seem to cover many places worldwide, but what is there is really neat! To me this already looks better than modern city sim games, because they never seem to get the scale right, among other things.

Not sure what's stopping them from covering more places, since the idea presumably is to generate these tiles from existing OSM data. And in fact one of the easiest things to do with StreetComplete is add the height and type of a building.

More like: thank you German taxpayers. You are very generous for funding stuff like this for the benefit of the entire world.

This is great! I wish more knowledge bases realized their barrier to entry. Eg even Wikipedia can be scary to edit the first time, if you want to present things like citations the right way.

This has been the most controversial quest in StreetComplete for a while. Following several discussions about it, I have now removed it for the upcoming version (i.e. v64.0).

Just tag POI, they get stale so quickly. Everybody wants to tag the roads, but the real gap in many places is stale POI, or missing tags like opening hours. You'll get much less attention from these gatekeepers there too

It’s tricky and maybe locale specific. A lot of roads near me have no pavement. You have to anticipate pedestrians, cyclists and horses on the road. Not at the same frequency as motor vehicles but not completely out of the ordinary.

Aren't there many places where a highway with no sidewalk is the only walkable option? So if someone saw your not-walkable, they might think not walkable at all.

Seems like you guys had two different perspectives, both arguably right. Maybe it needs to be split into technically-walkable and comfortably-walkable layers.

I actually feel better about making edits if I know people may revert them. I don't have the time or interest to dig in deeply to what exactly they want, so I normally wouldn't contribute. But if I know people double check and fix mistakes, I'm more likely to try and be helpful with the app.

It's not pedantic, it's just the way it is. For OSM to be valuable it needs to be consistent. There are many tags available but the "you can't walk here" tag is about whether you have a right to walk there. There are many highways you wouldn't want to walk on, but there are other tags to indicate that, like speed limit and presence of footpaths etc.

If you were using StreetComplete I don't think you would have run into that. StreetComplete is very beginner friendly, and I don't think you can use it to mark a road as prohibiting pedestrians (which, as you discovered, is easy to get wrong if you don't understand what you're doing). You can use StreetComplete to mark whether there's a sidewalk or not, but I don't think anyone would object to you marking roads without sidewalks as not having a sidewalk.

Thanks. If anyone from StreetComplete is watching - please put the TestFlight link prominently on your page!

Indeed, I've been following the issue since it was mentioned here last time and was positively surprised about how quickly they progressed and got the first version shipped.

Every Door has a very confusing UI (lots of unlabeled buttons with unclear icons), unfortunately. I would love to use it, but even the web-based iD editor is so much easier to figure out!

You can choose the type of questions you want to get asked about in StreetComplete. If you want to only enter store names and timings, then go into Settings and pick those.

Have you tried out the Things or Places overlay? Second button from the right at the top, looks like a cake.

StreetComplete, as indicated by it's name, is about street data. Both are for contributing to OSM, but they are for different parts of OSM

There is an undo button on the lower left corner of the screen. Try it!

(It only shows edits made in the last 24 hours IIRC, but this limit is chosen quite arbitrarily. If there is a use case for it, it can be extended.)

If you go to the OSM website, you can sort of get list of all your modification by date in your profile: https://www.openstreetmap.org/user/YOUR_USERNAME

you can revert immediately in bottom left corner of StreetComplete, click on little revert arrow

> I think 70% would be better

You can actually split the road into multiple segments and answer each separately if you don't mind the extra effort. I think there should be something like "differs along the way" button which then asks you to pick a point where to cut.

It takes a bit of practice, but I got it to work after a few tries.

Overall, my experience has been pretty smooth. Just look at how little platform specific code is found in the streetcomplete repo and how straightforward these connect with the common code.

Or maybe I have been using it too long so that I don't notice the awkward bits anymore.

Any specific parts you are after?

I've been building https://maplibre.org/maplibre-compose/ in my spare time for the past two years and helped with this port; happy to answer any questions you have about KMP or CMP

Generally, I'm very happy with the platform and it's only gotten better over the past couple years I've been deep in it.

Yes, to be more specific, every tool like this has benefits offered and then taxes to be considered. For example, what's the tax for:

- Maintaining a significant new moving part in the dev process. KMP updates, management, integration, futures awareness, this all takes non-zero time.

- If an iOS dev wants to work on a KMP project what's the ramp up time? How much less efficiently can they contribute compared to a pure native app?

- How much time is spent on problems, bugs, issues, related to KMP. This is guaranteed non-zero for any tool.

- Is there less benefit to KMP with coding agents? Previously with two native apps, a bug fix had to be done twice. Currently, say a fix in done on Android, it's quite easy to say "propose an equivalent fix for the iOS repo". I do not claim this removes all benefits of a single code base, just that some things are not as bad now.

It’s very confusing to me too. I clicked an icon to see what it was, and it was opening times of a supermarket, which I had no idea about. But I couldn’t find a way to just get back to where I was before. My workflow now is to keep force killing the app frequently when I get stuck.

Most of the time you can leave a note. Do you get an "Uh..." option?

I click a quest and answer it but the app seems to be stuck on that quest and I can't figure out how to get back to all of the quests available near me. Is that a common experience?

That's when you hit "uh..." and leave a note with details. In an effort to keep things simple on a small screen it doesn't include every possible option. You can read the wiki to find the best way to tag it. https://wiki.openstreetmap.org/

Yeah, dismissing a question I don't see an answer for right now easily is the worst. I think swiping the app closed is the easiest way out.

OpenStreetMap is a database, not a map application. The map on the official openstreetmap website is more of a demo to show some of the data. There are many different map apps that use OpenStreetMap data though.

https://cartes.app is trying to do this. OsmAnd is quite usable as well.

For navigation there's Magic Earth (can route around traffic jams), TomTom, and Scenic. OsmAnd can also do routing.

Partly, with Organic Maps or CoMaps.

However, in my opinion TomTom (https://play.google.com/store/apps/details?id=com.tomtom.spe... or https://apps.apple.com/us/app/tomtom-maps-traffic/id14381065...) is still the best way to use OpenStreetMap for navigation since it combines OSM data with their own real time traffic information without dark patterns or asking for an account like Waze or Maps do.

For the web, I personally like https://osmapp.org

https://cartes.app I can also recommend.

Both projects have a similar goal, to offer a more useful UI around using an OSM based map.

There's also OsmAnd for mobile.

You can swipe back on the bottom sheet for now. It's a known issue and is being worked on!