I assume that you were in a linux environment on your ship's network?<br><br>Our aquisition and navigation software run only on Windows machines. Sidescan is processed on Windows, RTK GPS is on Windows, I have some flexibility on bathy processing but you can see the pattern...
<br><br>I just updated the cygwin version of grass 6.1.cvs and it doesn't have r.in.xyz.<br>Cygwin grass is kind-of a mixed bag anyway...<br><br>How much work is involved compiling Grass on cygwin? I've only compiled it on Linux.
<br><br><br><div><span class="gmail_quote">On 8/24/06, <b class="gmail_sendername">Patton, Eric</b> <<a href="mailto:epatton@nrcan.gc.ca">epatton@nrcan.gc.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just to chime in on Hamish' r.in.xyz - I just got back from a field survey<br>of the Bay of Fundy where 56GB of swath sonar (Simrad EM1002) was collected.<br>After exporting each survey day from Caris HIPS as xyz, I've used
r.in.xyz +<br>r.patch to import the entire 56GB into Grass with no problems. I've always<br>felt that r.in.xyz runs very quickly given the size of each xyz dataset.<br><br>~ Eric.<br><br>-----Original Message-----<br>From:
<a href="mailto:grassuser-bounces@grass.itc.it">grassuser-bounces@grass.itc.it</a><br>To: Jonathan Greenberg; David Finlayson<br>Cc: <a href="mailto:grassuser@grass.itc.it">grassuser@grass.itc.it</a>; Helena Mitasova; <a href="mailto:Andrew@grass.itc.it">
Andrew@grass.itc.it</a>; Danner<br>Sent: 8/24/2006 2:50 AM<br>Subject: Re: [GRASS-user] RE: [GRASSLIST:1174] Working with very large<br>datasets<br><br>David Finlayson wrote:<br>> I am working with an interferometric sidescan SONAR system that
<br>> produces about 2 Gb of elevation and amplitude data per hour. Our raw<br>> data density could support resolutions up to 0.1 m, but we currently<br>> can't handle the data volume at that resolution so we decimate down to
<br>> 1 m via a variety of filters. Still, even at 1 m resolution, our<br>> datasets run into the hundreds of Mb and most current software just<br>> doesn't handle the data volumes well.<br>><br>> Any thoughts on processing and working with these data volumes (LIDAR
<br>> folks)? I have struggled to provide a good product to our researchers<br>> using both proprietary (Fledermaus, ArcGIS) and non-proprietary (GMT,<br>> GRASS, my own scripts) post-processing software. Nothing is working
<br>> very well. The proprietary stuff seems easier at first, but becomes<br>> difficult to automate. The non-proprietary stuff is easy to automate,<br>> but often can't handle the data volumes without first down sampling
<br>> the data density (GMT does pretty well if you stick to line-by-line<br>> processing, but that doesn't always work).<br>><br>> Just curious what work flows/software others are using. In particular,<br>> I'd love to keep the whole process FOSS if possible. I don't trust
<br>> black boxes.<br><br></blockquote></div><br><br clear="all"><br>-- <br>David Finlayson