Add `cross_street` support to `/v1/structured`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 259
- Forks
- 169
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 1
Description
The /v1/structured API currently only supports address as input.
This is not capable of parsing intersection queries which are supported by /v1/search and /v1/autocomplete.
It would be nice to have feature-parity between the endpoints.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the /v1/structured API with the existing /v1/search and /v1/autocomplete handling for intersection queries. Trace how cross_street is accepted by those endpoints and identify the corresponding structured-input entry point. Done means /v1/structured supports intersection queries through cross_street with feature parity to the other endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100