Skip to content

Include geo data for geo/geo id discovery and to support geo_value "*"? #240

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

Open
Tracked by #212
nmdefries opened this issue Jan 22, 2024 · 0 comments
Open
Tracked by #212
Labels
enhancement New feature or request

Comments

@nmdefries
Copy link
Contributor

nmdefries commented Jan 22, 2024

Geo helper functions let users easily fetch all geo ids of a given type. This could be extended to our non-US data sources, too, to make those easier to work with.

A wrapper around a geo helper function also lets us easily convert a request for "*" geo values to an explicit list, for the endpoints that don't support the wildcard "*". Related to #235

@nmdefries nmdefries mentioned this issue Jan 22, 2024
42 tasks
@nmdefries nmdefries added this to the Z: epidatr & epidatpy milestone Jan 22, 2024
@nmdefries nmdefries changed the title maybe we need to include geo data for geo/geo id discovery Include geo data for geo/geo id discovery and to support geo_value "*"? Jan 22, 2024
@nmdefries nmdefries added the enhancement New feature or request label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant