Difference between revisions of "Geodata Committee Sixth Meeting"

From OSGeo
Jump to navigation Jump to search
Line 33: Line 33:
  
 
* Current Status of Telescience hosting. The infrastructure is
 
* Current Status of Telescience hosting. The infrastructure is
−
  set up, and users who are looking to contribute to the effort should
+
set up, and users who are looking to contribute to the effort should
−
  be able to get accounts -- talk to the System Administration
+
be able to get accounts -- talk to the System Administration
−
  Committee for access.
+
Committee for access.
 
* What kind of Data display framework is necesary for the geodata
 
* What kind of Data display framework is necesary for the geodata
−
  repository to start with? Wiki was discussed: In the backend,
+
repository to start with? Wiki was discussed: In the backend,
−
  structured metadata will be stored, but the wiki-nature will allow
+
structured metadata will be stored, but the wiki-nature will allow
−
  for descriptive (non-normative) content to be added, which may later
+
for descriptive (non-normative) content to be added, which may later
−
  migrate to metadata storage when a more permanent solution arises.
+
migrate to metadata storage when a more permanent solution arises.
 
* Data storage should have three 'levels' of data:
 
* Data storage should have three 'levels' of data:
 
* Raw files. (Shapefiles, images, etc.) These would be designed for
 
* Raw files. (Shapefiles, images, etc.) These would be designed for
−
    use in cases where the default styling is 'not good enough' 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
+
users who are attempting to use the data, or cases where data
−
    processing is required, or whatever.
+
processing is required, or whatever.
 
* WMS Server: For cases when you need to have the full WMS support,
 
* WMS Server: For cases when you need to have the full WMS support,
−
    there should be WMS servers available for datasets where it is
+
there should be WMS servers available for datasets where it is
−
    applicable. (WFS, and other similar OGC web services, would also
+
applicable. (WFS, and other similar OGC web services, would also
−
    fit here.)
+
fit here.)
 
* Tiled Server: Datasets where tiling is applicable would have
 
* Tiled Server: Datasets where tiling is applicable would have
−
    support for making fast, cached requests against tiled-on-disk
+
support for making fast, cached requests against tiled-on-disk
−
    datasets. nhv and others express an interest in getting a standard
+
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
+
for tile caching set up before we do too much work on this aspect
−
    of it.
+
of it.
  
 
On the agenda, but not covered, were some visual suggestions for how
 
On the agenda, but not covered, were some visual suggestions for how
Line 60: Line 60:
  
 
* OpenLayers for Raster/Vector data? Easy to set up, might not be
 
* OpenLayers for Raster/Vector data? Easy to set up, might not be
−
    full featured enough for some people?
+
full featured enough for some people?
 
* Perhaps Ka-Map's tile.php as cached layer to feed both kamap and
 
* Perhaps Ka-Map's tile.php as cached layer to feed both kamap and
−
    openlayers?
+
openlayers?
 
* Single-image screenshots for Raster data as overviews
 
* Single-image screenshots for Raster data as overviews
 
* Vector dataset descriptions: What various attributes are/mean
 
* Vector dataset descriptions: What various attributes are/mean
−
    (better metadata)
+
(better metadata)
 
* GeoRSS out to get updates, with bounding boxes -- need to get some
 
* GeoRSS out to get updates, with bounding boxes -- need to get some
−
    way to display this data, does anything do GeoRSS rendering with
+
way to display this data, does anything do GeoRSS rendering with
−
    bounding boxes right now?
+
bounding boxes right now?
  
 
This was tabled until the next meeting.
 
This was tabled until the next meeting.

Revision as of 09:07, 29 June 2006

Meeting Info

 Chair: Jo Walsh
 Minutes: 
 IRC: #osgeo channel on irc.freenode.org
 Date: 2006-Jun-30 (at least in the Americas and Europe)
 Time: (fixed time)

People

Agenda

  • What more is needed to get OSGeo's Geodata Repository running at Telascience
    • User accounts to ask SAC for if needed
    • Responsibilities for different data sets
  • What kind of portal is needed - is wiki enough?
  • Some type of browsing interface for the data neccesary:
    • 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?
  • Free Earth Foundation working on distributed open geodata services targeted at WorldWind - how can we help?
  • Feedback appreciated on metadata client
  • Please feel free to add items here

Minutes

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.

Next Meeting

Retrieved from "http://wiki.osgeo.org/w/index.php?title=Geodata_Committee_Sixth_Meeting&oldid=5539"