[GRASS-dev] [GRASS GIS] #3823: "where" parameter incorrectly parsed in "d.vect" command on Windows
GRASS GIS
trac at osgeo.org
Mon Apr 22 23:54:21 PDT 2019
#3823: "where" parameter incorrectly parsed in "d.vect" command on Windows
-----------------------+---------------------------------
Reporter: Giacomo96 | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.6.2
Component: Display | Version: svn-releasebranch76
Keywords: d.vect | CPU: x86-64
Platform: MSWindows |
-----------------------+---------------------------------
I'm using GRASS GIS 7.6.0 on Windows 10 1809 (10.0.17763.437). I'm not
sure if the version and milestone of the ticket are correct, I will change
them if needed.
When I execute the {{{d.vect}}} command, special characters in the
{{{where}}} parameter (like the space, "<" and ">") are not correctly
interpreted, even if the query is enclosed in quotes.
An example is the following command, executed on the ''nc_spm_08_grass7''
dataset:
{{{
d.vect schools_wake where="ADDRCITY='Raleigh' and GLEVEL='E'"
}}}
The output consists in the help page of {{{d.vect}}}, followed by this
error message:
{{{
Sorry <GLEVEL='E'> is not a valid option
}}}
Nothing is shown on the monitor after the execution.
Therefore, it looks like the {{{GLEVEL='E'}}} query condition is
interpreted as another parameter of the d.vect command, when it is
actually part of the {{{where}}} parameter.
This problem happens both from the CLI (in Windows CMD) and the GUI. I've
tried every possible combination of quotes and escape characters in the
command, but none of them are working.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3823>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list