Implementing Dapper for in-situ profile data

[McCann, Mike]

Hi Thomas,

Yes, I would like to start the an implementation from your
software; and I understand the resource constraint from 
your end. 

I think we have a choice of 2 approaches: 1) adopt your
database schema and transfer our data to it, or 2) rewrite 
the access layer to match our existing schema.

Looking at your database schema and source code will help
us decide.

Thanks for offering to help. I hope I can return the favor.

-Mike

> -----Original Message-----
> From: Thomas LOUBRIEU [mailto:Thomas.Loubrieu at ifremer.fr] 
> Sent: Friday, October 27, 2006 6:50 AM
> To: McCann, Mike
> Cc: Joe Sirott; Tech DODS
> Subject: Re: Implementing Dapper for in-situ profile data
> 
> Dear Mike and Joe,
> 
> I would be happy to help you to implement your dapper-like server on 
> relational database.
> Our server has been developed in java (thanks to the dods.jar 
> API) and 
> it is running as a servlet in tomcat.  The oracle database 
> connection is 
> managed with a tomcat jdbc pool.
> 
> Unfortunatly, the software has not been design so that it could be 
> configured for different databases schemas, but it has been carefully 
> developed so that the database access layer is separated from the 
> opendap "presentation" layer.
> 
> It means that, if you're interested in using our software, 
> the only part 
> of code you should update is the database access layer (2 
> main classes).
> 
> If you want to start your implementation from our software, I 
> can send 
> you the source code and some documentation (javadoc in english but 
> design documents in french).
> 
> Knowing the amount of resources we have on that project for 
> the moment, 
> I cannot promise you very reactive assistance, but I hope the 
> software 
> will be updated in the coming months so that it will be fully 
> compliant 
> with dapper convention and more efficient (in answer delays).
> 
> Thomas
> 
> Joe Sirott wrote:
> > Hi Mike,
> >
> > Another possibility -- have you spoken to Thomas Loubrieu 
> at Coriolis 
> > about their Dapper compliant server (at 
> http://www.ifremer.fr/dap4cor/ 
> > <http://www.ifremer.fr/dap4cor/>) ? I believe that they 
> store all of 
> > their data in an Oracle database. I'm not sure if the software is 
> > publicly available or not.
> >
> > - Joe
> >
> > McCann, Mike wrote:
> >> DODS techies,
> >>
> >> The discussion over the dapper specification has been 
> interesting to follow.
> >>
> >> I would like to contribute to the discussion, but feel 
> that I need some experience with implementing a server for 
> our data which reside in a relational database.  
> >>
> >> I know that I could extract the data into EPIC-compliant 
> netCDF files and load them into dapper with dapperload.sh, 
> but am hoping that there might be a better way.  I've 
> experimented a bit with the OPeNDAP DRDS server but don't see 
> how I can write a das/dds to mimic the dapper spec, viz:
> >>
> >>   
> >>> -------------------------------
> >>>
> >>> Profile / Sounding Collection: (same as Dapper "CTD 
> measurements" example)
> >>>
> >>>  Sequence {
> >>>   lat, lon, time;
> >>>   id;       
> >>>   Sequence {
> >>>     z;		
> >>>     v1, v2, ...
> >>>   } obs;             
> >>>  } profile;         
> >>>
> >>> -------------------------------
> >>>     
> >>
> >>
> >> Is this possible with DRDS?  Or, is the reason there is so 
> much discussion regarding the spec is that this capability is 
> in the process of being implemented?
> >>
> >> Some guidance would be welcome and I'd be glad to 
> contribute if I can.
> >>
> >> -Mike
> >>
> >> --
> >> Mike McCann 
> >> Software Engineer
> >> Monterey Bay Aquarium Research Institute
> >> 7700 Sandholdt Road
> >> Moss Landing, CA 95039-9644
> >> Voice: (831) 775-1769 Fax: (831) 775-1646 http://www.mbari.org
> >>
> >>   
> >
> 
> -- 
> 
> 
> -------------------------------------------------------------
> Thomas LOUBRIEU
> IFREMER IDM/ISI
> BP70
> 29280 Plouzane
> FRANCE
>   
> email: Thomas.Loubrieu at ifremer.fr
> WWW  : http://www.coriolis.eu.org/cdc
> Tel.:  (+33) (0)2 98 22 48 53
> Fax:   (+33) (0)2 98 22 46 44 
> 
> -------------------------------------------------------------
> 
> 
>