Difference between revisions of "Public:Future OpenCellID database content"
Line 77: | Line 77: | ||
| title="Technology" | all | | title="Technology" | all | ||
| title="Comment" | | | title="Comment" | | ||
+ | |- | ||
+ | | title="Field name" | asu | ||
+ | | title="Data type" | | ||
+ | | title="Description" | signalstrength as value asu | ||
+ | | title="Filter criteria" | | ||
+ | | title="Formula (if computed)" | ??? | ||
+ | | title="Affected components" | measurements_.csv | ||
+ | | title="Technology" | all | ||
+ | | title="Comment" | At the moment there is value signal a mix between asu and value in dBm | ||
|- | |- | ||
| title="Field name" | zip_code | | title="Field name" | zip_code |
Revision as of 00:49, 29 January 2014
This page is intended to compile all ideas how to improve the information stored for each measurement / cell in the main OpenCellID database.
Please use the "Discussion" page for discussing the various ideas, concerns etc. It is planned to keep this discussion going for a few weeks and when it becomes obvious that no additional, new information is contributed regarding this topic then it will be decided what to implement. Due to the current work load of the developer it is unlikely to start with the implementation of the enhanced database sceme before summer 2014, so there is enough time from that perspective to discuss the OpenCellID database evolution briefly. The following table contains the list of potential additional fields of the database according to the current status of the discussion. |
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 | |||
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 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 | ||||
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 | ||||
altitude | string | GPS altitude | measurements_.csv | all | |||
tower_height | integer | height of the tower/building above ground | cell_towers.csv | all | how to enter this data? | ||
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 | |||
speed | string | Speed of the phone / tracking device when recording the measurement | measurements_.csv | all | the field already exists in the database but the measurement unit is not clear (m/s or km/h or mph) | ||
gps_quality | string | GPS quality of the phone / tracking device when recording the measurement | measurements_.csv | all | there might be issues with the values provided by the different devices; maybe storing the device type is required |