DB Viewer UX and layout issues
Created by: E3V3A
For the DB Viewer
to be of any informative value, it should better reflect the important contents of the DB tables. Especially important to us is the key info in the DBi_bts
and DBe_import
tables.
I propose the following improvements:
-
1. In DB Viewer
, usethe same two-color text-coloring-scheme as in theMap Viewer
pin-info. -
2. In DB Viewer
, try to left-align all the text columns. -
3. In DB Viewer
, use 2 columns to fit additional data for measurements and OCID data.
Specifically, for the BTS Measurements
and in map view details, we'd like something like this:
----------------------------------------------------
CID(hex): HHHHH Sector: nn
----------------------------------------------------
PC: NNN-NN Lat: 51.9898
LAC: nnnnn Lon: 176.58705
CID: nnnnn? first: 2014-12-01 21:00:00
PSC: nnn last: 2014-12-19 21:00:01
RAT: HDSP XXX:
RSS: -NN samples: 3
----------------------------------------------------
H : variable length HEX [0-9a-z] (depending on RAT)
n : variable length integer (depending on RAT)
N : Fixed length integer
RSS = AvgSignal for OCID data, and RSSI for measured data. XXX = isGPS_exact for OCID data and for measured data:
LTE: *TA*
UMTS: -
GSM: /
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.