The problem I have most of all with the routing is that it seems to default to my location as either the From or To value (whichever is the one I haven't selected). Once that's been chosen it's not immediately clear how to change it, all you can do is view the route. That's a fine solution when you're immediately looking to go somewhere, but it's not great when you're trying to plot a route between two places in advance.
I've been using CoMaps for a few months and only just discovered that if you choose another location on the map once you've got an initial route and select Route To/From, it then updates the current routing.
> The problem I have most of all with the routing is that it seems to default to my location as either the From or To value (whichever is the one I haven't selected). Once that's been chosen it's not immediately clear how to change it
Yeah this is an oft-asked question at least for OsmAnd, but I was recently corrected on this myself: so long as you don't press 'start' on the route, you can always change the from position freely and it won't flip back to your current location. You can close the navigation window (back button, swipe it away, or tap on the map) to get the map view back in full-screen for further browsing and selecting another point that you want as departure point, waypoint, or (subsequent) destination. Rinse and repeat until you have the route figured out with all the waypoints :)
I use this a lot for planning mapping routes. Another protip is to go into the waypoints view and on the top right you can do traveling salesman sorting to get the shortest way that visits all waypoints
CoMaps/OrganicMaps I don't know; I'm one of those who grew up with OsmAnd and got used to having all those features
Also an owner of a non-electric Babboe. We looked at converting it to electric but very few companies would actually do it and the one that we finally got to give us a quote basically said it wasn't worth it. They would've had to replace the whole brake system due to the higher speed of an electric bike. We ended up just buying a different electric cargo bike.
I believe your story, the thing is... once my Babboe is driving, I can reach 20 km/hour. The problem is, it takes some time, and I'm fine with the 15 km/hour to 20 km/hour taking time or effort. I'm cool with staying at 15 km/hour as well. The problem is only after I am completely at 0 km/hour at a traffic light or stop sign, getting velocity. I wouldn't need better brakes there. Since I would never go higher than 20 km/hour electric, I wouldn't need better brakes. If they say I shouldn't go faster than 15 km/hour, I'll stick to that, no problem.
But for people who'd reach the max 26 km/hour, if they'd need better brakes, then if they reach such speed manually (going downwards, for example) would suggest my current brakes aren't adequate either. But I'm not interested in going from to 20 km/hour ASAP. I am interested in getting a little of help at 0 km/hour going forward. After that, the electric part can go off for all I care.
Is there a reason why the URL parameters are obfuscated? I think it would more user (and SEO) friendly to have at least the place names in the URL, e.g. brolly.sh/forecast/united-kingdom/yorkshire/york.
Still, great project! Definitely fulfils my desire for minimalism in all things.
It’s a good question. Initially, the URL was lat/long values, and then I did try place names. I ended up with the short code approach to minimise API calls to downstream services.
The short code in the URL is generated at search time, and maps to a location name, lat/long, altitude etc. within a table. It’s generated off of the location name, so two people searching for the same place get the same short code.
The short code enables a forecast lookup to be a SQLite DB read, followed by a single API call for the forecast.
A more descriptive URL would have required two sequential calls - one to figure out the lat/long and/or place name, and another for the forecast. This wasn’t a huge speed problem, but I struggled to find geocoding APIs with generous free tiers or reasonable low volume pricing. It would have also made the forecast at a given URL somewhat non-deterministic, as the geocoding API could change its output or preferred result over time.
Short codes quite possibly wasn’t the right solution. It’s definitely something I’ll think more about. Thank you!
How about adding the location information as a suffix to the short code, e.g. `/forecast/<shortcode>/united-kingdom/yorkshire/york`? The latter part of the URL is of not use to the site, but is useful for the user.
I don’t get that reason, couldn’t you just use the location name as a field in the database just like you use the short code right now? Where’s the additional API call on lookup coming from?
Situation a:
Someone searches for location XYZ.
The geocoding API returns lat and Lon and canonical name ABC.
You save that and the slugified name abc in your DB.
(If the API doesn’t return a name, you can use XYZ instead of ABC).
You return slug abc to the user.
Situation b:
Someone requests weather for location at slug abc. You look in your DB, ask the weather API for the weather at lat/lon and return that to the user.
Situation c:
Someone searches for a place that happens to already exist in the DB.
You geocode the search term and get a lat/lon pair that’s already in the DB so you return the saved slug.
How is that different than using a shortcode? In which situation are you doing a geocoding API request you don’t need to do with the current system?
Agreed. I think the code examples in the article could do with showing before and after states of the branch or repo and maybe compare with standard git commands.
Even then I don't think the abstraction to HTTP verbs is necessarily a useful one as web requests and version control are two different mental models.
I think OP has envisioned a situation half way between what we now have and what will soon be the actual reality and that his idea will just be quickly skipped over.
I don't think website design will go away, but I do expect that people will soon be ordering products and booking holidays through AI chats instead of doing it themselves, which will require the kind of manifests he's talking about, but will skip the UI layer completely.
I checked that out... IIRC there was a channel showing videos of custom-architected millionaire houses, mostly in california. They were all gorgeous, with huge, open, window-filled designs showing great CA vistas, garages filled with sports cars, unlike any house I'd ever seen before yet somehow all felt the same. It was like all the millionaires had identical lives, just shifted onto some other CA hill. It was very strange.
I had this problem and it turned out to be an upstream issue with MicroG which was eventually patched. If you have an error message you can search for existing issues on /e/OS' gitlab/forum.
Revolut stopped working for me for a while with the error that the bootloader wasn't recognised and rooted phones aren't supported. After about a month an OS update solved it.
I've been using CoMaps for a few months and only just discovered that if you choose another location on the map once you've got an initial route and select Route To/From, it then updates the current routing.