Serialize time extent using to_rfc3339() #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b4l
approved these changes
Jan 4, 2025
Member
b4l
left a comment
b4l
left a comment
There was a problem hiding this comment.
Hi @jacovdbergh , thanks for the contribution! Just a minor nit. CI needs some love like the rest of the project. Maybe I will get around.
Contributor
Author
|
Thanks for having a look, I've resolved the issue. |
Member
|
Thanks @jacovdbergh ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes serialization of the time extent to use the to_rfc3339() function instead of just to_string(), which I believe is in line with the OGC Features Core specification.
Before:
After: