Add database schema and migration files #80
Conversation
Added info about Tableau and cleaned up existing info on the README
Added details about features & project architecture
…ges into respective folders
…istian-patch-1 Create workflow
…istian-patch-2 Delete .github/workflow
…istian-patch-3 Create workflow
…t values to point to updated index.js path
…nize-codebase-structure Refactor codebase structure
…patch-1 Issue OpenSourceFellows#30 - Create issue_template.md
…patch-2 issue OpenSourceFellows#32 - Create PULL_REQUEST_TEMPLATE
…son-description Clean up package.json description
- Add download_canopy.py for downloading canopy GeoTIFF - Add visualize.py for generating canopy height visualizations
- Add download_canopy.py for downloading canopy GeoTIFF - Add visualize.py for generating canopy height visualizations - Add .gitignore to exclude large data files
|
Can you please resolve all the merge conflicts and update it with the latest pull? |
|
@thao-1 @ramakanth98 @dylanpicart @blopez024 My judgement tells me that this PR should be moved to dashboard-server repo and then maybe we can decide on how much of the work done here could be salvaged and integrated to our project. I will wait for comments for a couple of weeks and then try moving this to the other repo. Will appreciate any comments a lot. Thank you. |
|
we would want this to be merged to dashboard-server repo instead of this one so maybe we can create a new PR for that. You can salvage the work of this by cherry picking your commits something similar to https://github.com/OpenSourceFellows/dashboard_server/pull/89 |
10 participants
Description
Issue: Postgres Database (#15)
I couldn't find any existing table so I create a new landmark table and campaign table.
I've set up the database schema with the following features:
Landmarks Table:
Includes all requested fields (id, name, latitude, longitude, acres_owned)
Added timestamps for tracking
Added validation for coordinate ranges
Created a spatial index for efficient location-based queries
Campaigns Table:
Linked to landmarks via foreign key
Includes species (from Notion)
Includes water_volume (from Gov APIs)
Added canopy_density for future use
Status field for campaign state management
Additional Features:
Automatic timestamp updates
Spatial indexing for location queries
Data validation constraints
Please let me know if I need to change anything