[Thread Prev][Thread Next][Index]
Re: _id - please ASAP
Adam,
Several of the ferret scripts that create output graphics depend upon
the existence of the ProfID variable. If you simply leave the profID
<database_access> property blank:
<profID></profID>
the existing TMAPDBI database access code should create this variable
from you automatically.
If you've copied the TMAPDapper module you need to be sure you get rid
of these lines as well:
# The _id variable is a mandatory variable
# which needs no info from the LAS UI request, so it's set up here
$self->setVariableAttributes('_id', 'Profile ID',
"none",$self->{config}->{missing});
$self->{variables}->{_id}->{profID} = 1;
Then go and have a look at what TMAPDBI is doing to create this variable
on the fly.
-- Jon
Adam Baxter wrote:
I've been attempting to finish up the OPeNDAP module, but I've run
into some kinks.
What I've done is essentially copy the Dapper module in feeble hopes
that it might do the trick.
I've run into issues with the ProfID variable. regardless of whether
it's removed from the xml file or not, the program still looks for it.
I've removed mentions of it throughout the module, but I get different
errors looking for <ID>.
I've removed the ProfID from the request and left in the part in
getData, but it fails miserably.
Can anyone tell me where I've gone wrong?
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement