• URL: https://osmapp.org
• Full changelog: https://github.com/zbycz/osmapp/releases/tag/v1.7.0

OsmAPP is the one integrated app for OpenStreetMap ecosystem for both web and mobile. It should be as easy to use as Google Maps, but fully open-source using all the great services around. It was first aimed at broad public, but now it becomes apparent, that it works best for the OpenStreetMap contributors, who want better UX or share OSM around.

Special thanks to all our 6 contributors in this release. 🎉

The new Relation editor

The main feature of this release is the reworked Edit dialog with the new Relation editor. That took a lot of work and refactoring. Now if you click (or create) a relation, you can browser through its members and its parents and easily edit metadata accross whole hierarchies.

It is the most useful on hierarchies like the climbing=area, climbing=crag and routes (example here), but it is written in general manner and can help OSM contributors in unexpected ways.

… See full entry

• URL: https://osmapp.org
• Full changelog: https://github.com/zbycz/osmapp/releases/tag/v1.6.0

For those who doesn’t know, OsmAPP is trying to be the one integrated app for everyday use which runs both on web and mobile. It should be as easy to use as Google Maps, but fully open-source with privacy in mind. We still have a way to go, but we are going stellar. 🌠🔥🍾

First we have great news to share – we are thrilled to welcome @Dlurak to the core team! 🎉 His persistence, focus on code quality and dedication to bringing open maps to public earned him a place in project maintainers. In this release he proved himself as a top contributor and also took care of other people’s PR. Thank you @Dlurak! ♥️

Release 1.6.0 sums up almost 3 months of great changes by @kudlav, @amenk, @j9d3it and also from the core team @dlurak, @jvaclavik and @zbycz.

Directions. Finally! 🚶 🚴 🚗 🚀

This was the plan from the beginning of the project. Issue #31 from summer 2021 speaks for itself. The problem was, it seemed too easy. It is not challenging enough to use some API and write a line on the map 😅.

In the end, the challenge was designing the directions form. First trials with expanded Search input were catastrophical and salvation came from AI. The v0 tool by Vercel lets you chat with GPT and get the code in any framework. You can check our results here: https://v0.dev/chat/3MwraSQEqCc

Second challenge were the form interaction and persistence. React is one-way sync by design, and synchronizing the Autocomplete inputs to URL was tricky.

But it went well in the end, and thanks to our valued core team, we got also driving instructions and beatiful start-end markers. And yes, we hear you - there are also open PRs for multiple stops and turn-by-turn navigation. Stay tuned! 🤞 🔮

Big shout out also for @karussell from GraphHopper to proactively offer us bigger limits for API usage. ❤️

SearchBox is becoming omni-box 🔎

Did you know, you can use Overpass API in OsmAPP?

… See full entry

URL: osmapp.org

For those who doesn’t know, OsmAPP is trying to be the one integrated app for everyday use which runs both on web and on mobile. It should be as easy to use as Google Maps, but fully opensource with privacy in mind. We have still some way to go, but it is getting much better recently.

Release 1.5.0 brought some great changes from wonderful contributors @Dlurak, @amenk, @loviuz and also from the core team @jvaclavik and me. See https://github.com/zbycz/osmapp/releases/tag/v1.5.0

In search of Opening Hours Editor

Opening hour widget was something I wanted to do for a long time. It always seemed as a big task, until I read a message from user @Mapspot on the OpenStreetMap Discord server: “A little 2x7 text box interface where you type the opening/closing time for each day would typically suffice”. What could be so hard about 2x7 boxes, right?

My first requirement was, that I cannot ruin existing advanced opening_hours. That meant, that I have to parse the value in my intermediate objects, then build the text again, and if it doesn’t match, lets tell user, that they should better use YoHours :-) This also brought some challenges, that Editor should be shown even when original text was Sa,Su ..., but after parsing it becomes Sa-Su ....

There were only a few expections like 24/7 which was quite easy to catch, and opening_hour without specified days, which is internally translated to Mo-Su ....

In the end, it took two days of work and it was so satisfying to see it working in the end. Some issues like Multiple images for feature or Wikimedia Upload, takes months to finish (or even almost a year in the second case), and this was ready in such a short time. Also worth mentioning is, that this was possible by @Dlurak’s work on the opening_hours renderer also featured in this release.

More details and screenshots in Pull Request

One image is worth a thousand words

… See full entry