-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restructure work - clear up site conditions vs site location #127
Comments
erDiagram
Campaign ||--|{ Site : "has many"
Site ||--|| SiteCondition : "has one"
Campaign
Site {
int campaign_id
int site_condition_id
String plot_id
date site_visit
}
SiteCondition {
int site_id
}
|
Yep, basically everything here https://github.com/SnowEx/snowexsql/blob/master/snowexsql/tables/site_data.py#L15-L28 |
So I was initially under the impression that a site would not be date dependent unlike the pits. This was a misconception on my part. |
I guess we can keep these as attributes in the table. Can't think of a obvious reason and we can come back to this if needed. |
Sweet, I'll just consolidate for now then |
We now have a
Site
belonging to aCampaign
. PreviouslySiteData
had a date AND location associated with weather, conditions, etc.To maintain this info, we can change
SiteData
toSiteConditions
and link that to theSite
.https://github.com/SnowEx/snowexsql/blob/dev/snowexsql/tables/site_data.py#L11
https://github.com/SnowEx/snowexsql/blob/dev/snowexsql/tables/site.py#L20
Site
can have the location andSiteConditions
can have date-specific conditions. Each point or pit can link to aSiteCondition
, belonging to aSite
, belonging to aCampaign
.FYI @micahjohnson150
The text was updated successfully, but these errors were encountered: