[Geoserver-users] observing system template db schemas

Thanks for the info. I’m posting to the cc’d list as suggested. I agree as to the value of the abstract mapping approach, but I’d also be curious as to what others with similar rdb schema problems have developed.

Looking for others feedback on the below thread or links to similar geospatial observation schema interests.

Thanks
Jeremy

-----Original Message-----
From: Chris Holmes
To: Cothran, Jeremy
Sent: 8/21/06 9:39 PM
Subject: Re: observing system template db schemas

Sure, we’d definitely be happy to reference them. You might start with
an email to the user list, and then we can figure out a place in the
wiki to make the recommendation. Actaully one place you could put it is

the End User Experiences - I think that’s where people would look for
such advice.

Note that within our community there are several groups pushing a
different approach to the same problem. If you email the list Rob
Atkinson will likely jump in with some details. Basically the idea is
to let users configure their database however they want, and then define

a mapping in GeoServer to a well known schema. So even if people
already have a bunch of data defined then they can still output it in
the same way, the thought being it’s much harder to get people to agree
on how to set up their tables, but easier to define a schema and stick
GeoServer in between to do the translation. This work is unfortunately
a bit stalled at the moment, waiting for more funding, but there’s been
very good progress made. I believe we have a few ocean observing types,

an Rob’s work is definitely observation oriented. So yeah, just email
the lists, and we’ll figure out where to go from there.

best regards,

Chris

Cothran, Jeremy wrote:

Hi Chris,

I work with gathering ocean observing system data and displaying it as

various outputs as detailed at
http://www.ogleearth.com/2006/04/try_this_sensor.html

I’m working towards trying to develop some basic template database
schemas for the same observation types we get over and over again -
scalars, vectors, maps/collections as detailed at
http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/XeniaPackage

Is the GeoServer team interested in recommending or referencing these
types of geospatial observation database implementation schemas or can

they reference other development groups that are trying to develop a
consensus on relational database implementation schemas for
observation
system oriented work?

Thanks
Jeremy Cothran
Software Developer
http://carocoops.org
http://seacoos.org

!DSPAM:1003,44e53a9b233362223018498!


Chris Holmes
The Open Planning Project
http://topp.openplans.org
<<cholmes.vcf>>