using dap2arc and multidimensional tools via python to visualize netdcf results

[ashleytarver1]

HI all

Im in a bit of a pickle.  I'm graduating late, and I'm at a roadblock for my thesis.  I need to pull netcdf files into Arc to visualize some results. I've downloaded both the zipped open2arc folder an the multidimensional tool service package, but now I'm stuck. 

Although I am somewhat familiar with Arc, I have no experience with python or programming.  Which text file from the folders I downloaded need to be copy and pasted into the python window under the "geoprocessing" tab in order to make the tools available for use?

Any suggestions are appreciated!

Thanks in advance!

Ashley

[ashleytarver1]

OK! Progress has been made, this pleases me!  I installed the module, which enabled me to access the dap2tin toolbox in the catalogue window.

I accessed the fortran 74 file (fort.74.nc) from the link here http://opendap.renci.org:1935/thredds/catalog/tc/isaac/catalog.html

It shows the wind velocity at all the nodes on my unstructured grid. 

Then I typed in the corresponding date for Hurricane Isaac (the storm simulated within the file), and chose the "windx" variable from the drop-down window, which will show the east/west wind velocity of the storm.

Unlike the video, Arc10.2 has an additional line in the toolbox that requires the spatial reference.  I am unsure what to put here, since the output was created on a lat/long grid, so I chose the corresponding State Plane Coordinate system for Louisiana (the area of interest).

I chose a location (my C drive) for the output TIN, then clicked "OK", but  a box pops up with red letters that read:

KeyError 'lon'

Failed to Execute dap2tin

Do you know what I am doing wrong?  The file i'm attempting to pull in is a netcdf format (fort.74.nc), which should already have the mesh built in.

Since I was unsure what input value I should set as the vertical layer,  I tried both "0" and "-1", but to no avail.  The same error I described above pops up.

Thanks!

[IanMurray]

can you put in a screenshot of your input parameters you are using for the tool?

[ashleytarver1]

Sure. This is the most recent attempt and result

[ashleytarver1]

When I try to save the output to my C drive another way:

On Thu, May 7, 2015 at 7:44 PM, Ashley Tarver <tarverashley190@gmail.com>

[IanMurray]

run it again, and scroll up and get the complete error message.  Usually it will say what line of the code it is failing on.

[ashleytarver1]

Hi all

Do you guys know if I am allowed to contract out for hire on this site to perform the specific python task I described above?

Of course, I would acknowledge their work in my thesis.  I just have no programming experience and I need to focus on other areas.

Thanks

[IanMurray]

I can try to help you out with this further, its just a matter of having the time/access I need to do work on something like this.  Like you I'm a grad student and I'm off for the summer. I am not working in the lab where I was helping you with this previously and I can't do any work while at my day job.  I can put some time in later this week to follow up on where I got to, and from there I'm hoping its pretty simple to get what you were needing.

[IanMurray]

Okay, some progress, some not.

To fix the problem of lat/long key errors, they key needs to be changed to y and x in lines 296 and line 297.  I missed mentioning this earlier, apologies

Next problem is the nv dictionary key on line 314. 

OPeNDAP Dataset Query Form

On the query form of the datasets this was developed on, there is a variable nv, which does not exist in the same format on the query form you are using, yours has nvdll, nvell, and nvel. I believe you need a combination of several of those for this to work, but not sure which since I'm not overly familiar with the data. 

I know Curtis mentioned getting in contact with the person who developed it, and I would second that, since I'll admit I'm a bit out of my depth here, since I don't know this data or some of the modules he is using at all.  I think if you got the nv problem fixed it would work, since x,y,time, and nv are the parameters for the land xml which makes the tin.