Le 22/07/2018 à 11:45, Samuel Gougeon a écrit :
Hello Lester,
Le 22/07/2018 à 11:12, arctica1963 a écrit :
Hello,
I am looking to use netCDF files generated from the GMT software in
Scilab
6.0.1, but there is no easy way to work the problem other than
exporting the
data out from the binary grids to either XYZ or ESRI Ascii raster. The
latter is a more compact form with the basic structure of a header
describing the data limits and structure:
ncols 1200
nrows 1200
xllcorner -10 Lower-left X (Long-Lat limits -10/10/-10/10
yllcorner -10 Lower-Left Y
cellsize 0.0166666666667 - increment = 1 arc minute
nodata_value -9999
451.343170166 436.005554199 443.061035156 443.665924072
465.607574463
492.191741943 476.50994873 452.265014648 451.439880371
461.659393311 ......
...
... all of the Z-values
...
-4323.2890625 -4315.12451172 -4307.19384766 -4305.27490234
-4311.49902344
-4317.90771484 -4324.23046875 -4320.47070313 -4308.60107422
-4292.62011719
-4280.39697266
This is a moderately large file ~20 mB or so. Is there a way to reliably
read this structure and vectorise X, Y, and Z? The data I am looking
at is a
grid so want to work on the whole grid as eith DEM data or gravity etc.
As a test, I converted the grid to xyz, and tried csvRead, having
replaced
the spaces (which were not a constant number of spaces between
values) with
commas. The file was in excess of 50 mb, so not that huge really, but
csvRead always failed to read all the file and drop out at one
specific line
(~7608) with a message of inconsistent column numbers, i.e. it though
there
were only 2 columns when in reality the whole thing was 3 (checked in
the
program Surfer). When one looks at the line specified, it is clearly 3
columns.
Do you really get this error with the new nightly built Scilab release
http://www.scilab.org/en/development/nightly_builds/branch60
indicated by Antoine E. yesterday?
It is due to the same mgetl() bug (for Windows), that spreads all over
Scilab 6.0.1.
The continuous build
https://build.scilab.org/view/Scilab%206.0/job/scilab-6.0-windows-64/
can also be used without waiting for any publication delay.
To me, the major advantage of the continuous built vs the nightly built
is that,
beside there is no delay, its SCIHOME directory and configuration files
are stable:
the version can be updated as often as required. Each time you get back
the config,
history, Scinotes config, etc as you left them from the previous version.
_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users
