What is the best method for managing large grid surface datasets for use in gINT Fences?

Hi all,

  1. What is the best method for managing large grid surface datasets for use in gINT Fences?
  2. Also, if I have elevation data in meters for a grid and want to display in feet in gINT, I wonder if there is a fairly easy method to do this?

We have a bunch of subsurface data that we'd like to plot on fences. We can convert in the form of GRIDS but it seems like my file sizes get really big for the GRIDs and gINT won't always import because they are big.

I was converting to a GRID ASCII in Surfer...it actually is called a Text GRID and it doubled the file size.

I haven't tried using GIS to convert to TIN.  I wonder if this is any better for file size?

Thank you,
Matt

Parents
  • Thanks everyone for the responses.

    As a follow up, Kirk has been helping me with my GRID data import.  What we determined is that gINT can't handle very large Grid sizes (ASCII GRID, TIN, or LandXML, even if you try to store as a .gsf.  I have had trouble with sizes around 25 MB.  I have seen others load sizes as large as 45 MB.

    Our work-around is to extract surface data along my baselines in GIS and export to gINT as alignments.  In some cases I have 6 to 7 datasets, so I have to create alignments in multiples of 3 datasets, alignments only store 3 z values at a time.  We then export FENCES with each alignment and then copy and paste to buffer our alignments into one final FENCE.

    It's not ideal but it does work.

Reply
  • Thanks everyone for the responses.

    As a follow up, Kirk has been helping me with my GRID data import.  What we determined is that gINT can't handle very large Grid sizes (ASCII GRID, TIN, or LandXML, even if you try to store as a .gsf.  I have had trouble with sizes around 25 MB.  I have seen others load sizes as large as 45 MB.

    Our work-around is to extract surface data along my baselines in GIS and export to gINT as alignments.  In some cases I have 6 to 7 datasets, so I have to create alignments in multiples of 3 datasets, alignments only store 3 z values at a time.  We then export FENCES with each alignment and then copy and paste to buffer our alignments into one final FENCE.

    It's not ideal but it does work.

Children
No Data