Adjust end dates #2778
Merged
Adjust end dates #2778
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
Note: the imagery is currently missing a diagonal stripe that couldn't be recorded in 2024 due to the weather. For this reason I've currently set the "best" value to false.
All three products are continously updated, the terrain ones in a six year cycle the orthofoto faster. Making the start and end dates quite meaningless outside of a rough indication from when the data is. Maybe it would be a better idea to allow specification of an "update_cycle" value, which would allow the user at least to determine the maximum age of the imagery they are using.
simonpoole
force-pushed
the
remove_end_dates
branch
from
3d3edc1 to
ae44f9b
Compare
I think that makes sense. Though I've seen imagery on an update cycle getting stale too, URLs break, or the updates just don't appear on schedule, so perhaps just for imagery that seems to reliably keep to a cadence we could add that. |
andrewharvey
approved these changes
Aug 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed start/end dates don't make really make sense for these products.
All three products are continuously updated, the terrain ones in a six year cycle the orthofoto faster. Making the start and end dates quite meaningless outside of a rough indication from when the data is.
Maybe it would be a better idea to allow specification of an "update_cycle" value, which would allow the user at least to determine the maximum age of the imagery they are using.