did some comments of how to do the calculations
Gives back CRS for correct UTM
Test for UTM finder
I think I've got the coordinates for the transects done, I just need to figure out how to do a line perpendicular to and crossing other lines.
Almost done with transect creation, need to find some tests to run
Tabbing is working properly now. Plot still looks horrible
With the help of the prodigious Mr. Sibley, plotting is now working properly!
Added required JSF libs to compile scope in order for 
Added more slf4j logging dependencies. Changed how results session writing is done in results.js
dygraphs now sized dynamically based on client's window onstead of being hard coded
Enable/Disable buttons are now provided with the shoreline identify - Clicking a button will enable or disable the shoreline.  
Front end for creating transects now wired up with a form from the front end, creates WPS execute request, and gets WPS result from geoserver. I currently don't have a working stub to hit against but have created my input(s) and output from skimming through Jordan's GenerateTransects WPS extension process - once the process is up and running, I should be able to get a working transects layer loaded
Refactored so all stages are pulling and setting the stage config from a single function 
Further refactoring and consolidation of upload functionality across stages
Reserved colors for baseline, intersection, shorelines and transects
Using version 1.0.2-SNAPSHOT of proxy-utils since the proxy implementation was changed to use AlternateProxy. Changes to the version in this pom needs to be orchestrated with the release of proxy-utils.  This is to introduce the ability to use dynamic parameters to pass forward-url using dynamic "read-only" properties
Updated pom to use 1.0.2 release of dynamic readonly properties
Removed netbean hint
Changed the gs:collectgeometries GeoServer wps process as an input into gs:GenerateTransects to combine shorelines
Created a protected shoreline color set of 232 distinct colors. This needs to be pared down after user input