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

value not present vs null #157

Closed
m-mohr opened this issue Dec 7, 2022 · 2 comments
Closed

value not present vs null #157

m-mohr opened this issue Dec 7, 2022 · 2 comments

Comments

@m-mohr
Copy link
Collaborator

m-mohr commented Dec 7, 2022

From experience in STAC and openEO, it seems some implementations/programming languages have a hard time to distinguish between "not present" and "null". Specifying different meanings for null and not present as for crs (unknown / CRS:84) might be a bad idea. Therefore, I'm putting out for discussion whether it's a good idea to do this and maybe instead use "unknown" as string or so instead of null?

@jorisvandenbossche
Copy link
Collaborator

I don't have a strong opinion about how we exactly represent this, except for that I want there is some way to indicate that the CRS is unknown.

In Python, it's very easy/natural to use null/None, so I can't judge about the difficulties it gives. Changing it to use "unknown" is not forward compatible (older readers will fail on files with this new value)

@m-mohr
Copy link
Collaborator Author

m-mohr commented Jul 26, 2023

Closing, didn't seem overly relevant to implementors yet.

@m-mohr m-mohr closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2023
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

2 participants