Hello GRASSLIST,
I write you from Spain and I'm just starting with GRASS. I have a txt file
with lots of point extracted from a 1:5000 Dgn Microstation archive. I have
created a location and i have specified the UTM projection and zone,
(Hayford 30, i think). Then i load the text file with
s.in.ascii sites=heights input=local.txt d=3 fs=,
Then i prepared the region with g.region. In the menu i select use the
sites file to determine the region.
Now i would like to see my points, I do
d.mon x0
d.sites heights color=white
Then my computer seems to be doing 'something', but finally nothing appears
in the monitor x0, and no error message appears.
I'd like use this data to interpolate the DEM of my study region. I think
my problem is related to the region definition but not sure.
I have no problem to explore the spearfish location, every raster, vector
and sites is displayed correctly.
Coul anybody help me?
If it can help, I'm working on Debian Linux, and my Grass version is 5.0.2,
that i have compiled.
--
Antonio Jesús Sánchez Padial
Oviedo SPAIN
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
I am still having some problems with the transition from
pre3 to 5.0.2 on Cygwin/WinGRASS/Xserver.
- Starting the monitors gives warnings (but the behavior
seems otherwise fine). I am unable to get a clean start even
after running various d.mon options. The problem is in 5.0.2
but not pre3 (I reverted and checked.)
GRASS:~ > d.mon stop=x0
Monitor 'x0' terminated
GRASS:~ > d.mon start=x0
Socket is already in use or not accepting connections.
Use d.mon to select a monitor
Problem selecting x0. Will try once more
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
- spearfish (the version I downloaded with pre3 and the
newest version) is fine with 5.0.2
- vector maps and site maps that I created in pre3 seem to
be fine 5.0.2
- raster maps that I created in pre3 have strange values
that look like confusion among datatypes, e.g., huge
negative numbers. I told grasslist that I would recreate
the data in 5.0.2 and then report, and I haven't had a
chance to do so yet. I will report as soon as I can, but
the project is dauntingly large.
- one suggestion was change in lzw algorithm to zlib, but
the lzw algorithm was switched between beta10 and beta11,
i.e., well before pre3. From the beta11 change log:
# LZW removal switched on: GRASS is using DEFLATE/zlib now (Eric G. Miller)
Best regards,
Michael
Michael Ash, Assistant Professor
of Economics and Public Policy
Department of Economics and CPPA
University of Massachusetts
Amherst, MA 01003
Tel 413-545-6329 Fax 413-545-2921
Email mash@econs.umass.edu
http://people.umass.edu/maash
Michael Ash wrote:
I am still having some problems with the transition from
pre3 to 5.0.2 on Cygwin/WinGRASS/Xserver.
- Starting the monitors gives warnings (but the behavior
seems otherwise fine). I am unable to get a clean start even
after running various d.mon options. The problem is in 5.0.2
but not pre3 (I reverted and checked.)
GRASS:~ > d.mon stop=x0
Monitor 'x0' terminated
GRASS:~ > d.mon start=x0
Socket is already in use or not accepting connections.
Use d.mon to select a monitor
Problem selecting x0. Will try once more
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
The warnings are a known issue on Cygwin.
- spearfish (the version I downloaded with pre3 and the
newest version) is fine with 5.0.2
- vector maps and site maps that I created in pre3 seem to
be fine 5.0.2
- raster maps that I created in pre3 have strange values
that look like confusion among datatypes, e.g., huge
negative numbers. I told grasslist that I would recreate
the data in 5.0.2 and then report, and I haven't had a
chance to do so yet. I will report as soon as I can, but
the project is dauntingly large.
Odd; the internal format for integer maps hasn't changed since 4.3.
Is it possible that the maps were created in text mode? This will
cause \x0a to be written as \x0d\x0a.
--
Glynn Clements <glynn.clements@virgin.net>
Recap of the problem:
> I am ... having some problems with the transition from
> pre3 to 5.0.2 on Cygwin/WinGRASS/Xserver.
>
> - raster maps that I created in pre3 have strange values
> that look like confusion among datatypes, e.g., huge
> negative numbers. I told grasslist that I would recreate
> the data in 5.0.2 and then report, and I haven't had a
> chance to do so yet. I will report as soon as I can, but
> the project is dauntingly large.
I was able to bypass some of the steps in recreating the
data from scratch. Using s.to.rast on pre3 sites maps I
successfully created 5.0.2 raster maps that have the right
properties (values as expected, no more huge negative
numbers, etc.)
Glynn Clements wrote:
Odd; the internal format for integer maps hasn't changed
since 4.3. Is it possible that the maps were created in
text mode? This will cause \x0a to be written as \x0d\x0a.
I am not sure I understand what is meant by "maps ...
created in text mode." Text mode in GRASS? The raster maps
were in any case floats or doubles, not integers.
Anyway, I think that I have resolved the problem
(functionally) but I remain a bit puzzled by what happened.
My thanks to the many grasslist participants, especially
Glynn, Roger, and Moritz who contributed ideas and
solutions.
Best regards,
Michael Ash, Assistant Professor
of Economics and Public Policy
Department of Economics and CPPA
University of Massachusetts
Amherst, MA 01003
Tel 413-545-6329 Fax 413-545-2921
Email mash@econs.umass.edu
http://people.umass.edu/maash
Michael Ash wrote:
> Odd; the internal format for integer maps hasn't changed
> since 4.3. Is it possible that the maps were created in
> text mode? This will cause \x0a to be written as \x0d\x0a.
I am not sure I understand what is meant by "maps ...
created in text mode." Text mode in GRASS?
Text mode in Cygwin. Cygwin does automatic CRLF <-> LF translation in
certain circumstances. Rhis can be useful for reading and writing text
files, but will corrupt binary files.
The raster maps
were in any case floats or doubles, not integers.
Well, 4.3 didn't support floating-point, but the floating point format
5.0 hasn't changed since it was introduced (it uses XDR).
--
Glynn Clements <glynn.clements@virgin.net>
On Sat, May 24, 2003 at 05:12:51AM -0400, tonisan@cocoguawa.com wrote:
Hello GRASSLIST,
I write you from Spain and I'm just starting with GRASS. I have a txt file
with lots of point extracted from a 1:5000 Dgn Microstation archive. I have
created a location and i have specified the UTM projection and zone,
(Hayford 30, i think). Then i load the text file with
s.in.ascii sites=heights input=local.txt d=3 fs=,
Then i prepared the region with g.region. In the menu i select use the
sites file to determine the region.
Now i would like to see my points, I do
d.mon x0
d.sites heights color=white
forst you may try
s.info heights
to see how many sites were imported.
Then zoom to the region:
g.region sites=heights
d.erase
d.sites heights color=white
Markus Neteler