Geocoding V6 API Using Structured Input Does Not Support Secondary Address
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 768
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the V6 API via the SDK version 0.16.0 and would like to utilize the structured input option. However, I cannot find a way to include a secondary_address parameter either on its own as a structured field or as part of the address input string. Both strategies for accessing the API with a structured query fail to include it in the response.
Is there a way to use structured input in V6 that allows for the inclusion of a secondary address in both the request and response?
Also, I'm the author of the TypeScript interface for the V6 API. I'd be happy to update that package to include secondary_address as a known feature in both the response and the structured input if/when it's added to the SDK.
Thanks!
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 reviewing the SDK's V6 geocoding structured-input entry point and its request and response handling; the issue names no files or tests. Verify whether secondary_address is accepted and returned, then define the SDK changes needed for support and update the referenced TypeScript interface if the feature is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100