Public:Future OpenCellID database content cellid

From OpenCellID wiki
Jump to: navigation, search
This page is intended for compiling all ideas on how to improve the information stored for each cellid measurement.

Please use the "Discussion" page for discussing the various ideas and concerns on this subject.

The following table contains the list of potential additional fields of the database according to the current status of the discussion.
Please update it each time you introduce a discussion about a new database field.

Field name Data type Description Filter criteria Formula (if computed) Affected components Technology Comment
LCID string concatenation of RNC and CID
https://stackoverflow.com/questions/7240038/utran-cell-identity-returned-by-getcid
measurements_.csv / cell_towers.csv UMTS
RNC string Radio Network Controller measurements_.csv / cell_towers.csv UMTS One RNC can handle multiple LACs. RNC ID does not necessarily have a connection to LAC ID - it depends how the network is planned. For example you can find in the same RNC (12) LACs 33, 21 and 78 - no connection between them. No relative connection of RNC IDs and LAC. This is based on how to plan the network. LAC depends on paging. RNC ID is same as Site IDs. It only serves as identification.
RGPS string Real GPS position (changeable=0) cell_towers.csv all Currently, EITHER the real GPS position OR the computed GPS position is provided in cell_towers.csv depending on if the fix GPS position is available or not. The intention of this field is to provide the calculated GPS position as well as the fix GPS position in case the fix GPS position exists.
SGPS string GPS position of measurement with best signal The closer the signal is to ASU=31 or -51 dBm the better it is cell_towers.csv all
CGPS string GPS position computed from all measurements of all cells being a sector of the same base station Average of all GPS positons of all measurements of all cells being a sector of the same base station cell_towers.csv all
cell_range  ??? cell_towers.csv all
manufacturer string the manufacturer of the mobile phone (LGE, Samsung, Apple) measurements_.csv all allows to estimate market share per manufacturer
model string the model of the mobile phone (Nexus 4) measurements_.csv all allows to correct erratic data of certain models like signal strength offset per model
version string the version (firmware) from the mobile phone (4.1.2 for Android 4.1.2) measurements_.csv all
asu signalstrength as value asu  ??? measurements_.csv all At the moment there is value signal a mix between asu and value in dBm
zip_code cell_towers.csv all
city string cell_towers.csv all
street_name string cell_towers.csv all
housenumber string cell_towers.csv all
other_address_information string cell_towers.csv all
tower_height integer height of the tower/building above ground cell_towers.csv all how to enter this data?
GPS height long integer height above sea level reported by GPS measurements_.csv all WGS84 format
timestamp of measurement creation timestamp timestamp of the moment when the measurement was created measurements_.csv all allows to predict on which weekday how many people must be expected close to this tower at which time
technology string GSM/UMTS/LTE ??? measurements_.csv / cell_towers.csv all
bcch string Der Broadcast Control Channel ist ein Downlink-Kanal in GSM, der dem Endgerät Informationen über die aussendende Zelle liefert. Dies sind z. B. die PLMN-Kennung des Netzes, Cell-ID, Location Area, Kanalstruktur, Zugriffsbeschränkungen, Verfügbarkeit von Datendiensten und Frequenzen der Nachbarzellen. measurements_.csv / cell_towers.csv all
RNC, POS-RAT, RFU are present in DB but hidden. What is it? Ticket 14221 all title="Comment" -

Data filters

tbd