Carolinas Coast

This page serves at a table of contents that points Carolina Coast website development related activities.

Related links

• Production interface, http://www.carocoops.org/carolinas
• Development interface, TBA

Hot topics

Front burner (read this if nothing else)

This section will describe what is being worked on right now as well as progress or immediate action items that require the group's attention.

• All obs are updating well.
• Submaps are working. Susanna will tweak the radar loop which seems quirky.
• NHC announcements are part of the data sweep. These were not enabled during Ernesto.

The prioritized plan

• The CC team has 3 main objectives to achieve ASAP (over the next month), and in order of priority, these are:
  1. Reduce observation update lags. DONE!
  2. Complete cosmetic interface work.
     1. Make zoom boxes work.
     2. Elminate Internet Explorer problems on tides page.
  3. Expand the map to include identified parts of N FL
  4. Incorporate updates and special marine warning (polygon warnings) into the Hazards page. Now syncing w/ NHC.

Technical next steps

1. bugs to be fixed
   1. IE: Once zoomed in, clicking on zoom out causes browser crash.
   2. IE: I clicked on the red (NOS tide station) dot at Morehead City, but the small graph didn’t appear in the bottom right corner. I then clicked on all of the red dots but not Tide Station data appeared.
   3. ALL: Radar loop doesn't seem to work well.
2. Charlton waiting on feedback from John re. forecast hazard polygons.

Wish list

The following bullets are in no particular order. They will get bumped up to the list above (under prioritized plan) when there is room in the queue. And not all wishes will be granted since the team needs to yay or nay each one.

• Plan for and execute deployment of CC to a NWS server.
• Genericize the code so that it could work for any region.
• Clicking on a hazard pops up the hazard text and the hazard polygon (similar to when you click on an obs site that has a hazard associated w/ it). Also include well konwn marine locations.
• Make sure that nothing is listed as "Marine Warning"; they should all be "Special Marine Warnings".
• Add radio button togle for marine break points to be displayed.
• Forecast page : assign correct buoy to each obs zone for the "current conditions" box.
• Make sure hazards tab is flashing when there is a hazard.
• Remove credit descriptions on some of the images.
• Develop point-and-click capability to produce point specific forecasts utilizing NDFD
• OBSERVATIONS: On the observations for the buoys, if the link is to a CDIP buoy we'd would like to see an additional option to link to the Scripps page (provides more information about the breakdown in the various wave trains than the NDBC page).
• HAZARDS: Consider adding a link to NOS's Notice to Mariners (updated every couple of weeks). EKA has exchanged e-mails with John Kelley of the the NOS nowCOAST page and suggested that they add this -- if they do, another link here would be beneficial.
• SST: Very nice. Is there a way to include the contours and well as the image or to be able to mouse over and read out the SST like it does the lat/long? The SST is very important to albacore fisherman and often there is not enough temperature demarcation in the image to determine the exact temperature.
• ANOTHER MAP OVERLAY: In EKA's communications with nowCOAST, they suggested adding the NOS Nautical Charts as a separate layer. They agreed, but due to staffing it may take them awhile to implement. If they can't get to it, this is another suggestion for this webpage or to link to theirs. There may be other on-going discussions with the nowCOAST people since it seems there is some duplication of data on the two pages.
• How about a link to the model (WaveWatch) output bulletins (at output points)? Hopefully our official forecasts with a PFM type output would replace these bulletins, but until then they do provide a wealth of information.
• As an additional overlay, similar to radar, satellite imagery would be very beneficial (vis, IR, fog channels, especially -- user selectable).

Techo babble

Visit CarolinasCoastLite for details on a possible backend and frontend approach.
to top