Re: [las_users] dependency between 2 constraints

["Jerome King" <jejeking@xxxxxxxxxxx>]

Thanks Steve!

Could you or someone point me towards those LAS that shows what you are 
explaining?

I am not quit sure I really understand what you mean.
If I understand you correctly, I would have to design "categories" where the 
user would pick on one page the transect and then it would take the user to 
a "Station" page and finally to the query page? And this would mean 
redesigning all my xml files?

I think I am just not familiar with the term "intermediate products".
Is there a demo example with this "intermediate product" that come with the 
LAS that I could set-up like the insitu_demo or the section_demo?

Thanks,
Jerome






> From: Steve Hankin <steven.c.hankin@noaa.gov>
> To: Jerome King <jejeking@hotmail.com>
> CC: oar.pmel.las_users@noaa.gov
> Subject: Re: [las_users] dependency between 2 constraints
> Date: Thu, 21 Jul 2005 13:05:38 -0700
>
> Hi Jerome,
>
> There are a number of LAS examples out there that create what we have 
> called
> "intermediate products".  (Others can point you to the specific example 
> URLs.)
> We have used this approach for example as a mechanism to select individual
> profiles or satellite passes when the space time constraints are just too 
> blunt
> an instrument for the job -- i.e. the user specifies an approximate region 
> and
> requests this intermediate product;  the intermediate product presents a 
> list or
> clickable map showing all of the individual profiles or satellite passes in 
> that
> region; then the user is able to select individual obs. by clicking on the
> intermediate product.  The intermediate product actually sends a standard
> request back to the LAS Product Server.
>
> The same technique could be used on your problem.  Create an "intermediate"
> output product that shows all of the stations on a particular transect.  
> The
> user chooses from that list.
>
>     - steve
>
> =================================
>
> Jerome King wrote:
>
> > Hi all,
> >
> > I am using the insitu package with a database behind it.
> > I have a couple constraints defined in the user interface.
> >
> > For example, users can query data per transect.
> >
> > Now, there are stations located on those transects.
> > I was wondering how to go about having a second constraint where users 
> could
> > query data per stations but only the stations located on the transect 
> picked
> > in the first constraint would appear in the drop down menu.
> >
> > It would work a little bit like the output menu that is dependant on 
> what
> > you choose in the view menu.
> >
> > I tried replicating the same type of system used between the view and 
> output
> > menu to 2 constraints but it did not work.
> >
> > Another example where a constraint would be dependent on another 
> constraint:
> > If you have data collected at different stations and the data is 
> collected
> > at different depth strata for each stations. Then you want to have a 
> "depth
> > strata" constraint that is dependent on the "station" constraint. 
> Depending
> > on what station you pick, it would fill the dropdown menu for the depth
> > strata constraint with different values.
> >
> > Is there a way to do this and how?
> >
> > Thanks a lot!
> > Jerome.
>
> --
> º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤º¤ø,¸¸,ø¤º
>
> Steve Hankin, NOAA/PMEL -- Steven.C.Hankin@noaa.gov
> 7600 Sand Point Way NE, Seattle, WA 98115-6349
> ph. (206) 526-6080, FAX (206) 526-6744