Meeting Summary

[Christopher Schmidt]

An IRC meeting of the Geodata Committee occurred today, from
11AM->12:30PM EDT. 

http://wiki.osgeo.org/index.php/Geodata_Committee_Sixth_Meeting

In the meeting, we discussed:

 * Current Status of Telescience hosting. The infrastructure is
   set up, and users who are looking to contribute to the effort should
   be able to get accounts -- talk to the System Administration
   Committee for access.
 * What kind of Data display framework is necesary for the geodata 
   repository to start with? Wiki was discussed: In the backend,
   structured metadata will be stored, but the wiki-nature will allow
   for descriptive (non-normative) content to be added, which may later
   migrate to metadata storage when a more permanent solution arises.
 * Data storage should have three 'levels' of data: 
    * Raw files. (Shapefiles, images, etc.) These would be designed for
      use in cases where the default styling is 'not good enough' for
      users who are attempting to use the data, or cases where data
      processing is required, or whatever.
    * WMS Server: For cases when you need to have the full WMS support,
      there should be WMS servers available for datasets where it is
      applicable. (WFS, and other similar OGC web services, would also
      fit here.)
    * Tiled Server: Datasets where tiling is applicable would have
      support for making fast, cached requests against tiled-on-disk
      datasets. nhv and others express an interest in getting a standard
      for tile caching set up before we do too much work on this aspect
      of it.

On the agenda, but not covered, were some visual suggestions for how
data should be exposed from the geodata repository browsing interface: 

    * OpenLayers for Raster/Vector data? Easy to set up, might not be
      full featured enough for some people?
    * Perhaps Ka-Map's tile.php as cached layer to feed both kamap and
      openlayers?
    * Single-image screenshots for Raster data as overviews
    * Vector dataset descriptions: What various attributes are/mean
      (better metadata)
    * GeoRSS out to get updates, with bounding boxes -- need to get some
      way to display this data, does anything do GeoRSS rendering with
      bounding boxes right now? 

This was tabled until the next meeting.

Jo offered 
 
  https://geodata.osgeo.org/source/browse/geodata/trunk/metadata/

as her work on a MetaData client, to collect data from shapefiles, etc.
and put it into a database.

At approximately this time, we reviewed the content of the meeting, and
adjourned for two weeks, same bat time, same bat channel.

Regards,

-- 
Christopher Schmidt
Web Developer