1 / 29

Ripcurrent Tracker

Ripcurrent Tracker. Christopher Seeley, Ralph Mattiaccio Ken Bodzak, Will Abeel, Danielle Maginnis. Project Overview. Goal: To gather ripcurrent data to assist in research Collect detailed information Wave data Water level Wave period Time & Location Frequency Type of rip current

jalen
Download Presentation

Ripcurrent Tracker

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ripcurrent Tracker Christopher Seeley, Ralph Mattiaccio Ken Bodzak, Will Abeel, Danielle Maginnis

  2. Project Overview Goal: To gather ripcurrent data to assist in research • Collect detailed information • Wave data • Water level • Wave period • Time & Location • Frequency • Type of rip current • Pre-existing weather conditions • Compare to other tidal/buoy data

  3. Project Overview • Use data to better understand causes of rip currents • Improve public safety • Avoid potential dangers on the beach

  4. How? • Mobile application used by lifeguards • Submit reports and input data as it happens • Website used by researchers • View data in real-time • Store all reports in central website/database • Researchers can collect and use all current and historical data for analysis

  5. User Groups • Each group has different permissions and features available. • Three main groups: Lifeguards Researchers Administrators • Permission Enforcement • Access Control Lists

  6. Lifeguards • Use mobile application • Submit rip current reports • View reports submitted within last 24 hours

  7. Researchers • Use website • View rip current reports • Search through all reports • Collect large quantities of data from reports in a batch

  8. Administrators • Add, view, and edit managed lifeguards within local community • Disable users or alter privileges • View local rip current reports • Add, view, and edit researchers and lifeguard administrators • Disable users or alter privileges • View all rip current reports • Last 24 hours • Full search Lifeguard Admin Research Admin

  9. Functional Requirements • Features of the software that must be included: • Receive GPS location data from mobile device • Transmit data to remote server • Store data in database • Display stored data • Maintain a log of database modifications

  10. Functional Requirements (continued) • Features of the software that must be included: • Multi-user account and login system • User administration • Security: Restrict access to system interfaces and data • Username and password • User account permission hierarchy • User permission enforcement • Log user activities

  11. Evolutionary Requirements If time permits… • Pull external data • Use with the data collected by the users of this system • Types of data: • Coastal buoy data • NOAA ocean data • Expanded: NBDC buoys • Additional goals successfully implemented

  12. Platform Requirements • Internet-connected smartphone or mobile device • Mobile web browser:HTML5 Compatible • Android • iOS • Blackberry • WebOS

  13. Platform Requirements • Live web server • Provides functionality for both website and mobile application • Specifications: • Apache2 • PHP 5 • MySQL • CakePHP 2.0 Framework

  14. Interface Requirements • Web browser for non-mobile application use • Internet Explorer 7+ • Firefox 3.0+ • Google Chrome • Interface with existing database systems • Retrieve data from 3 local buoys and Atlantic City tide gauge • Access given by Stevens researchers • Expanded to buoys from NBDC

  15. Process Requirements What’s needed: • Large project • Many files and code • Collaboration • Simultaneous editing • Solution: Version Control System • Subversion

  16. System Design - Hardware • User workstation • Connects to web server and interacts from browser • System administration and data collection • Mobile Device • Internet-enabled device connects to web server • Remote access and submission to system • Web Server • Provides system interface and functionality • Communication with database server • Database Server • Store all system data and retrieve when necessary

  17. System Design - Software • Models • Contains all data access functions • Ensures data is in a usable format for DBMS • Controllers • Functions to access data and determine which web page to display • Data accessed through models, returned to views • Views • Contains all web pages • Has all logic for organizing and displaying data to user (through UI)

  18. System Design - Software • Mobile Views • Similar to full website • Optimized CSS/Javascript for mobile devices • Lighter UI • Smaller size • Redirect based on user agent • Database Management System (DBMS) • MySQL backend

  19. User Accounts • Username • Password hash • Password salts • Email • Community • User type (sets permissions)

  20. User Creation

  21. Login Authentication

  22. User Administration

  23. Rip Current Reports • Date/time of occurrence • Reporting user • GPS/Location coordinates • Intensity • Nearby structure information • Description (comments, other info) • Buoy data (external source) • Wave height, frequency • Station • Date/time of tidal data reading

  24. Submit Report: Mobile version Retrieve location data Fill out report

  25. View Report

  26. Report List

  27. Report List: Map View

  28. Report View: Mobile version List View Map View

  29. Questions?

More Related