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

Better support of "Lincoln, Nebraska" in spatial value #4451

Open
FuhuXia opened this issue Sep 5, 2023 · 1 comment
Open

Better support of "Lincoln, Nebraska" in spatial value #4451

FuhuXia opened this issue Sep 5, 2023 · 1 comment
Labels
bug Software defect or bug

Comments

@FuhuXia
Copy link
Member

FuhuXia commented Sep 5, 2023

We support string value for spatial field such as Lincoln, Nebraska, as documented here. But in reality:

  • Lincoln, NE is supported, NOT Lincoln, Nebraska
  • Brown County, Nebraska is supported, NOT Brown County, NE

The reason is the how the values are present in the locations table. We need to introduce some logic in the code so that all four values are supported.

How to reproduce

See the difference in the query results:

catalog=# select name from locations where name like '%Nebraska';
catalog=# select name from locations where name like '%NE';

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

@FuhuXia FuhuXia added the bug Software defect or bug label Sep 5, 2023
@hkdctol hkdctol moved this to 📔 Product Backlog in data.gov team board Sep 7, 2023
@hkdctol
Copy link
Contributor

hkdctol commented Dec 28, 2023

Moving to icebox for now

@hkdctol hkdctol moved this from 📔 Product Backlog to 🧊 Icebox in data.gov team board Dec 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Software defect or bug
Projects
Status: 🧊 Icebox
Development

No branches or pull requests

2 participants