I know that the Windows Vista grass users community is not so wide, anyway I
would like to know if someone is thinking about the problem I posted
sometime ago and if someone else can reproduce it.
Whenever I try to create a new Location (in my case from epsg code)
g.proj.exe crashes and returns the
Markus Metz pisze:
Maciej Sieczka wrote:
Thanks for your v.in.gshhs GRASS 6 port.
I have a problem: when importing full GSHHS extent, strange
horizontal lines through the whole longitudal extent are present in
the output GRASS vector map, which are *visible only in v.digit or
QGIS*, but never
#532: Vector editing not possible with wx tools
--+-
Reporter: geognu1 | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major| Milestone: 6.4.0
#532: Vector editing not possible with wx tools
---+
Reporter: geognu1| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Miles
Markus:
> Patch attached (maybe there is a better way to write it):
> Eigen values, (vectors), and [percent importance]:
> PC1 4712.17 (-0.2798,-0.3332,-0.5054,-0.0015,-0.5341,-0.5196) [ 84.0537% ]
just cosmetics, but please could it look like:
(G_message version)
> PC1 4712.17 ( -0.2798
Re. the missing functionality of DBF, would it be feasible
for v.db.join to import the DBF table to a temp SQLite file,
do the join and export it back to a DBF?
Would the same thing be possible for other SQL ops that DBF
does not support? For where=SQL module options?
It should be possible to ship
