New doc page for new NSRDB endpoint#280
Merged
Merged
Conversation
Member
|
@PjEdwards do you know if the plan is for all new versions of PSM3 data to be accessed via new API endpoints (rather than, for example, a |
Collaborator
Author
|
No, this was a special case because they reworked the model in such a way that the new data no longer aligns with the old data. Same points, but different ID associated with each location than before. We didn't want to break existing code so we pulled the trigger on releasing this as a whole own endpoint. In the near future the rest of the years 1998-2020 plus TMY, TDY, and TGY will be added. |
Collaborator
|
@PjEdwards okay to merge this in now? |
Collaborator
Author
|
Yep! Thanks Rob |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
No description provided.