Select to view content in your preferred language

Pro loses connections to NetCDF files on every single close

383
6
03-04-2025 01:37 PM
DougBrowning
MVP Esteemed Contributor

This has been happening for months now and its driving me nuts.  Every single time I shut down Pro and reopen all my NetCDF file paths break.  Nothing has moved.

DougBrowning_0-1741124078977.png

Pro 3.3.1 and 3.1 so far.

Plus if you try to change the data source I get this.

DougBrowning_1-1741124178535.png

 

Can we please get this fixed. 

Also half the time the files won't even open from Add Data and I have to do it multiple times.  All of these are created from Pro and not external files.

Thanks

0 Kudos
6 Replies
ChrisUnderwood
Esri Regular Contributor

Hello @DougBrowning  , it's not uncommon for C:\TEMP folder access to be restricted by Security Policies. Does the problem still occur if you use an alternative folder ?

0 Kudos
DougBrowning
MVP Esteemed Contributor

I do not think so - c:\temp is one of the few I can use.  Been using it on that computer for over 4 years with no issue.  Does it on 2 different computers from multiple locations.  No other files in c:\temp have issues.

Any other ideas?

thanks

0 Kudos
ChrisUnderwood
Esri Regular Contributor

Can you post a small sample NetCDF file for us to try ?

DougBrowning
MVP Esteemed Contributor

It has done it on dozens of files as I have been making lots of time cubes.  The time cube ones do seen to have the most trouble but could be that is what I use most.  I have not found a pattern yet but it seems to take a reboot or more than one day for it to happen.  So if I add, save, close, open its ok.  If I come back in the next day, or a few days later, it breaks.  CRF files never a problem.

Also as a side note why can I not add .NC files from catalog but I can add CRF?

Thanks

Adding as a zip since I get this message with .nc

DougBrowning_0-1741190118278.png

 

0 Kudos
ChrisUnderwood
Esri Regular Contributor

The file paths are not lost (so far) and Set Data Source seems to work fine in ArcGIS Pro 3.4.2, if you are able to try that version ?

 

 

DougBrowning
MVP Esteemed Contributor

No we are on 3.3.1 for a bit now.  3.1 seemed the worst but I will keep trying it.

0 Kudos