Difference between revisions of "Public:Future OpenCellID database content gps"

From OpenCellID wiki
Jump to: navigation, search
 
(7 intermediate revisions by one user not shown)
Line 12: Line 12:
 
Please update it each time you introduce a discussion about a new database field.
 
Please update it each time you introduce a discussion about a new database field.
 
|}
 
|}
 +
 +
==Measurements==
  
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;" width=998px
 
{| class="wikitable sortable" style="font-size: 85%; text-align: left;" width=998px
Line 24: Line 26:
 
! scope="col" | Comment
 
! scope="col" | Comment
 
|-
 
|-
−
| title="Field name" | LCID
+
| title="Field name" | WGS84_altitude
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | concatenation of RNC and CID<br><u>https://stackoverflow.com/questions/7240038/utran-cell-identity-returned-by-getcid</u>
+
| title="Description" | GPS altitude
−
| title="Filter criteria" |  
+
| title="Filter criteria" | <15000m
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | measurements_.csv / cell_towers.csv
+
| title="Affected components" | measurements_.csv
−
| title="Technology" | UMTS
+
| title="Technology" | all
−
| title="Comment" |  
+
| title="Comment" |
 
|-
 
|-
−
| title="Field name" | RNC
+
| title="Field name" | WGS84_altitude_accuracy
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | <u>[http://de.wikipedia.org/wiki/Radio_Network_Controller Radio Network Controller]</u>
+
| title="Description" | GPS altitude
 +
| title="Filter criteria" | >0
 +
| title="Formula (if computed)" |
 +
| title="Affected components" | measurements_.csv
 +
| title="Technology" | all
 +
| title="Comment" |
 +
|-
 +
| title="Field name" | speed
 +
| title="Data type" | integer
 +
| title="Description" | Speed of the phone / tracking device when recording the measurement
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | measurements_.csv&nbsp;/ cell_towers.csv
+
| title="Affected components" | measurements_.csv
−
| title="Technology" | UMTS
+
| title="Technology" | all
−
| title="Comment" |  
+
| title="Comment" | the field already exists in the database but the measurement unit is not clear (m/s or km/h or mph)
 
|-
 
|-
−
| title="Field name" | RGPS
+
| title="Field name" | heading
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | Real GPS position (changeable=0)
+
| title="Description" | Speed of the phone / tracking device when recording the measurement
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | cell_towers.csv
+
| title="Affected components" | measurements_.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" | 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.
+
| title="Comment" | 0= north, 90=east
 
|-
 
|-
−
| title="Field name" | SGPS
+
| title="Field name" | accuracy
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | GPS position of measurement with best signal
+
| title="Description" | GPS accuracy of the phone / tracking device when recording the measurement
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" | The closer the signal is to ASU=31 or -51 dBm the better it is
+
| title="Formula (if computed)" |  
−
| title="Affected components" | cell_towers.csv
+
| title="Affected components" | measurements_.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" |  
+
| title="Comment" | meters
 
|-
 
|-
−
| title="Field name" | CGPS
+
| title="Field name" | hdop
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | GPS position computed from all measurements of all cells being a sector of the same base station
+
| title="Description" |  
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" | Average of all GPS positons of all measurements of all cells being a sector of the same base station
+
| title="Formula (if computed)" | real hdop*10
−
| title="Affected components" | cell_towers.csv
+
| title="Affected components" | measurements_.csv
 
| title="Technology" | all
 
| title="Technology" | all
 
| title="Comment" |  
 
| title="Comment" |  
 
|-
 
|-
−
| title="Field name" | cell_range
+
| title="Field name" | vdop
−
| title="Data type" |  
+
| title="Data type" | integer
 
| title="Description" |  
 
| title="Description" |  
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" | ???
+
| title="Formula (if computed)" | real vdop*10
−
| title="Affected components" | cell_towers.csv
+
| title="Affected components" | measurements_.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" |
+
| title="Comment" |  
 
|-
 
|-
−
| title="Field name" | manufacturer
+
| title="Field name" | pdop
−
| title="Data type" | string
+
| title="Data type" | integer
−
| title="Description" | the manufacturer from the mobile phone (LGE, Samsung, Apple)
+
| title="Description" |  
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" |  
+
| title="Formula (if computed)" | real pdop*10
 
| title="Affected components" | measurements_.csv
 
| title="Affected components" | measurements_.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" |
+
| title="Comment" |  
 +
|}
 +
 
 +
==Cells==
 +
 
 +
{| class="wikitable sortable" style="font-size: 85%; text-align: left;" width=998px
 
|-
 
|-
−
| title="Field name" | model
+
! scope="col" | Field name
 +
! scope="col" | Data type
 +
! scope="col" | Description
 +
! scope="col" | Filter criteria
 +
! scope="col" | Formula (if&nbsp;computed)
 +
! scope="col" | Affected components
 +
! scope="col" | Technology
 +
! scope="col" | Comment
 +
|-
 +
| title="Field name" | RGPS
 
| title="Data type" | string
 
| title="Data type" | string
−
| title="Description" | the model from the mobile phone (Nexus 4)  
+
| title="Description" | Real GPS position (changeable=0)
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | measurements_.csv
+
| title="Affected components" | cell_towers.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" |
+
| title="Comment" | 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.
 
|-
 
|-
−
| title="Field name" | version
+
| title="Field name" | SGPS
 
| title="Data type" | string
 
| title="Data type" | string
−
| title="Description" | the version (firmware) from the mobile phone (4.1.2 for Android 4.1.2)
+
| title="Description" | GPS position of measurement with best signal
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" |  
+
| title="Formula (if computed)" | The closer the signal is to ASU=31 or -51 dBm the better it is
−
| title="Affected components" | measurements_.csv
+
| title="Affected components" | cell_towers.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" |
+
| title="Comment" |  
 
|-
 
|-
−
| title="Field name" | asu
+
| title="Field name" | CGPS
−
| title="Data type" |  
+
| title="Data type" | string
−
| title="Description" | signalstrength as value asu
+
| title="Description" | GPS position computed from all measurements of all cells being a sector of the same base station
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
−
| title="Formula (if computed)" | ???
+
| title="Formula (if computed)" | Average of all GPS positons of all measurements of all cells being a sector of the same base station
−
| title="Affected components" | measurements_.csv
+
| title="Affected components" | cell_towers.csv
 
| title="Technology" | all
 
| title="Technology" | all
−
| title="Comment" | At the moment there is value signal a mix between asu and value in dBm
+
| title="Comment" |  
 
|-
 
|-
 
| title="Field name" | zip_code
 
| title="Field name" | zip_code
Line 159: Line 184:
 
| title="Comment" |
 
| title="Comment" |
 
|-
 
|-
−
| title="Field name" | altitude
+
| title="Field name" | average_altitude
 
| title="Data type" | string
 
| title="Data type" | string
 
| title="Description" | GPS altitude  
 
| title="Description" | GPS altitude  
−
| title="Filter criteria" |
 
−
| title="Formula (if computed)" |
 
−
| title="Affected components" | measurements_.csv
 
−
| title="Technology" | all
 
−
| title="Comment" |
 
−
|-
 
−
| title="Field name" | tower_height
 
−
| title="Data type" | integer
 
−
| title="Description" | height of the tower/building above ground
 
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
 
| title="Affected components" | cell_towers.csv
 
| title="Affected components" | cell_towers.csv
−
| title="Technology" | all
 
−
| title="Comment" | how to enter this data?
 
−
|-
 
−
| title="Field name" | technology
 
−
| title="Data type" | string
 
−
| title="Description" | GSM/UMTS/LTE ???
 
−
| title="Filter criteria" |
 
−
| title="Formula (if computed)" |
 
−
| title="Affected components" | measurements_.csv / cell_towers.csv
 
 
| title="Technology" | all
 
| title="Technology" | all
 
| title="Comment" |
 
| title="Comment" |
 
|-
 
|-
−
| title="Field name" | bcch
+
| title="Field name" | average_speed
−
| title="Data type" | string
+
−
| title="Description" | 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.
+
−
| title="Filter criteria" |
+
−
| title="Formula (if computed)" |
+
−
| title="Affected components" | measurements_.csv / cell_towers.csv
+
−
| title="Technology" | all
+
−
| title="Comment" |
+
−
|-
+
−
| title="Field name" | speed
+
 
| title="Data type" | string
 
| title="Data type" | string
 
| title="Description" | Speed of the phone / tracking device when recording the measurement
 
| title="Description" | Speed of the phone / tracking device when recording the measurement
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | measurements_.csv
+
| title="Affected components" | cell_towers.csv
 
| title="Technology" | all
 
| title="Technology" | all
 
| title="Comment" | the field already exists in the database but the measurement unit is not clear (m/s or km/h or mph)
 
| title="Comment" | the field already exists in the database but the measurement unit is not clear (m/s or km/h or mph)
 
|-
 
|-
−
| title="Field name" | gps_quality
+
| title="Field name" | average_gps_quality
 
| title="Data type" | string
 
| title="Data type" | string
 
| title="Description" | GPS quality of the phone / tracking device when recording the measurement
 
| title="Description" | GPS quality of the phone / tracking device when recording the measurement
 
| title="Filter criteria" |  
 
| title="Filter criteria" |  
 
| title="Formula (if computed)" |  
 
| title="Formula (if computed)" |  
−
| title="Affected components" | measurements_.csv
+
| title="Affected components" | cell_towers.csv
 
| title="Technology" | all
 
| title="Technology" | all
 
| title="Comment" | there might be issues with the values provided by the different devices; maybe storing the device type is required
 
| title="Comment" | there might be issues with the values provided by the different devices; maybe storing the device type is required
 
|}
 
|}
 +
 +
==Data filters==
 +
tbd

Latest revision as of 00:46, 3 February 2014

This page is intended for compiling all ideas on 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 and concerns on this subject.

The plan is to keep this discussion going for a few weeks and decide what to implement when it becomes obvious that no additional new information is contributed regarding this topic.
In cases where there are different opinions regarding a feature, a vote similar to the votes in OpenStreetMap, which is a proven mechanism, will be initiated.

Due to the current work load of the developer, it is unlikely to start with the implementation of the enhanced database scheme before summer 2014; therefore, there is enough time in 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.
Please update it each time you introduce a discussion about a new database field.

Measurements

Field name Data type Description Filter criteria Formula (if computed) Affected components Technology Comment
WGS84_altitude integer GPS altitude <15000m measurements_.csv all
WGS84_altitude_accuracy integer GPS altitude >0 measurements_.csv all
speed integer 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)
heading integer Speed of the phone / tracking device when recording the measurement measurements_.csv all 0= north, 90=east
accuracy integer GPS accuracy of the phone / tracking device when recording the measurement measurements_.csv all meters
hdop integer real hdop*10 measurements_.csv all
vdop integer real vdop*10 measurements_.csv all
pdop integer real pdop*10 measurements_.csv all

Cells

Field name Data type Description Filter criteria Formula (if computed) Affected components Technology Comment
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
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
average_altitude string GPS altitude cell_towers.csv all
average_speed string Speed of the phone / tracking device when recording the measurement cell_towers.csv all the field already exists in the database but the measurement unit is not clear (m/s or km/h or mph)
average_gps_quality string GPS quality of the phone / tracking device when recording the measurement cell_towers.csv all there might be issues with the values provided by the different devices; maybe storing the device type is required

Data filters

tbd

Retrieved from "http://wiki.opencellid.org/index.php?title=Public:Future_OpenCellID_database_content_gps&oldid=1776"