Open
Conversation
Deploying bats-ai with
|
| Latest commit: |
08a4246
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0a905410.bats-ai.pages.dev |
| Branch Preview URL: | https://grts-cell-updates.bats-ai.pages.dev |
a2ac62d to
c278db4
Compare
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
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.
Updates GRTS Cells
Background:
Initially the USGS had provided us with recording within the United States that had a GRTS_Cell_ID associated with them. This was a unique Id that indexes a 10kmX10km grid of the CONUS. You could use that to determine the location of a recording. I had created the GRTS Cell Model to include the cell_id as a primary key because I expected these to be unique values that could be used to index the locations. These GRTS Cell Ids can be loaded from shapefiles that are provided on sciencebase.gov.
Update:
There are multiple lists of GRTS_Cell_ids for different countries and regions that are not unique. They have something called a "Sample_Frame_ID" the sample_frame_id for CONUS is 14. So Canada and CONUS could have overlapping GRTS_cell_ids which means the primary key being relate dto the GRTS_cell_id doesn't work if you are loading multiple countries.
Issue:
To further add to the confusion, there is a shapefile for CONUS, and there is a shapefile for Alaska/Canada.
Alaska has a sample frame Id of 20 and Canada has a sample frame Id of 19. The shapefile that includes both Alaska and Canada doesn't differentiate between GRTS_cell_ids that are from Alaska or Canada, it's all one list of non-conflicting GRTS Cell Ids. So any recording from Canada or Alaska needs to look intot he same list of GRTS_cell_ids to get the proper cellId and the location associated with it.
PR Changes:
loadGRTSmanagement script to have a--locationsoption that allows for loading other regions. For right now the only additional location that will loaded is Canada/Alaska usingloadGRTS --locations 20loadGRTSmanagement command will now replace any GRTS row that has a matching GRTS Cell Id and sample frame Id_delimitation. This is taken from guano metadata file processing. The underscores separate and contain information like the GRTS_Cell_Id, could contain the sample_frame_id and a time. The consistency in the files aren't great, so there are a few edge cases where files can have different structured values. I.E sometimes the first number is a GRTS_cell_id and sometimes it is a sample frame_id.