DJ: Jace Bain - Britwaves
#overpass #DJJaceBain #Britwaves #Radio1190 #KVCU
@harry_wood the purpose wasn't to load balance overpass, but to encourage people to learn how to use SQL.
So often, clients come needing OSM Data and they have an overpass query. And ... You could have written it in SQL!!!
@spacehobo "I had to give up on #overpass queries"
Just an anecdote but, on some recent occasion I did notice the main OverPass API seemed to be broken, and at the time I found I was able to swap to using "PostPass" instead. It's a new system Frederik and the @geofabrik folks were presenting a #sotmeu25 . https://wiki.openstreetmap.org/wiki/Postpass
(Not sure it was really their intention to load balance the main overpass API, but maybe it can. It performs a lot better with some queries)
I am REALLY FRIKKEN MAD now that the PBF→Spatialite conversion of #OSM data loses all of the relationships made by the relations in the data. I had to give up on #overpass queries because hey nobody can run an API any more without drowning in LLM scrapers, and the SQLite database is so much quicker in #QGIS than my old geojson/shapefile approach, but the limits of the separate multilinestring rendering of relation data are significant.
My project used to have really nice distinct rendering for signposted cycle routes that changed depending on whether or not the route forced the rider to tAkE tHe LaNe on a designated road. It really highlighted how bad the gaps were in the local cycle network, and was a really important tool for local campaigning!
But now I'm forced into some compromises that make my maps far less useful, all because everything's a botnet now. I'm still not sure it's going to work!
I migrated the container with #Wanderer to a more powerful #Proxmox node, increasing the number of CPUs and the amount of RAM. Now I can build trails using my own computing powers!
#Wanderer also uses #OVERPASS and #Nominatim, and it looks like I can host them as well.
Da ich gerade in der Gegend unterwegs bin hab ich mir gedacht füge doch die #stolpersteine in #rijeka in die #OSM Datenbank hinzu. Der #wikipedia Artikel liefert dazu die passenden Adressen, den Rest erledigt man mit #osmand unterwegs. Jetzt ist mir allerdings aufgefallen das im Wikipedia Artikel https://de.wikipedia.org/wiki/Liste_der_Stolpersteine_in_Rijeka ein paar Fehler in den Adress-Daten vorhanden sind.
Unterwegs am Smartphone kann ich das jetzt nicht korrigieren.
Hier die #overpass Abfrage:
https://overpass-turbo.eu/s/2q8m