Feature/1677 ngsi2 geoqueries as payload scope #1828
Conversation
| } | ||
| } | ||
| EOF | ||
| ``` |
There was a problem hiding this comment.
If remark about that "coords" needs to be provided before "geometry" should be included in the documentation in this section.
There was a problem hiding this comment.
Yes, only, coords needs to go after geometry.
I got the impression you would add this to the documentation. Perhaps I'm confusing this with something else ...
There was a problem hiding this comment.
You or me, it doesn't matter ;)
I'm suggesting you doing it as the PR is "hot under your fingers" (I'm now working in another piece of code), but as you prefer...
| EOF | ||
| ``` | ||
|
|
||
| Please note that the 'coords' field of the complex value of the scope needs to be put **after** the field 'geometry'. |
There was a problem hiding this comment.
For literal citing fields, we typically used code-style, i.e. using coords instead of 'coords' (the same for geometry).
|
LGTM (passing the ball to @crbrox for final LGTM + merge + delete branch) |
|
LGTM |
…ies_as_payload_scope Feature/1677 ngsi2 geoqueries as payload scope
Implements #1677
NGSIv2 geo-queries now also possible in V1, as part of JSON payload