[Thread Prev][Thread Next][Index]

Re: [las_users] Ferret init files used in LAS


LAS does not expect an init_script as part of the product_server properties, so that property is just going to be ignored. We didn't consider that somebody might want the opening plot to look different from what happens when you select that data set.

You might be able to accomplish having a custom opening plot by making a new "private" operation. Copy the operation that is being used to make the default plot in the operationsV7.xml. Give it a new ID and mark it with the private="true" attribute. You could then use that operation for the initial plot and customize it to your liking, but because it's "private" it would not show up as an operation when you select the data set. I haven't actually tried this, but something along those lines might be made to work.


On Wed, Mar 2, 2016 at 2:02 PM, Oots, Penny C. (LARC-E301)[SCIENCE SYSTEMS AND APPLICATIONS, INC] <penny.c.oots@xxxxxxxx> wrote:
I am trying to use a different Ferret init script ( <init_script>Script1_init</init_script>  ) for the default_varid parameter under the product server section  in las.xml  than the Ferret init script to be used in the xml file for the same parameter in ….tomcat/content/las/conf/server ( <init_script>Script2_init</init_script>).  I would like to be able to differentiate between the display of the parameter as the default and actual use of the parameter.  It appears that the the init script specified in las.xml (in this case Script1_init) is being ignored or overridden by Script2.  

Any suggestions or workarounds would be appreciated.
Penny Oots

[Thread Prev][Thread Next][Index]

Contact Us
Dept of Commerce / NOAA / OAR / PMEL / TMAP

Privacy Policy | Disclaimer | Accessibility Statement