Amᵃᵖanda | map data witchRE: https://en.osm.town/@MapAmore/116254253660987536
More praise for #Postpass, the modern replacement to #Overpass
jomo
watmildonRE: https://en.osm.town/@watmildon/115999393169314773
Also, because we're truly living in the future, this uses Postpass from @geofabrik to pull data each night.
TV ad voice: Overpass troubles have you pulling your hair out? Postpass may be right for you!
@watmildon I'll have to look in Jan when I'm at a computer.
One tip, try add a && geom bbox filtering, in addition to the St_Intersects. Yes I know #postgis is supposed to do it, but IME it can be faster
But I've wanted to add a server side cache for #Postpass for a while. But hasn't been done yet.
One tip, try add a && geom bbox filtering, in addition to the St_Intersects. Yes I know #postgis is supposed to do it, but IME it can be faster
But I've wanted to add a server side cache for #Postpass for a while. But hasn't been done yet.
RE: https://en.osm.town/@watmildon/115793587184062200
The Global view for MascotMap can now run against Postpass. It's crazy fast. Still working out why subregion queries are crazy slow. Computers.. amirite?
You can try it yourself!
I am trying to work out how to get MascotMap pulling from Postpass. My current best result is that Postpass takes twice as long as Overpass to return the same data. Hopefully I can nerdsnipe someone into showing me a more efficient query.
Fortunately, I am an absolute noob so it's probably easy to do something better!
Today's work lunch conversation was about duplicate place names. So naturally I looked at #OpenStreetMap to see how common it was (#postpass to the rescue!)
OK this is much more common than I thought. (This is all `place=*` excl `p=locality` & `=isolate_dwelling`)
