WIP: GT db record for 2017 MC #3696
Open
Conversation
This file contains 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
* Create a record for the 2017 MC GT db * Additionally create a record for the 2017 collision GT db * Fix a typo in the 2016 MC GT db record * Closes cernopendata#3695
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
One question to resolve is whether or not to have a separate record for the 2016 and 2017 collision GT db when they point to the same file. The other option would be to make a new record for the GT MC db, modify the GT for collision data to include references to 2017, adding a new link.
The XXXX and YYYY in the json file refer to the as-yet-undefined record ids