#3292: Query on spatially overlapped features in one vector map
--------------------------+-------------------------
Reporter: hcho | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.2.1
Component: Default | Version: svn-trunk
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by annakrat):
Since this can potentially break scripts which rely on the JSON output, it
should be used only when requested, so a new flag (-m as 'multiple') would
solve this. And I think it makes sense to allow user to choose if they
want one or multiple results.
Also the json output must follow the same hierarchy for points, lines and
areas. Currently areas behave differently:
{{{
{
"Coordinates": {
"East": "640122.510114",
"North": "235832.342168"
},
"Maps": [{
"Map": "bridges",
"Mapset": "PERMANENT",
"Features": [{
"Type": "Point",
"Id": 3932,
"Categories": [{
"Layer": 1,
"Category": 3932
}]
}]
}]
}
}}}
{{{
{
"Coordinates": {
"East": "640122.510114",
"North": "235832.342168"
},
"Maps": [{
"Map": "lakes",
"Mapset": "PERMANENT",
"Features": [],
"Type": "Area",
"Sq_Meters": 373.733,
"Hectares": 0.037,
"Acres": 0.092,
"Sq_Miles": 0.0001,
"Categories": [{
"Layer": 1,
"Category": 3813
}]
}]
}
}}}
From brief testing, this command creates invalid JSON:
{{{v.what -d -j map=bridges@PERMANENT coordinates=641178,235089
distance=100}}}
It would be great if you could update the v.what implementation and I
could try to implement the tree for features in the GUI query dialog.
Please upload a diff instead of the entire file.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3292#comment:2>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-dev
