-
Notifications
You must be signed in to change notification settings - Fork 3
Project Proposal
Jeremy Steward edited this page Sep 19, 2013
·
13 revisions
- [Introduction](https://github.com/ThatGeoGuy/ENGO500/wiki/Project Proposal#introduction)
- [Background Information](https://github.com/ThatGeoGuy/ENGO500/wiki/Project Proposal#background-information)
- [Objectives](https://github.com/ThatGeoGuy/ENGO500/wiki/Project Proposal#objectives)
- [Methods](https://github.com/ThatGeoGuy/ENGO500/wiki/Project Proposal#methods)
- [Conclusion](https://github.com/ThatGeoGuy/ENGO500/wiki/Project Proposal#conclusion)
Below are rough descriptions of what should go into each section of the report. See the relevant issues in the issue tracker for more details / discussion.
- Introducing the concept of the "Internet of Things (IoT)
- Proposed benefits / reasons for the existence of IoT
- Definition of the OGC specification for the IoT
- Reason why we're using the OGC specification
- Aims of the project
- What we hope to accomplish See issue #2
- What is the Internet of Things (IoT)
- What is the Open Geospatial Consortium (OGC)
- What is the OGC specification (OGC RESTful API) that we are using
- Why we want a common API See issue #3
- Finding a sensor setup to add to the Internet of Things (IoT) / Sensor Network (SensorWeb) that can measure information relevant to us locally
- Develop an intermediate library / interface for the sensors to the OGC RESTful API that is being hosted on Dr. Liang's servers
- Develop some user interface (UI), such as a mobile application or web page, that uses sensor data in some fashion. See issue #4
- Sensors used / considered
- How we plan on creating the library / interfacing with the database
- Programming languages we may consider using for the task
- Organization / management (project will be managed and tracked through github) See issue #5
The Conclusion of the proposal will not be completed until all the other sections have been, so it is not entirely useful to mark down what will be inside of it now, but it is important to track that it should be done. See issue #6