|
|
|
@ -13,6 +13,8 @@ release history and the `develop` branch serves as an integration branch for fea
|
|
|
|
branches should be created and merged as necessary.
|
|
|
|
branches should be created and merged as necessary.
|
|
|
|
|
|
|
|
|
|
|
|
## Where to start?
|
|
|
|
## Where to start?
|
|
|
|
|
|
|
|
Check .env
|
|
|
|
|
|
|
|
Uses pipenv
|
|
|
|
1. Clone this repository.
|
|
|
|
1. Clone this repository.
|
|
|
|
2. Pull data from WRL coastal J drive with `make pull-data`
|
|
|
|
2. Pull data from WRL coastal J drive with `make pull-data`
|
|
|
|
3. Check out jupyter notebook `./notebooks/01_exploration.ipynb` which has an example of how to import the data and
|
|
|
|
3. Check out jupyter notebook `./notebooks/01_exploration.ipynb` which has an example of how to import the data and
|
|
|
|
@ -54,3 +56,6 @@ as this shows how they were manually extracted. Note that the shapefiles only sh
|
|
|
|
- `/notebooks/qgis.qgz`: A QGIS file which is used to explore the aerial LIDAR data in `/data/raw/raw_lidar`. By
|
|
|
|
- `/notebooks/qgis.qgz`: A QGIS file which is used to explore the aerial LIDAR data in `/data/raw/raw_lidar`. By
|
|
|
|
examining the pre-strom lidar, dune crest and dune toe lines are manually extracted. These are stored in the
|
|
|
|
examining the pre-strom lidar, dune crest and dune toe lines are manually extracted. These are stored in the
|
|
|
|
`/data/profile_features/`.
|
|
|
|
`/data/profile_features/`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## TODO
|
|
|
|
|
|
|
|
https://ljvmiranda921.github.io/notebook/2018/06/21/precommits-using-black-and-flake8/
|
Chris Leaman
6 years ago