Route match response logic updates api.mdx #499
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clarifies that Route Match will not return all indices if there are impossible distances between points, clarifies the -1 speedLimit logic
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
clarifies that Route Match will not return all indices if there are impossible distances between points, clarifies the -1 speedLimit logic
What?
Addresses questions from Innovative-E regarding when Radar doesn't return all indices in our Route match response - also clarifies when we return -1 as speedLimit
https://linear.app/radarlabs/issue/MAPS-1091/route-matching-issues
Why?
Document Route Match response behavior based on latest changes
How?
Screenshots (optional)
Anything Else? (optional)