Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web UI latitude/longitude issue #51

Closed
kjorg50 opened this issue May 28, 2015 · 3 comments
Closed

Web UI latitude/longitude issue #51

kjorg50 opened this issue May 28, 2015 · 3 comments
Labels

Comments

@kjorg50
Copy link
Contributor

kjorg50 commented May 28, 2015

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
screenshot 2015-05-27 17 13 47

But after the first auto-refresh occurs it shows this
screenshot 2015-05-27 17 14 54

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!

@kjorg50 kjorg50 changed the title GSN Web UI latitude/longitude issue Web UI latitude/longitude issue May 28, 2015
@ebiiii
Copy link
Contributor

ebiiii commented Jun 2, 2015

Hello,

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.

Thanks!

@ebiiii ebiiii added the bug label Jun 2, 2015
@kjorg50
Copy link
Contributor Author

kjorg50 commented Jun 3, 2015

Okay, looking forward to the new UI!

@ebiiii
Copy link
Contributor

ebiiii commented Jul 28, 2015

As the new UI is getting a bit late, this (d317c1d) should solve the issue.

@ebiiii ebiiii closed this as completed Jul 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants