Hi,
Currently I am working on developing geofences for a project. I am using the Dashboard-Worldmap node in order to draw polygons and save them in a .json file. As it turns out though when executing a GeoIntersect query (mongoDB) with a coordinate point laying within the polygon I get an empty result. Further analysis shows me that the polygon created with the Dashboard-Worldmap node is without the start coordinate at the end, which results in a failing geointersect query.
Example of a rectangle drawing using the dashboard-worldmap node:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"Port": "test"
},
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
5.075828271373202,
52.5520956610614
],
[
5.075828271373202,
52.73619031754503
],
[
5.562168359767676,
52.73619031754503
],
[
5.562168359767676,
52.5520956610614
]
]
]
}
}
]
}
Example of a rectangle drawing for example in geojson.io:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"Port": "Test"
},
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
5.211982727050781,
52.605132598485969
],
[
5.4087066650390629,
52.605132598485969
],
[
5.4087066650390629,
52.72652036177586
],
[
5.211982727050781,
52.72652036177586
],
[
5.211982727050781,
52.605132598485969
]
]
]
}
}
]
}
Where the geojson.io adds the start point also as an end point, the worldmap-dashboard node does not. Is this normal functionality or is this a possible fix opportunity?
Node-red-dashboard version 3.1.7
Node-red-contrib-web-worldmap version 2.21.9