Loading data with same Parameter name but different parameter long_name fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load an OPeNDAP dataset
2. Load another OPeNDAP dataset that has the same Parameter name, but a 
different long_name
3. Try to access the Parameter from the second dataset

What is the expected output? What do you see instead?

The Parameter from the second dataset is not accessible.

Not sure what is to happen in this scenario.  Currently, the load appears to 
fail for not finding a parameter match on the second load.  Perhaps an 
exception should be thrown on the second load informing the data janitor that 
they need to choose a different parameter name or use the same long_name as 
what exists in the database.

Original issue reported on code.google.com by MBARIm...@gmail.com on 12 Jun 2012 at 10:43

[GoogleCodeExporter]

Actually addParameters() in DAPloader.py does not compate long_name. It 
compares only the Parameter name. The first entry in the Parameter table and 
its attributes (standard_name, units, long_name, origin) are the ones that are 
used for each successive Parameter that has the same name.  The problem with 
the waveglider data is that the names in the netCDF file changed to TEMP and 
PSAL, while the include_names in loaders/CANON/loadCANON_may2012.py were stil 
'temp' and 'salinity'.  These were changed to TEMP and PSAL and now the data 
load.

Original comment by MBARIm...@gmail.com on 13 Jun 2012 at 6:02

• Changed state: Fixed