Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DO NOT MERGE: Expose full details about geocoding clusters (primary/secondaries) #211

Closed
wants to merge 91 commits into from

Conversation

leonardehrenfried
Copy link

As discussed in the tech call and Jira, this is a backwards-incompatible change for indexing and exposing the full details of a geocoding stop cluster.

You can now search by any of the cluster's elements' name or code and the full cluster with primary and secondary elements is returned.

An example of the new JSON response is here: https://gist.github.com/leonardehrenfried/7c7140407098b64417c7ffe7506c4139

Note that this doesn't include any special handling of shared stops. Hence they will only become a cluster when they have an identical name and are closer than 100m meter to one another. Also, the primary location is chosen at random.

abyrd and others added 30 commits January 24, 2024 20:12
also capitalize constant identifier
add updater reads from buffer
add garbage collection
Uniformly add RT_AB to all TODO and FIXME comments
Co-authored-by: Thomas Gran <[email protected]>
renovate bot and others added 17 commits May 26, 2024 09:54
Document and validate timeRange GraphQL parameter
With this it's possible to differentiate between entries added because of
configuration and those from runtime requests, the latter being candidates
for the former.
…/jersey-monorepo

fix(deps): update jersey monorepo to v3.1.7
…ter/transit/request/RaptorRequestTransferCache.java

Co-authored-by: Henrik Abrahamsson <[email protected]>
…ayer-no-stoptimes

Realtime stops vectortile layer checks whether there are stoptimes on the service day
…er-cache-request-origin

Log the origin of a request that causes a transfer cache addition.
@leonardehrenfried leonardehrenfried force-pushed the cluster-geocoder branch 2 times, most recently from d4858c0 to d46d895 Compare May 29, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants