Much progress!
<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Micha Silver wrote:</div>
<div class="quote-message">
Set resolution to 10m. X 10m. with
g.region -s -p res=10
</div>
</div></blockquote>
<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Hamish_b wrote:</div>
<div class="quote-message">
Multiple displays would need multiple
WIND files but the processing module (eg v.to.rast) wouldn't know which
was the appropriate one to use. Thus computational region refers to what
is stored in the mapset's WIND file.
</div>
</div></blockquote>
<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Moritz Lennert-2 wrote:</div>
<div class="quote-message">
You are aware that this means that the Contour.shp did not contain any
projection info and that GRASS thus consideres it as unprojected ?
</div>
</div></blockquote>
Setting the resolution BEFORE converting to raster was the answer, thank you. I now see the contours in the raster map as well as in the original vector file. As for the null projection, thanks for pointing it out (I was not aware!) but since the purpose of the exercise was to create an elevation profile from tabular data perhaps it is not critical.
So I went ahead with the original purpose, i.e. to create an elevation profile for the track.
<blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">Micha Silver wrote:</div>
<div class="quote-message">
r.surf.contour to create an elevation surface from the rasterized contours <br>
r.profile to get the elevations along the tracks.
</div>
</div></blockquote>
So I entered:<br>
r.surf.contour input=contours_rast@PERMANENT output=elevmap_raster --overwrite <br>
and few seconds later it completed its job without errors. Then went ahead with:<br>
r.profile -i input=elevmap_rast@PERMANENT output=- null=* <br>
I followed the track with the left mouse button and a two column list of values was printed on stdout, the distance and the elevation. Success!<br>
My only remaining question is:
Is there a way to use the track raster file to input the values instead of using the mouse, so that the process can be more or less automated?
Thank you all for your great help. I'll write a summary and post it in the Wiki as an FAQ or short tutorial as suggested by Markus Neteler.<P>
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
</quote>
<br><hr align="left" width="300">
View this message in context: <a href="http://www.nabble.com/Elevation-profile-from-intersecting-shapefiles%E2%80%8F-tp20744104p20844940.html">Re: Elevation profile from intersecting shapefiles‏</a><br>
Sent from the <a href="http://www.nabble.com/Grass---Users-f1202.html">Grass - Users mailing list archive</a> at Nabble.com.<br>