Reconciling with Places API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, javascript
- Domain
- api, internationalization
Research direction
Begin by comparing the address metadata at the Chromium i18n URL with the Córdoba result returned by Google Places Autocomplete and its JavaScript widget. Determine whether the mismatch is in address normalization or validation; done means a documented compatibility conclusion or a clearly scoped library change.
Written by the indexing model from the issue text.
Description
Hi,
I'm trying to use metadata to validate addresses which may be populated from Autocomplete using the Google Places API. There are some challenging inconsistencies, such as Córdoba, Argentina.
Assuming the reference in this DB is the province (which includes a city by the same name):
https://chromium-i18n.appspot.com/ssl-address/data/AR/Córdoba
Places API and the corresponding JavaScript widget, however, returns a version without the accent on the province name: "Córdoba, Cordoba, Argentina" like here:
https://www.google.com/maps/place/C%C3%B3rdoba,+Cordoba,+Argentina
This is just one example. Has anyone successfully validated addresses returned from Places Autocomplete using this library?
Thanks!
- Dominant language
- C++
- Stars
- 629
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from google/libaddressinput
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/libaddressinput#255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
google/libaddressinput#245 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
google/libaddressinput#254 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 52/100
google/libaddressinput#250 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
google/libaddressinput#249 ·
All issues in google/libaddressinput
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
shadps4-emu/shadps4-qtlauncher#465 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Qiskit/qiskit-aer#2466 ·
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NVIDIA/attestation-sdk#41 · 1 comment ·
-
[Bug]: CMAKE Fails to find libgit2 on POP OSPossibly taken @Tirpitz93 claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
subsurface/subsurface#5007 · 2 comments ·
Maintainers usually reply within 2 days
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days