Slow searches using OSM Scout Server. I have added OSM Scout Server support for autocompletion on WhoGo side, but the server itself doesn't have any fancy algorithms made for such scenario specifically. It just runs the full search on every new input. So, maybe it has queued some searches before you get to the last of it.
INFO: 08:54:55 Request: /v1/search?limit=25&search=Lanc INFO: 08:55:38 Parsed query [GB]: house: {lanc}; INFO: 08:55:38 Parsed query [GB]: h-0: {lanc}; INFO: 08:55:41 Request: /v1/search?limit=25&search=Lancelot+Court,+Hull INFO: 08:56:19 Parsed query [GB]: city: {hull}; road: {lancelot court}; INFO: 08:56:19 Parsed query [GB]: h-0: {hull}; h-1: {lancelot court};
INFO: 09:04:16 Request: /v1/search?limit=25&search=Lancelot+Court,+Hull INFO: 09:04:51 Parsed query [GB]: city: {hull}; road: {lancelot court}; INFO: 09:04:51 Parsed query [GB]: h-0: {hull}; h-1: {lancelot court};
Geocoder, again, and missing streets
INFO: 09:13:01 Request: /v1/search?limit=25&search=Redwick+Road INFO: 09:13:02 Request: /v1/mbgl/style?style=osmbright-car-en INFO: 09:13:35 Parsed query [GB]: road: {redwick road}; INFO: 09:13:35 Parsed query [GB]: h-0: {redwick road};
The voice instructions told me to turn into A404, which it pronounced as "eigh-four-four" instead of "eigh-four-oh-four". This happened several times, so I was not hearing it wrong. Or maybe I was but consistently