I understand that from the command v.to.rast. what I asked is do you have
problem deleting raster map "created" from v.to.rast or other raster maps.
If you have problem deleting any raster map(create a duplicate and dont try
with your actual data) then it this is an issue with g.remove.
I want to
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
No, I am just creating new raster from point vector map..
v.to.rast --overwrite input=Temp_Aug_86@PERMANENT type=point
output=Rast_Temp_Aug_86 column=Rain14
here Temp_Aug_86 is point vector
but the problem is solve when we use command like-
v.to.rast --overwrite input=Temp_Aug_86@PERMANENT
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
On Sun, Mar 10, 2013 at 9:49 PM, Helmut Kudrnovsky wrote:
...
> if we know that installing vcredist_2010_x86.exe would be enough, it should
> be doable by the nsis-wingrass-installer...
We could try... then decide. If it is not too much mess?
BTW:
http://www.microsoft.com/en-us/download/details.
On Sun, Mar 10, 2013 at 12:04 PM, Hamish wrote:
> Comment(by martinl):
>> The result will the same. Please bear in mind, that you are
>> probably only one from devs who really wants to keep `develbranch_6` alive.
>
> I'm not into making threats or big ego shows so I'll just say the way it is.
>
>Just guessing around: what if we "wget" dump all these msvcpXYZ.dll
>files into the lib/ directory? If it comes first in the DLL path, it may
>not conflict with any system DLLs?
good point.
AFAIK the msvcrt runtimes are delivered as exe/msi by ms and should be
installed,
e.g. see http://www.mic
On Sun, Mar 10, 2013 at 4:06 PM, Helmut Kudrnovsky wrote:
...
> it seems not to be really obvious from the different reports which version
> of the ms runtimes is needed?
...
> in the last weeks there were reports about missing msvcp100.dll...
Just guessing around: what if we "wget" dump all thes
#1803: GRASS 6.4.3RC1 on Win 7: grass64.bat fails due to UNIX line endings in
Init.bat
--+-
Reporter: msieczka | Owner: grass-dev@…
Type: defect| Status: n
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
> The situation is untenable as-is, but pretty easy to fix with an extra page
+ [yes/no] + wget as a
> near-last page the nsi installer I think.
it seems not to be really obvious from the different reports which version
of the ms runtimes is needed?
see http://trac.osgeo.org/grass/ticket/1428#c
#1270: wingrass: Error in Attribute Table Manager
---+
Reporter: antonioall | Owner: grass-dev@…
Type: defect | Status: new
Hi devs!
Besides _editing_ the PERMANENT/MYNAME file manually (later, not while creating
a Location), is there a "proper" way to do so? It is used for example by the
"header" instruction in ps.map. I can't trace a single reference about it in
any of the user-manuals except for in ps.map's sec
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
#1803: GRASS 6.4.3RC1 on Win 7: grass64.bat fails due to UNIX line endings in
Init.bat
--+-
Reporter: msieczka | Owner: grass-dev@…
Type: defect| Status: n
Martin wrote:
> If nobody will fix it, we can release GRASS without binaries for
> Windows ;-)
If nobody fixes it, we will have to release GRASS without binaries for Windows
:-/
best,
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http:/
Hi,
2013/3/10 Hamish :
[...]
> Certainly binary release is out of the question until the license violation
> in the wingrass packages is resolved. The situation is untenable as-is, but
> pretty easy to fix with an extra page + [yes/no] + wget as a near-last page
> the nsi installer I think.
Martin wrote:
> good point, more over there were open four blockers in one
> day by one person just when we claimed to release RC3 and then
> final. We should really change policy in this sense.
> Ideally should come two RC in shorter period (two or three
> weeks) and then final.
> Currently we hav
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
[Subject: Re: [GRASS-dev] [GRASS GIS] #1889: wxPy loc'n wiz: don't auto-launch
into PERMANENT]
> Comment(by martinl):
> just small note: it's probably related to the fact, that
> you are probably only developer who wants to do "development"
> in GRASS 6 branches.
I don't mean new development, I
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
Does this error comes in deleting other maps. Could you try g.copy
rast=old,new
and delete the newly created raster map.
Btw, Please tell your grass version and platform
On Sun, Mar 10, 2013 at 1:41 PM, SWAPAN GHOSH wrote:
> *Dear all,*
>
> I am using the command like-
>
> v.to.rast --overwrit
#1889: wxPy loc'n wiz: don't auto-launch into PERMANENT
-+--
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker
*Dear all,*
I am using the command like-
v.to.rast --overwrite input=Temp_Aug_86@PERMANENT type=point
output=Rast_Temp_Aug_86 column=Rain14
Rast_Temp_Aug_86@PERMANENT is created successfully.
But when I want to delete this raster using command like-
g.remove rast=Rast_Temp_Aug_86@PERMANENT
Th
28 matches
Mail list logo