I did try to create a pull request, but it seems like the permissions for openscape-community don't allow it.

I have switched to aiohttp instead of requests, because requests is blocking and I think it was the cause of a lot of the errors that I previously saw. The branch is at RDMurray/overscape-server

Unfortunately it breaks tests for now. This is the branch currently running on soundscape.mur.org.uk

Log metrics about cache hits/misses, response time, etc. and optionally expose this as an API endpoint. The original Soundscape tile server did this; see https://github.com/microsoft/soundscape/blob/main/svcs/data/gentiles.py#L71

@Oliver2213 noticed this in our logs:

ERROR:aiohttp.server:Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 129, in sentry_app_handle
    transaction.set_http_status(response.status)
AttributeError: 'NoneType' object has no attribute 'status'

According to getsentry/sentry-python#951, this may be a bug with Sentry's aiohttp integration, but it's not clear what the fix or workaround is.

Does this failure in Sentry mean that a lot of our successful responses are actually being reported as failures? Hopefully it's not actually causing failed responses to users?

We're currently limited to forwarding all requests to a single (albeit configurable) Overpass server. We should have a pool acrosswhich to load balance, perhaps specifying the region of the world for which each can be used. I'm imagining a future where the world's data is distributed among a set of modest servers hosted by different individuals/organizations.

The original Soundscape tile server didn't just serve a subset of OSM objects; it also computed intersections and building entrances. We're currently computing intersections but not entrances.

This should just be a matter of translating the subquery at https://github.com/microsoft/soundscape/blob/main/svcs/data/tilefunc.sql#L28 from SQL into Python, as was done for intersections (see https://github.com/openscape-community/overscape-server/blob/main/app/overpass.py#L137).

This sort of defeats the purpose of Overscape, but now that it's instrumented with Sentry probes, there's some value in supporting non-Overpass backends, namely to use a PostGIS server as a drop-in replacement and to compare the performance/error rate. @Oliver2213 am I correct this would be helpful? I think it wouldn't take much work from me.