Section 1 - discussion topics
#new servers - hardware provider, initial os, config profile ?
#ideal arch/application/server configuration discussion
#deep storage/archive ??? policy? main focus is providing longer term yearly type archival of data files, probably in formats which are simpler desktop/end user oriented(CSV, shapefile, etc) since the data will need to outlive the online web/application development space NODC, etc policy? usage?
#tech review process ?
#documentation ?
#dmac submission
- secoora netcdf/vocab
- obskml format/vocab, (tbd)dsi schema/vocab
- (tbd)secoora netcdf <-> obskml/dynamicSensorInventory mapping
- xenia db/products
Section 2 - possible server configuration(s)
server1 webserver
main focus is providing initial web access to webpages and associated data files/services would have say a minimum of 50 to 100 GB of immediate file storage available for application data file caching
zope/plone
trac
openlayers ? simple browser-based javascript/ajax map interaction ?
http://secoora.org/maps/dynamic
#optimization
cachebot
web file/service throttling ? google analytics? web server log usage analysis
php? javascript
server2 GIS/mapserver (open-source Minnesota mapserver for Secoora case)
main focus is providing map images from associated geospatial data say in one of three base file formats:
dan - mapserver install documentation
http://code.google.com/p/rcoos/wiki/MapserverNotes
- raster image + world(.wld) file
- shapefile
- geospatial sqlite file (html/table content type links)
should provide WMS/WMS-GFI/WFS access to map layers (existing openlayers as test? which layers learn with? include?)
OGR - batch geospatial file processing ?
optional? postgresql+postgis relational database
server3 database and/or file/product server - optional ?
main focus is providing support to spatially enabled postgresql+postgis database
If move to sqlite focused, file passing architecture, can we remove the need for a database specific server?
instead maybe focus on:
#server3a file/product server
main focus are to provide some additional quickly available file storage space(say 200-1000 GB) and data/product processing capacity
===================== #additional applications - put on webserver? separate product server(s)?
perl - packages DBI, LibXML
gnuplot
#files
http://secoora.org/data - various formats all_obs, by_obs latest/recent/weekly/monthly(CSV,shapefile,KML,sqlite db,georss)
ObsRegistry? (http://obsregistry.org)
#services
DODS/OPeNDAP
OGC SOS,etc (IOOS DIF - pySOS(jesse?), Oostethys)
telemetry/qc processing of original or other data providers to secoora netcdf ?
Scout - ongoing data aggregation (does not have to be a high-end server)
Section 3 - near-term development
develop
obskml/xenia switch for scout and tables - understand/ok ? make sure equivalent, summary log check
rcoos - update sqlite platform links for html_tables out
sqlite time_series graphs, html table links
top_of_hour trigger
'dynamic' sensor inventory (dsi)
instrument/event metrics/notification
IOOS DIF SOS, XML feeds for Secoora
status - waiting some for any final tweaks in design process on DIF side and validation test via CSC before moving forward
RENCI interaction ?
status - renci is pulling Secoora obs via ObsKML into the ODM database
other obs of opportunity ?
vembu - tampa area hf radar
adcp bin currents, graphs
hf radar - wave height
implement
html_table approach, breakout by_obs?
georss, etc link?
qc in netcdf at data providers?
bonus
sqlite query wrapper
general sqlite table/html/ogr-GFI to replace imagemaps/shapefiles?
internal/third party - training to utilize desktop tools/data maps/feeds
optimization
web throttling, cachebot ?
layer performance (firebug analysis)
google analytics / webserver log analysis - file/product detail proxy for better usage tracking?
data/processing/product redundancy
Section 4 - documentation
jesse/dan - openlayers/ajax proxy
dan - mapserver install http://code.google.com/p/rcoos/wiki/MapserverNotes
sensor metrics jesse - cgi/wms map layers optimize ?
jeremy - xenia/sqlite products website
jeremy/dan/jesse
secoora netcdf <-> obskml/dynamicSensorInventory mapping
