Skip to content

Clarify no-data value / null / NaN / character encoding for most processes #480#490

Merged
m-mohr merged 4 commits intodraftfrom
nodata
Aug 7, 2025
Merged

Clarify no-data value / null / NaN / character encoding for most processes #480#490
m-mohr merged 4 commits intodraftfrom
nodata

Conversation

@m-mohr
Copy link
Member

@m-mohr m-mohr commented Jan 3, 2024

Fixes #480 and related issues:

  • No-data values vs. null
  • NaN
  • Character encoding for strings

Guide for no-data values and character encoding have been added to https://github.com/Open-EO/openeo-processes/blob/nodata/meta/implementation.md

@m-mohr m-mohr added this to the 2.0.0 milestone Jan 3, 2024
@m-mohr m-mohr changed the title Clarify no-data value / null / NaN for most processes #480 Clarify no-data value / null / NaN / character encoding for most processes #480 Jan 3, 2024
@m-mohr m-mohr marked this pull request as ready for review January 3, 2024 14:02
This was referenced Jan 3, 2024
@m-mohr m-mohr linked an issue Jan 3, 2024 that may be closed by this pull request
Copy link
Member

@soxofaan soxofaan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't got through this giant PR yet, but here are some comments already.

Also note that some comments probably apply to multiple other places, I didn't cover yet

@m-mohr m-mohr requested a review from soxofaan August 23, 2024 13:18
@soxofaan
Copy link
Member

I just stumbled on this old PR where I'm expected to give a follow-up review, but in the meantime it got marked as "has conflicts that must be resolved" (but github doesn't show me more info)

Is this still a valid PR to chase?

@m-mohr
Copy link
Member Author

m-mohr commented May 23, 2025

Yes, this PR is still valid. I've resolved the conflicts. @soxofaan

@m-mohr
Copy link
Member Author

m-mohr commented Jul 16, 2025

Updated the PR again to the latest draft version.

This PR is important for #468 and, if we want to have it, we should certainly have it with rc.2 and not just for the stable release to ensure the changes make sense and work as expected.

- `aggregate_temporal_period`: Removed unused exception `DistinctDimensionLabelsRequired`.
- `aggregate_temporal_period`: Clarified that the definition of weeks follows ISO 8601.
- `apply_polygon`: Replaced outdated usage of `raster-cube` subtype with `datacube` and dimensions. [#524](https://github.com/Open-EO/openeo-processes/issues/524)
- `array_interpolate_linear`: Apply interpolation to NaN and no-data values.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

out curiosity: is there a reason for not only adding changelog items, but also changing the order of non-related items?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I try to keep larger changes at the top and then the processes in alphabetical order so that it's a bit easier to follow. Sometimes changes also come in when resolving merge conflicts.

@soxofaan
Copy link
Member

soxofaan commented Aug 7, 2025

I did another superficial pass and I think this is fine to merge, at least to unblock other progress

@m-mohr m-mohr merged commit e3fe884 into draft Aug 7, 2025
2 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Next processes release Aug 7, 2025
@m-mohr m-mohr deleted the nodata branch August 7, 2025 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

null vs NaN

2 participants