On Mon, Oct 31, 2011 at 9:25 PM, Brian Oney zenli...@gmail.com wrote:
Yes, everything works great. Thanks again.
Ok, good to know. Yeah, the algorithm could be improved I guess. But, the
improvement that I would suggest is supposed to be the -l flag, right?
Yes, that was the idea of the -l
On Tue, Nov 1, 2011 at 2:46 PM, Markus Neteler nete...@osgeo.org wrote:
On Mon, Oct 31, 2011 at 9:25 PM, Brian Oney zenli...@gmail.com wrote:
Yes, everything works great. Thanks again.
Ok, good to know. Yeah, the algorithm could be improved I guess. But, the
improvement that I would suggest
One would think the -l flag would do what it is supposed to, but this
then squeezes the raster into a sliver. I get the warning...
May I ask why?:
...
if (cellhd.east 360.) cellhd.east = 180.;
...
Why not?
...
if (cellhd.east 180.) cellhd.east = 180.;
...
Also, is the 3d
Hi,
Thanks for the useful suggestions especially the M. Metz's ERROR 4 info
The double 's were due to my typing.
I still get the ERROR: 4... message when I copy the file to the working
directory.
However, when I **changed the file extension from HF2 to HFZ**, gdal_translate
successfully
On Tue, Nov 1, 2011 at 4:53 PM, Chi Kit Lau lau.chiki...@gmail.com wrote:
Dear GRASS users,
sorry for the beginner's question. How do I work out the maximum
achievable resolution when rasterizing a vector map on a scale
1:1? In other words what is the resolution of a map with a scale
I realize this might be more of a QGis question than a GRASS one, but
perhaps the same problem has affected someone here. In QGis when I click
on the Edit GRASS Vector Layer button, I no longer can see the GRASS
layer and do any editing operations to it. The Symbology pane of the
GRASS Edit
Dear Rengifo,
have you tried
' http://grass.osgeo.org/grass64/manuals/html64_user/v.to.db.html v.to.db '
with the option 'coor'?
So you would go like this:
1) Create the columns for x and y coordinates in your attribute table:
2) Upload the x and y coordinates to your attribute table:
If
Dear friends,
Some days back , I had problems with a script used to correct river network.
With help from a database expert and friend, the script worked perfectly
for me.
With thought that it may help, correct script is posted below:
elcat=4907;
echo delete from gis_schema.cat_temp;
Dear friends,
r.stream.extract and r.stream.order are not creating tables for vector
stream in postgres database.
Error is reproduced below:
Create temporary files...
Load input maps...
Initialize A* Search...
A* Search...
Extract streams...
Thin stream segments...
6214 of 18513 stream segments
