Dear all,
I have two mapsets, one on my c:\DATA and other on my H:\HDEXT external
disk.
The first (my target database) are setted as LatLong/WGS84 projection.
The 2nd (my source database) are setted as UTM/SouthAmericaDatum1969 (zone
24).
I tryed this command to import a map from UTM to WGS:
Markus Neteler wrote:
> > but sudo doesn't work with GRASS commands).
>
> I darkly remember some discussion on this but don't recall
> the tricks (see mailing list archive).
sudo will reset the environment unless -E is used (and the "setenv"
option is enabled in the sudoers file).
Also, the lo
Felix wrote:
> Driver: GTiff/GeoTIFF
> Files: srtm_38_03.tif
> Size is 6000, 6000
> 2. Region settings:
> $g.region -p
> rows: 31200
> cols: 55200
rows, cols to not match.
try 'g.region rast=your_imported_raster_map'
Hamish
___
Milton wrote:
> > O flyed on your email and saw only warnings, not errors.
> > It appears to worked.
here:
maning wrote:
[...]
> Remove duplicates:
> Duplicates: 7
> -
> Clean boundaries at nodes:
> Modifications: 0Bus error
Hamish
Felix wrote:
> 2. Region settings:
> $g.region -p
>
> projection: 3 (Latitude-Longitude)
> nsres: 0:00:03
> ewres: 0:00:03
> rows: 31200
> cols: 55200
> cells: 172224
unless you have some very large monitor, I would suggest to
set the resolution to say 0:01 fo
Markus Neteler wrote:
Hi Felix,
On Fri, Aug 14, 2009 at 11:43 PM, Felix Schalck wrote:
...
1. DEM resolution:
$gdalinfo srtm_38_03.tif
...
Pixel Size = (0.0008333,-0.0008333)
...
2. Region settings:
$g.region -p
...
nsres: 0:00:03
ewres:
Hi Felix,
On Fri, Aug 14, 2009 at 11:43 PM, Felix Schalck wrote:
...
> 1. DEM resolution:
> $gdalinfo srtm_38_03.tif
...
> Pixel Size = (0.0008333,-0.0008333)
...
> 2. Region settings:
> $g.region -p
...
> nsres: 0:00:03
> ewres: 0:00:03
which corresponds to:
g.region -
Dear Nikos,
Many thanks for your reply. But even before listing up the requested
data, please noticed that, basically, I didn't change any settings
(g.region) when upgrading to 6.4: I just compiled and installed the
new version, and now everthing I loaded in 6.23 looks "soappy" in 6.4.
Resolution
Hi John,
On Thu, Aug 13, 2009 at 1:12 PM, John A
Stevenson wrote:
> Markus Neteler wrote:
>>
>> g.extension r.denoise
>> g.extension r.surf.volcano
>>
>> and everything should be installed.
>> If also g.extension fails, there might be a bug in the "install" part.
>>
>
> Hi Markus,
>
> I tried wi
Felix Schalck:
> Since I compiled latest 6.4RC5 Grass version, I experienced
> significative speed gain when displaying DEM raster levels - at the
> expense of the displayed resolution: the whole thing just looks
> "soappy", and keeps getting worse once you zoom in. With my previous
> version (6.23
Hello,
Since I compiled latest 6.4RC5 Grass version, I experienced
significative speed gain when displaying DEM raster levels - at the
expense of the displayed resolution: the whole thing just looks
"soappy", and keeps getting worse once you zoom in. With my previous
version (6.23), the same raste
> both reported issues are serious bugs of v.edit. Can you fill trac
> ticket for that? Just to avoid that it will forgotten. I will try to
> take a look ASAP.
I'll write a report then.
Do you (or anyone else) have an idea how else to get the lines splitted
on these points?
Achim
_
On Fri, Aug 14, 2009 at 9:39 PM, maning
sambale wrote:
> There was a vector file but not layers so in effect, there was an error.
>
> On Fri, Aug 14, 2009 at 9:21 PM, Milton Cezar
> Ribeiro wrote:
>> Hi Maning,
>>
>> O flyed on your email and saw only warnings, not errors.
>> It appears to worked.
Hi,
2009/8/14 achim :
> there is another "strange result" I don't understand. I attach a picture
> to show, what I mean.
>
> I guess it has to do with producing new start- and end-points and so a
> new line is born?
>
> Anyone an idea how to avoid this?
>
>> I try to break a couple of lines on spe
Hello,
there is another "strange result" I don't understand. I attach a picture
to show, what I mean.
I guess it has to do with producing new start- and end-points and so a
new line is born?
Anyone an idea how to avoid this?
> I try to break a couple of lines on specified points (nodes in a net
Hi Maning,
O flyed on your email and saw only warnings, not errors.
It appears to worked.
bests
milton
2009/8/14 maning sambale
> I am importing a polygon shapefile and I get this error. The
> shapefile was created using QGIS.
>
> v.in.ogr layer=forest_p116r048_repair output=forest_p116r048
>
Hi Martin
Martin Landa schrieb:
> Hi,
>
> 2009/8/12 achim :
>> does anyone know, how the operator relate is meant in v.select (grass6.5)?
>>
>> Only explanation in module description is:
>> "relate - feature A is spatially related to feature B"
>
> It checks if elements in the DE-9IM intersectio
I am importing a polygon shapefile and I get this error. The
shapefile was created using QGIS.
v.in.ogr layer=forest_p116r048_repair output=forest_p116r048
dsn=/Users/maning/pfua/map_data/forest_2002_digit/forest_p116r048_p117r047_edited
--o
WARNING: Vector map already exists and will be
18 matches
Mail list logo
