G3ZIL

Stu
"The Mix of 'text' "text" and text fields is also an acquired skill obviously" ...
I think the problem is that Grafana's Query Builder does not isolate you from the syntax needs of the database being queried - in this case postgreSQL. So from what I've gathered of postgreSQL syntax:
1. Column names do not need any form of quote, except if the name of the column has even one capital letter in it. It's bad form to have capitals in postgreSQL column names, but we have SNR and tx_dBm, and so postgreSQL demands that we use double quotes around those column names, else it turns them into lower case and then can't find them.
2. Column data entries that are text fields e.g. rx_id, tx_call etc need single quotes to denote as text. In the noise table, while one may think band is numeric, I had to make it text so as to have 60eu and 80eu as options.
3. As for time - I'm still trying to figure that one out. In part because I think that if one makes a manual entry, then even if it is wrong, the pull-down remembers it.
Yes, a nice tool, but I spent many hours to get this far ...
73
Gwyn G3ZIL

To answer my own question. The status page GPS position is fixed by design, picking it up, apparently, from the position set on the admin page sdr.hu for security reasons.