Cartes.app, a French Web alternative to Google Maps, based on OSM, is now translated in English. Lots remain to be done, but the app should be usable by English speakers
Other languages are provided but with limited coverage. It’s a mix of auto-translations and community contributions. The community’s primary language is French, but we welcome english issues of course. Hopefully, Codeberg will add a translate option soon ?
Unfortunately, the app is very slow today, due to the French Overpass instance (that we’ve set up) being down, and the German one being constantly under load.
If someone here knows about other public instances, it would be helpful.
We hope to showcase a v1 of the app at SOTM Paris in August
Looking at the requests the page is making, it’s to get details of POIs when clicked on, and to get nearby POIs of similar type. Actually that is putting a fair amount of load on Overpass, not surprising that things are slow…
Yeah, I have read it. There’s not enough context. Didn’t investigate further. Requests are still being made when changing the zoom. I assume it’s not finished deploying.
Is meta necessary ? Would there be any saving by removing it? It may be acceptable to simply link to OSM.
At least the results should be cached, to not make the same query again when searching the same category/string, or clicking on the PoI later. Better yet, store some of the most prominent and frequently used objects (eg transit, as you have much French transit data already) somewhere yourself, to reduce API calls. Spatial query on those can then further be performed yourself.
Bluesky is nice and useful. I won’t judge it being the default for user reviews. But can more options be added? Eg Mangrove was discussed recently again.
I don’t know how review systems work. Maybe you can simply add a “share” functionality for posting to Mastodon and other services, without directly and deeply integrating them for reviews? That can be a compromise to balance between your requirements, and user needs or the userbase.
@Kovoschiz yes, still a lot of optimizations to be coded. A double ghost overpass call is fixed by this PR.
Maintaining our own cache DB is not an option yet, it’s too much work.
But can more options be added?
Yes sure, but with A) an seamless interface for the user B) a long-lasting commitment from someone to maintain this addition (Mangrove, Mastodon, others).
All the reviews should be stored as a cache on our own DB on the server (not the source of truth, we don’t want to handle this : there should be a simple script to recreate the review cache DB from the source of truth). Note that our ATproto implementation isn’t good enough yet. We’re not handling eurosky correctly ; we’re not handling atproto oauth correctly. I’m in favor of having a proper v1 before adding more (inevitable) complexity.
Looks like a Webgl problem. Also check if you have Firefox fingerprinting protection enabled : this is known to mess the map completely. Did not have time to see if MapLibre can work despite this option.
