State of the project

The initial Module is the Duty Logs module. The purpose of the Duty Logs module is to replace the ever-present notebook on the desk of the Duty Officers. This is really about Accountability. This module will serve as a record of actions in the event that there is ever an audit, or a duty officer needs to testify in court. The Duty officer can call on his duty logs as an official record of what has been done.

So the following requirements are met with this module.

• very quickly make a duty log entry - least amount of mouse clicks/key strokes
• duty log entries must be revisioned - never deleted
• quickly make an extensive duty log entry with complex formatting
• quickly view recent duty log entries to get caught up on the situation
• High Level Duty Officers need to see all duty logs and all revisions;
• Low Level Duty Officers need to see each others entries if they work the same desk
• non-duty officers should only be able to see their own logs
• The log needs to be quickly and cleanly made into PDF for printing
• the interface needs to be fast and easy
• Reports on the duty logs must be available and customizable
• High and Low Level duty officer must be role based - so the DL module must be configurable so that you can choose your own roles for this

Duty logs is now working and going through prelim alpha testing

I am now using the Pantheon system to develop this module, every now and then I will commit back to the main sandbox here on drupal.org.

after a fair bit of perfromance issues on pantheon, I have moved the sparcs module back here.

I will be developing this module on a ubuntu 10.10 64 bit LAMP VM and alternating between running it in the pantheon cloud and on my local machine so this system will be ready for the cloud (pantheon at minimum) on release.

Weather module HTTP GOES collection is now operational.

Weather module is now calculating CFFDRS indices based on C2 fuel type and is now sensitive to Leap years, DST and uses the drupal timezone.

The Second Module is the weather module. The purpose of the weather module is to provide a way to collect weather from automatic and manual weather stations and provide a way to record and track other types of weather observations such as belt kit and portable quick deploy weather. The weather module also provides Fire Weather Index (FWI) and Candian Forest Fire Danger Rating System (CFFDRS) codes for weather collected. Currently this is done by using the C2 Fuel type and Equations from the STX-3 Manual. In the future this will be deprecated in favor of integrating the Open Fire Calculator Engine currently being developed in Canada. In addition to these services, the weather module will also serve as a climatology storage and distribution system, allowing other agencies to subscribe to weather in SPARCS and to allow long term storage of weather data and the production of predictive products based on the statisitics of the climatology within. Some examples would be:

• Prevailing wind (windrose)
• Daily Severity Ratings (DSR)
• Long term spatial weather trends and graphs.

So the following requirements are met with this module.

• GOES based RAWS data collection
• Manual Weather entry
• quick deploy station creation on the fly
• exaustive weather, FWI, CFFDRS Reporting
• Climatology Storage, analysis and reporting
• High Level Weather Station Management
• Weather Data/reporting Subscription Service

The weather module dependancies list as of today is:
php = 5.2
dependencies[] = sparcs
dependencies[] = search
dependencies[] = entity
dependencies[] = entityreference
dependencies[] = geofield_map
dependencies[] = geofield
dependencies[] = field_group
dependencies[] = php
dependencies[] = date
dependencies[] = number
dependencies[] = editablefields

my last round of code cleaning broke all the includes, so dont upgrade to the master commit!
the last good commit is Commit 722b5f5 on master
use that until I finish cleaning up the code.

Ok, and we are back, while cleaning up my code I brok all my includes using a search and replace blindly, fix it up and we are back to collecting wx again :) so we are good as of Commit 52265c9 on master
Franco

it appears as though there are still some aspects broken because of my code cleanup, so the last good commit is Commit 722b5f5 on master until further notice.

Ok, the code has been cleaned up, broken code fixed, and the repo is now working on 7.x-1.x NOT master and master has been deprecated, so things are normal starting with: Commit e2aeff1 on 7.x-1.x

You can now spin up your own sparcs, if you have drupal 7 installed. If you are using drush life is easy, just use this command first:

drush dl views devel date entity_reference geofield field_group editable_fields entityreference entity editablefields ctools libraries

to make geofield work follow these directions:
in brief:

• Download GeoPHP
• decompress to the libraries folder

as of Fri march 16, 2012 MST, the last known good commit is: Commit a3eddec on 7.x-1.x
Grab the snap shot from that commit:

This project is still alive albeit moving slowly because we are mid-fire season.
Please only use the 7.x-1.x branch.
Weather collection, FWI and FBP for C2 is working
Manual weather entry in grids or single stations is working
Manual weather in simple or advanced mode working
Duty logs and Duty Log macros are working.

We are currently introducing the Weather Archive module

Migration module is now roughed in, this is mainly to allow easy migration from the D6 version of SPARCS used operationally to SPARCS TNG
We are now looking at ways to Integrate RedApp into SPARCS.
We need help from PHP/Drupal Programmers on this huge project.
Please contact me HERE

Project is still active, just short on time to devote to it. Will be working on it heavily this summer.

All active bugs are being dealt with internally and will not be listed here, if you use my code and find a bug, you are welcome to enter it here.

update