You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FVCOM data we were testing dap2tin with were relatively small, around 50,000 nodes, and it wasn't too big a deal, but for the ADCIRC dataset I'm testing now, there are 400,000 nodes, and it takes 7 minutes to load a single time step, writing a 50MB XML file in the process. Probably a lot of this is a slow approach to writing the XML file, but it does really seem crazy to have to write such a file in the first place.
Has this been fixed yet, or if not, at least on an enhancement issue somewhere?
I notice that this guy apparently has a TIN generator, I wonder how he does it?
The text was updated successfully, but these errors were encountered:
@scw, do you know if there are any updates here?
Is it now possible to instantiate a TIN object from python in ArcPy?
If not, how would we go about getting someone's attention?
@scw, as I mentioned at the inaugural Ocean Summit a few years ago, it really sucks to have to write out ASCII LandXML data to instantiate a TIN object with specified topology (connectivity array):
https://github.com/rsignell-usgs/dap2arc/blob/master/src/dap2tin.pyt#L28
The FVCOM data we were testing dap2tin with were relatively small, around 50,000 nodes, and it wasn't too big a deal, but for the ADCIRC dataset I'm testing now, there are 400,000 nodes, and it takes 7 minutes to load a single time step, writing a 50MB XML file in the process. Probably a lot of this is a slow approach to writing the XML file, but it does really seem crazy to have to write such a file in the first place.
Has this been fixed yet, or if not, at least on an enhancement issue somewhere?
I notice that this guy apparently has a TIN generator, I wonder how he does it?
The text was updated successfully, but these errors were encountered: