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

GOAT Core / Client: Don't treat empty result as a job failure, communicate "no result features" to the user #3389

Open
nihar1024 opened this issue Nov 11, 2024 · 0 comments
Assignees
Milestone

Comments

@nihar1024
Copy link
Contributor

nihar1024 commented Nov 11, 2024

For many indicators, an empty result set is expected and valid (for eg., nearby stations with modes that are rare, catchment areas in regions with PT modes that don't exist in a region, etc). This sort of a result should be communicated to users specifically, rather than triggering a job failure.

@nihar1024 nihar1024 added this to the v2.2 milestone Nov 11, 2024
@nihar1024 nihar1024 self-assigned this Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant