Geodata Committee Sixth Meeting - Revision history

Neteler at 15:33, 23 August 2007

2007-08-23T15:33:41Z

Wiki-JoWalsh: /* Minutes */

2006-07-12T18:53:37Z

Minutes

Neteler: moved people into minutes

2006-06-30T10:04:54Z

moved people into minutes

Arnulf: /* Minutes */ formatting

2006-06-29T17:27:43Z

Minutes: formatting

Wiki-Putler: /* People */

2006-06-29T17:27:39Z

People

Wiki-Bitner: /* Minutes */

2006-06-29T17:07:06Z

Minutes

Wiki-Bitner: /* Minutes */

2006-06-29T17:05:57Z

Minutes

Wiki-Bitner: /* Minutes */

2006-06-29T17:04:52Z

Minutes

Wiki-Dsampson: /* People */

2006-06-29T16:43:05Z

People

Wiki-Pnaciona: /* People */

2006-06-29T15:13:26Z

People

← Older revision		Revision as of 15:33, 23 August 2007
Line 62:		Line 62:

	== Next Meeting ==		== Next Meeting ==
		+
		+	[[Category:Public Geospatial Data Committee]]

@@ Line 25: / Line 25: @@
 == Minutes ==
-People: David Bitner, Christopher Schmidt (http://crschmidt.net/), [[User:Pnaciona|Perry Nacionales]], Dave Sampson (http://cemml.carleton.ca:8080/OGUG/Members/drsampson/emp/), Dan Putler, [[User:JoWalsh|zool]], [[User:Neteler|Markus Neteler]]
+People: David Bitner, Christopher Schmidt (http://crschmidt.net/), [[User:Pnaciona|Perry Nacionales]], Dave Sampson (http://cemml.carleton.ca:8080/OGUG/Members/drsampson/emp/), Dan Putler, [[User:JoWalsh|zool]], [[User:Neteler|Markus Neteler]], Arnulf Christl
 In the meeting, we discussed:

@@ Line 6: / Line 6: @@
    Date: 2006-Jun-30 (at least in the Americas and Europe)
    Time: ([http://timeanddate.com/worldclock/fixedtime.html?month=6&day=29&year=2006&hour=15&min=0&sec=0&p1=0 fixed time])
 == Agenda ==
@@ Line 31: / Line 24: @@
 == Minutes ==
 In the meeting, we discussed:

@@ Line 33: / Line 33: @@
 In the meeting, we discussed:
-* 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 be able to get accounts -- talk to the System Administration Committee for access.
-set up, and users who are looking to contribute to the effort should
+* 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
+# 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.
-use in cases where the default styling is 'not good enough' for
+# 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.)
-users who are attempting to use the data, or cases where data
+# 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
+* 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 openlayers?
 * 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 way to display this data, does anything do GeoRSS rendering with
 bounding boxes right now?
@@ Line 77: / Line 56: @@
 https://geodata.osgeo.org/source/browse/geodata/trunk/metadata/
-as her work on a MetaData client, to collect data from shapefiles, etc.
+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
+At approximately this time, we reviewed the content of the meeting, and adjourned for two weeks, same bat time, same bat channel.
 == Next Meeting ==

@@ Line 12: / Line 12: @@
 * Perry Nacionales
 * Dave Sampson http://cemml.carleton.ca:8080/OGUG/Members/drsampson/emp/
 == Agenda ==

← Older revision		Revision as of 17:04, 29 June 2006
Line 30:		Line 30:

	== Minutes ==		== 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 ==		== Next Meeting ==

@@ Line 10: / Line 10: @@
 * David Bitner
 * Christopher Schmidt, http://crschmidt.net/
 == Agenda ==