Public:Future OpenCellID database content gps

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