|
|
| (21 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | + | |
| | {|width=998 | | {|width=998 |
| − | |This page is intended to compile all ideas how to improve the information stored for each measurement / cell in the main OpenCellID database. | + | |This page including its sub pages is intended for compiling all ideas on how to expand the information stored in the OpenCellID database. |
| | + | The following data base tables are currently discussed: |
| | | | |
| − | Please use the "Discussion" page for discussing the various ideas, concerns etc.
| + | *[[Public:Future_OpenCellID_database_content_cellid|Future cell-id data structure]]<br> |
| | + | *[[Public:Future_OpenCellID_database_content_cellid_neighbours|cell-id neighbours]]<br> |
| | + | *[[Public:Future_OpenCellID_database_content_wifi|Future WiFi data structure]]<br> |
| | + | *[[Public:Future_OpenCellID_database_content_wifi_network_neighbours|wifi network neighbours]]<br> |
| | + | *[[Public:Future_OpenCellID_database_content_gps|Future GPS position data structure]]<br> |
| | | | |
| − | 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.<br>
| + | Please use the "Discussion" page of each of the above sub pages for discussing the various ideas and concerns on this subject. |
| − | In case there are different opinions regarding one or the other feature it is intended to initiate a vote similar to the votes in OpenStreetMap, which is a proven mechanism.
| + | |
| | | | |
| − | 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 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 thess topics.<br> |
| | + | 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. |
| | | | |
| − | The following table contains the list of potential additional fields of the database according to the current status of the discussion.<br>
| + | 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. |
| − | Please update it each time you introduce discussion about a new database field.
| + | |
| | |} | | |} |
| − |
| |
| − | {| class="wikitable sortable" style="font-size: 85%; text-align: left;" width=998px
| |
| − | |-
| |
| − | ! scope="col" | Field
| |
| − | ! scope="col" | Data type
| |
| − | ! scope="col" | Description
| |
| − | ! scope="col" | Filter criteria
| |
| − | ! scope="col" | Formula (if computed)
| |
| − | ! scope="col" | Affected components
| |
| − | ! scope="col" | Technology
| |
| − | ! scope="col" | Comment
| |
| − | |-
| |
| − | | title="Field" | LCID
| |
| − | | title="Data type" | string
| |
| − | | title="Description" | concatenation of RNC and CID
| |
| − | | title="Filter criteria" |
| |
| − | | title="Formula (if computed)" |
| |
| − | | title="Affected components" | measurements_.csv / cell_towers.csv
| |
| − | | title="Technology" | UMTS
| |
| − | | title="Comment" |
| |
| − | |-
| |
| − | | title="Field" | RNC
| |
| − | | title="Data type" | string
| |
| − | | title="Description" | [http://de.wikipedia.org/wiki/Radio_Network_Controller Radio Network Controller]
| |
| − | | title="Filter criteria" |
| |
| − | | title="Formula (if computed)" |
| |
| − | | title="Affected components" | measurements_.csv / cell_towers.csv
| |
| − | | title="Technology" | UMTS
| |
| − | | title="Comment" |
| |
| − | |-
| |
| − | | title="Field" | RGPS
| |
| − | | title="Data type" | string
| |
| − | | title="Description" | Real GPS position (changeable=0)
| |
| − | | title="Filter criteria" |
| |
| − | | title="Formula (if computed)" |
| |
| − | | title="Affected components" | cell_towers.csv
| |
| − | | title="Technology" | all
| |
| − | | title="Comment" | 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.
| |
| − | |-
| |
| − | | title="Field" | SGPS
| |
| − | | title="Data type" | string
| |
| − | | title="Description" | GPS position of measurement with best signal
| |
| − | | title="Filter criteria" |
| |
| − | | title="Formula (if computed)" | The cloaser the signal is to ASU=31 or -51 dBm the better it is
| |
| − | | title="Affected components" | cell_towers.csv
| |
| − | | title="Technology" | all
| |
| − | | title="Comment" | 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.
| |
| − | |}
| |
| − |
| |
| − | '''* Add the value cellid in long/short-format in measurements_.csv/cell_towers.csv'''
| |
| − |
| |
| − | '''* Add the value RNC (Radio Network Controller) in measurements_.csv/cell_towers.csv (UMTS)'''
| |
| − |
| |
| − | '''* Add latitude and longitude from the calculated real position in the cell_towers.csv (Real place from the base station)'''
| |
| − |
| |
| − | The actual position from the most cells is the middle from all measurements.
| |
| − |
| |
| − | With the value signal maybe it is possible to calculate with the best signals (ASU = 31 or -51 dBm) the best calculated real place from the base station.
| |
| − |
| |
| − | The value for the real latitude/longitude can used in example from a clf-import.
| |
| − |
| |
| − | At the moment it is a mix with the middle and clf-import with the real position.
| |
| − |
| |
| − | The real postion is useful for the apps G-Mon, G-NetTrack or RF Signal Tracker to create a cellfile or show alayer with the base stations.
| |
| − |
| |
| − |
| |
| − | Calculated middle from the cell:
| |
| − |
| |
| − | changeable=1:
| |
| − | the GPS position of the cell tower has been calculated from all available measurements
| |
| − |
| |
| − |
| |
| − | Real position from the cell:
| |
| − |
| |
| − | changeable=0:
| |
| − | the GPS position of the cell tower is precise; no measurements have been used to calculate it.
| |
| − |
| |
| − |
| |
| − | Example:
| |
| − |
| |
| − | latitude_middle, longitude_middle, latitude_real, longitude_real
| |
| − |
| |
| − |
| |
| − | '''* Add the value cellrange.'''
| |
| − |
| |
| − | With the value cellrange you can add the simple way for triangulation (see example google).
| |
| − |
| |
| − | For this you use the calculated middle.
| |
| − |
| |
| − | Lat=45.641502
| |
| − |
| |
| − | Lon=8.812474
| |
| − |
| |
| − | '''Range=1177 m'''
| |
| − |
| |
| − |
| |
| − | Example with the calculated middle and cellrange:
| |
| − |
| |
| − | http://www.open-electronics.org/celltrack/cell.php?hex=0&mcc=222&mnc=10&lac=00010012&cid=00039309&lac0=00010012&cid0=00005188&lac1=00010012&cid1=00017252&lac2=00010012&cid2=00039303&lac3=00010012&cid3=00039301&lac4=00010012&cid4=00039307
| |
| − |
| |
| − |
| |
| − | '''* Add value description for details from the cel'''l
| |
| − |
| |
| − | Example:
| |
| − |
| |
| − | - street
| |
| − |
| |
| − | - address
| |
| − |
| |
| − | - bcch
| |
| − |
| |
| − | - town
| |
| − |
| |
| − |
| |
| − | Links:
| |
| − |
| |
| − | * http://senderlistemuc.de/standorte_telekom.html
| |
| − | * http://gsm.yz.to/karte.php?x=366458&y=548039
| |
