Proposal:Communications Transponder
| Communications Transponder | |
|---|---|
| Proposal status: | Inactive (inactive) |
| Proposed by: | mungewell |
| Tagging: | man_made=communications_transponder |
| Statistics: |
|
| RFC start: | 2009-07-13 |
There may be one or more transponders on a communications tower. Single transponders may be represented by adding the Communication_Transponder tags directly the tower's node.
For multiple transponders, each transponder should be added to a group relation. The 'communication_tower_group' relation shall contain the nodes representing the communication_tower and any/all communication_transponders.
Note: This will have the side effect of placing multiple nodes at the same position.
General Tags
Some general tags which are used across many other types of object are used to tag communication_transponder:
| Key | Value | Element | Comment | Example | Icon |
|---|---|---|---|---|---|
| name | * |  |
Name of the transponder | Nose Hill Park | |
| ref | * | |
Callsign of the transponder | VE6RYC | |
| operator | * | |
Maintainer/Operator of the transponder | Calgary Amateur Radio Association | |
| height | * | |
Height of the transponder's antenna from ground in meters, at the tower location | ||
| ele | * | |
Elevation of transponder's antenna above sea-level in meters | ||
| source | * | |
Where did the data come from? | nwham.com | |
| url | * | |
Website with information about this transponder. | http://www.caraham.org/ |
BTS (GSM\CDMA tower) Tags
Tags which aren't shared with other OSM features are prefixed with the "communications_transponder:" namespace.
| Key | Value | Element | Comment | Example | Icon |
|---|---|---|---|---|---|
| ref:mcc | * | |
Mobile Country Code | 247 | |
| ref:mnc | * | |
Mobile Network Code | 02 | |
| ref:lac | * | |
Location Area Code | 115 | |
| ref:cid | * | |
Cell ID | 10007 | |
| ref:act | * | |
Network access type (2G=GSM; 2G+=EDGE; 3G=UMTS \ CDMA; 3G+=HSDPA, HSPA, HSUPA \ EDV0_0, EDV0_A; 4G=LTE) | HSPA |
Specific Tags
Tags which aren't shared with other OSM features are prefixed with the "communications_transponder:" namespace.
| Key | Value | Element | Comment | Example | Icon |
|---|---|---|---|---|---|
| communications_transponder:frequency | * | |
The frequency of operations for the transponder, in MHz. May denote a frequency range with '..'. May include offset indication for duplex communications. | 146.8500-0.6 | |
| communications_transponder:polarisation | * | |
The polarisation of operations for the transponder. | vertical, horizontal or circular | |
| communications_transponder:power | * | |
The output power for the transponder, in W. | 150 | |
| communications_transponder:access | * | |
Whether the use of this transponder is public, private, etc | Public | |
| communications_transponder:service | * | |
Generalisation of the 'service' provided by this transponder (TV, RADIO, GSM800, GSM1800, UMTS, C2000, Amateur) | Amateur |
Technical Tags
These are included to suggest a scheme, but not recommended for placing into the main OSM database.
| Key | Value | Element | Comment | Example | Icon |
|---|---|---|---|---|---|
| communications_transponder:modulation | * | |
The modulation scheme for the transmission, (AM, FM, PAL, NTSC, COFDM, NFM, SSB, etc) | NFM | |
| communications_transponder:bearing | * | |
For a direction antenna the bearing on which it is pointed. (degrees from north) | 65 | |
| communications_transponder:tone | * | |
Whether a CTCSS (or the like) tone is required access/enable transponder | 110.9 | |
| communications_transponder:antenna_type | * | |
Description of antenna element | Dipole |
Possible Sources of Geodata
- http://www.openbmap.org/ - A free and open map of wireless communicating objects
- http://nwham.com/ - Amateur Radio Repeater Listing (permission granted to import)
- http://www.opencellid.org/ - Cell Tower Locations and transponder IDs (CC-SA 3.0 license)
- http://www.ic.gc.ca/eic/site/tafl-ltaf.nsf/eng/home Industry Canada - 'Frequency Assignment' data files.
- (US) FCC Antenna Structure Registration