You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that if I create a CSV virtual sensor and use the field names "latitude" and "longitude," then on the web page the actual <addressing> values for latitude and longitude get shown next to the data values. For example, when the virtual sensor is first loaded
But after the first auto-refresh occurs it shows this
I used 0.0, 0.0 as my latitude/longitude in the <addressing> section of the virtual sensor. All of the data is recorded in the database properly, so it's just an issue in the view. Is there a simple solution for this? Thanks!
The text was updated successfully, but these errors were encountered:
kjorg50
changed the title
GSN Web UI latitude/longitude issue
Web UI latitude/longitude issue
May 28, 2015
It looks indeed like a bug in the javascript of the UI. At https://github.com/LSIR/gsn/blob/master/src/main/webapp/js/gsn.js#L945 , when getting the list of fields, there is no distinction between actual dynamic fields and predicates. The XPath could be made more selective.
As we are working on a completely new interface, we won't have much time for fixing the old one. But this seems to be an easy one.
I noticed that if I create a CSV virtual sensor and use the field names "latitude" and "longitude," then on the web page the actual
<addressing>
values for latitude and longitude get shown next to the data values. For example, when the virtual sensor is first loadedBut after the first auto-refresh occurs it shows this
I used 0.0, 0.0 as my latitude/longitude in the
<addressing>
section of the virtual sensor. All of the data is recorded in the database properly, so it's just an issue in the view. Is there a simple solution for this? Thanks!The text was updated successfully, but these errors were encountered: