ivyrze / transit-a11y Goto Github PK

Programmatically adjust initial zoom to fit all route shapefiles within initial viewport

Currently, the search algorithm shows poor quality results for multi-word searches. This is no surprise because the Redis query uses the | operator between words. Play around in the CLI with new ways to build the database query, using escaping, wildcards, fuzzy matching, etc. Heads up – they can be finicky, especially when used together, so test thoroughly.

ft.search idx:stops "@name:%woodwerd% 9 mi* @coordinates:[...]"

Here is the search query syntax documentation for reference.

When the API endpoint is requested, the following error occurs:

AxiosError: write EPROT error:SSL routines:final_renegotiate:unsafe legacy renegotiation disabled:../deps/openssl/openssl/ssl/statem/extensions.c:908:
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16) {

My understanding is that this means their server doesn't support Renegotiation Indication Extension (RFC 5746). This makes sense because TLS 1.2 and 1.3 are also not supported by their server.

This is only showing up on Heroku and not on my local machine. I tried running with node --tls-min-v1.0, which didn't help.

I wish TriMet would just update their servers instead of running an ancient setup from 2008 – and I requested to join their developer forums to poke somebody about it. But if not, we might need to find a workaround, or at least use one temporarily.

This can be replicated by clicking on the route icons instead of the actual stop text. This error seems to occur because the client-side script looks for the stop ID in the child element, can't find it, and sends an invalid/empty request.

An updated GTFS with accessibility data is being developed at dtc-gtfs for the Detroit People Mover. Add this GTFS feed along with the current QLINE GTFS feed to the list of supported agencies.