Hey Sean,
Thanks for getting back to me. I was still getting the same symptoms
earlier today. Did it work on second inquiry for you?
I did make a change to that last file so the dim's match up with previous.
After I did that, checked again to make sure that wasn't causing the
problem. Seems i still am getting the same IndexError i was getting, so
this (as you mentioned) is not the root of the problem.
On Fri, Jan 31, 2020 at 11:03 AM Sean Arms <sarms@xxxxxxxx> wrote:
> Greetings Spicer,
>
> It looks like you have solved the issue? I was having problems the other
> day as well. I downloaded the files locally to see if I could reproduce the
> issue, and I am unable to do so now. However, I do see something that might
> cause an issue down the road. The dimension order on some of the variables
> in the latest file does not match what is in other files. For example, if
> we compare the latest file:
>
>
> https://chldata.erdc.dren.mil/thredds/dodsC/frf/geomorphology/DEMs/surveyDEM/FRF_20200110_1180_FRF_NAVD88_LARC_GPS_UTC_v20200113_grid_latlon.nc.dds
>
> with next latest file:
>
>
> https://chldata.erdc.dren.mil/thredds/dodsC/frf/geomorphology/DEMs/surveyDEM/FRF_20191206_1179_FRF_NAVD88_LARC_GPS_UTC_v20191209_grid_latlon.nc.dds
>
> The dimensionality of latitude, longitude, northing, and easting switch
> from (xFRF, yFRF) (20191206) to (yFRF, xFRF) (20200113).Might not be a big
> issue overall since the use of an NcML file on the server (as opposed to
> NcML directly in the catalog) uses the first file of the aggregation as
> template.
>
> Cheers,
>
> Sean
>
>
> On Wed, Jan 29, 2020 at 3:03 PM Spicer Bak <spicer.bak.frf@xxxxxxxxx>
> wrote:
>
>> hello TDS community,
>> I have a problem I'm quite pickled on. We had a dataset that was working
>> fine until (i think) we pushed the latest file. Our server is continually
>> updated with new files and all of the other datasets seem to work fine.
>>
>> I'm able to get the data from the individual file URLS, but not the time
>> concatenated ncml file. I can display the file or variables, but not
>> obtain any of the data through OPeNDAP, but i'm able to see the data
>> returned via the "get ASCII" button on the OPeNDAP page. The below python
>> script demonstrates the problem:
>>
>> # success with ncml:
>>
>> https://chldata.erdc.dren.mil/thredds/dodsC/frf/geomorphology/DEMs/surveyDEM/surveyDEM.ncml.ascii?latitude%5B0:1:0%5D%5B0:1:0%5D,time%5B0:1:425%5D,elevation%5B0:1:0%5D%5B0:1:0%5D%5B0:1:0%5D
>>
>> # Failure with python (matlab as well)
>> import netCDF4 as nc
>> for url in urls:
>> print(nc.Dataset(url)['time'])
>> variables= nc.Dataset(url).variables.keys()
>> for var in variables:
>> try:
>> nc.Dataset(url)[var][0]
>> print('Success! {} from {}'.format(var, url))
>> except IndexError as e:
>> print("won't load variable {} from {}".format(var, url))
>>
>> print(' {}'.format(e))
>>
>> Any help would be much appreciated!
>>
>> --
>> +++++++++++++++++++++++++++
>> Spicer Bak, PhD
>> USACE CHL Field Research Facility
>> 252-305-9975
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> thredds mailing list
>> thredds@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> https://www.unidata.ucar.edu/mailing_lists/
>>
>
--
+++++++++++++++++++++++++++
Spicer Bak, PhD
USACE CHL Field Research Facility
252-305-9975
