Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#3306 closed defect (fixed)

Query vector maps gives error

Reported by: pvanbosgeo Owned by: grass-dev@…
Priority: normal Milestone: 7.2.1
Component: Default Version: unspecified
Keywords: Cc:
CPU: Unspecified Platform: Unspecified

Description

When using the wxGUI vector attribute query tool to get the values for a vector layer, I am getting an error (but only for polygons, querying points and lines seem to work?). For example, trying to query the geology layer in the NC dataset:

Failed to query vector map(s) <geology@PERMANENT>. Check database settings and topology.

Reason: "198808.723525"}}]}]}]}

Traceback (most recent call last):
  File "/usr/local/grass7/grass-7.3.svn/gui/wxpython/mapdisp/frame.py", line 955, in QueryMap
    distance=qdist, encoding=encoding, multiple=True)
  File "/usr/local/grass7/grass-7.3.svn/etc/python/grass/script/vector.py", line 413, in vector_what
    raise ScriptError(_("v.what output is not valid JSON format:\n {ret}").format(ret=ret))
ScriptError: v.what output is not valid JSON format:
 {"Coordinates": {"East": "634570.206825", "North": "223191.644261"},
"Maps": [
{"Map": "geology",
"Mapset": "PERMANENT",
"Features": [
{,
"Type": "Area",
"Sq_Meters": 261215323.454,
"Hectares": 26121.532,
"Acres": 64547.712,
"Sq_Miles": 100.8558,
"Categories": [
{"Layer": 1, "Category": 217,
"Driver": "sqlite",
"Database": "/home/paulo/Data/GRASSdb/nc_spm_08_grass7/PERMANENT/sqlite/sqlite.db",
"Table": "geology",
"Key_column": "cat",
"Attributes": {"cat": "217",
"onemap_pro": "261215328",
"PERIMETER": "198808.71875",
"GEOL250_": "218",
"GEOL250_ID": "217",
"GEO_NAME": "CZfg",
"SHAPE_area": "261215323.454",
"SHAPE_len": "198808.723525"}}]}]}]}

Not sure if this has anything to do with ticket #3133? Using trunk r70721

Change History (2)

comment:1 by hcho, 7 years ago

Resolution: fixed
Status: newclosed

In 70726:

v.what: Fix #3306

comment:2 by hcho, 7 years ago

This bug was introduced by r70700 (-m flag) and fixed by r70726.

Note: See TracTickets for help on using tickets.