Traditional Hawaiian fishponds have long provided Kānaka Maoli communities with a sustainable food source and a vital means for connection with the natural world through the practice of kilo, or deep observation. However, due to the impacts of colonial exploitation and the effects of climate change, many loko i'a across Hawai'i have fallen into disrepair or have ceased to exist. Today, the Pacific American Foundation (PAF) engages in biocultural restoration of Waikalua Loko I'a in Kane'ohe. Such efforts include the monitoring of aquaculture experiment tanks used to propagate native fish and algae, weighing individual fish, and monitoring general fishpond conditions. Each of these practices collect, store, and retrieve data via disparate technologies including hand-written notes, data entry into spreadsheets, and automated sensor logging to a cloud service. This disparity between data management tools presents a barrier to PAF’s long-term vision of a centralized data management system. A feature of this system would manifest as a user interface that visualizes these data streams into a single comprehensive dashboard. Our work takes a step towards such a feature in the design of its user experience and a developed prototype displaying mock sensor data from 17 fish propagation tanks. Future work will expand on these foundations to fully implement a system that consumes transmitted sensor data, combines data streams, and supports more advanced end-user functionality. Long term, PAF staff and the greater Kāne`ohe community will be able to view and act on these aggregated data via a localized and place-based user experience in order to augment existing kilo practices.
This project was bootstrapped with Create React App. In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify