QDP2012/30/1/1
From The RadioReference Wiki
< User:QDP2012 | 30 | 1
Home | Prompts | Move | TRVA | Cat Tree | Links | CECC | Pgmg | Templates |
Tasks: Art, Cat, Tmp, DB 10, 13, 27, 29, 30/1 32, 43, 44, 193,194 | Conv&Stds Sandbox Edit PrfxIdx | ..WRRR ..USBR 1 ..USBR 76 ..PHT | Cat List Custom Avoid Unused 35, 36, 37, 38, CT (C E S N) SC | Categories to be DELETED Templates to be DELETED Pages to be DELETED TL (G IB C S D) | B, C, D, F, I Tk, Tb, Ct, Tx. M, S, TO Avoid Unused | |||
.
Contents
- 1 Documentation Sub-page for Template:Cat_StateFreq
- 1.1 Scope of Use
- 1.2 Parameters
- 1.3 Examples
- 2 Documentation Sub-page for Template:Collaboration
- 3 Documentation Sub-page for Template:Color
- 4 Documentation Sub-page for Template:DBSiteMap FCC
- 5 Documentation Sub-page for Template:Infobox TRS
- 6 Documentation Sub-page for Template:Infobox TRS Canada
- 7 Documentation Sub-page for Template:Infobox TRS DC
- 8 Documentation Sub-page for Template:Infobox TRS Federal
- 9 Documentation Sub-page for Template:Infobox TRS Military
- 10 Documentation Sub-page for Template:Infobox TRS MultiCounty
- 11 Documentation Sub-page for Template:Infobox TRS MultiState
- 12 Documentation Sub-page for Template:Refreshpage
- 13 Documentation Sub-page for Template:Table_ELTRfreqs
- 14 Documentation Sub-page for Template:Table_Motofreqs
- 15 Documentation Sub-page for Template:Table_Trbosys
- 16 Documentation Sub-page for Template:Text Airshow
- 17 Documentation Sub-page for Template:Text_CatGeneral
- 17.1 Scope of Use
- 17.2 Parameters
- 17.3 Examples
- 18 Documentation Sub-page for Template:Text Deprecated
- 19 Documentation Sub-page for Template:Text MTairshow
- 20 Documentation Sub-page for Template:Tracker_DMR
- 21 Documentation Sub-page for Template:Tracker_LTR
- 22 Documentation Sub-page for Template:Tracker_MPT-1327
- 23 Documentation Sub-page for Template:Tracker_NXDN
- 24 Documentation Sub-page for Template:Tracker_OpenSky
- 25 Documentation Sub-page for Template:Tracker_Phase2
- 26 Documentation Sub-page for Template:Tracker_Provoice
Documentation Sub-page for Template:Cat_StateFreq
Scope of Use
Purpose
- Template:Cat_StateFreq should be used to build frequency-related category-pages for individual Countries, US States, Territories, etc. and Canadian Provinces.
- Template:Cat_StateFreq is designed to be a category-template that provides a common and uniform structure for both the text that is displayed on, and the categories assigned to, specific frequency-related "state"-level categories.
Directly Invoked By
- Template:Cat_StateFreq should be directly invoked only by "state"-level frequency-related category-pages.
Not Intended For
- Template:Cat_StateFreq should not be directly invoked by any other template or category, including state-specific frequency-related sub-categories below a primary "state"-level frequency-related category; nor by the top frequencies-related category within a particular theme (e.g. not invoked by "Category:Medical Frequencies").
Parameters
- Specified values will override default values.
- Specified values and Default values are all case-sensitive.
Parameter Name | Var Description | Expected Value(s) | Default Value | Notes |
---|---|---|---|---|
State | A value is Required | |||
FreqParent | name of the parent "...Frequencies" category (omit the word "Frequencies") |
Wiki | The word "Frequencies" is already present in the template and should not be included in the FreqParent value. | |
MoreText | (no value) | This parameter allows for an optional custom message in the page's mid-section. When no value is specified, the parameter name is hidden. |
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template for a US State
- {{Cat_StateFreq|State=Utah}}
Result
Welcome to the "Category:Utah Frequencies" category. This category:
- Is a sub-category of:
- Lists all the articles for Category:Utah that contain Wiki Frequencies information as submitted by the members.
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
To CATEGORIZE an article into this category, please add the following as the last line in the article:
[[Category:Utah Frequencies]]
Please do NOT edit this page unless you intend to change the Description of this Category. Thank you.
How to invoke this template for a Canadian Province
- {{Cat_StateFreq|State=Ontario}}
Result
Welcome to the "Category:Ontario Frequencies" category. This category:
- Is a sub-category of:
- Lists all the articles for Category:Ontario that contain Wiki Frequencies information as submitted by the members.
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
To CATEGORIZE an article into this category, please add the following as the last line in the article:
[[Category:Ontario Frequencies]]
Please do NOT edit this page unless you intend to change the Description of this Category. Thank you.
How to invoke this template for another Country with Custom Message
- {{Cat_StateFreq|State=My Country|MoreText=<br/><br/>....This example uses bogus names....<br/><br/>}}
Result
Welcome to the "Category:My Country Frequencies" category. This category:
- Is a sub-category of:
- Lists all the articles for Category:My Country that contain Wiki Frequencies information as submitted by the members.
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
....This example uses bogus names....
To CATEGORIZE an article into this category, please add the following as the last line in the article:
[[Category:My Country Frequencies]]
Please do NOT edit this page unless you intend to change the Description of this Category. Thank you.
How to invoke this template for a State in another Country with Custom Message
- {{Cat_StateFreq|State=My State|FreqParent=My Country|MoreText=<br/><br/>....This example uses bogus names....<br/><br/>}}
Result
Welcome to the "Category:My State Frequencies" category. This category:
- Is a sub-category of:
- Lists all the articles for Category:My State that contain My Country Frequencies information as submitted by the members.
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
....This example uses bogus names....
To CATEGORIZE an article into this category, please add the following as the last line in the article:
[[Category:My State Frequencies]]
Please do NOT edit this page unless you intend to change the Description of this Category. Thank you.
Return to: Template:Cat_StateFreq
Documentation Sub-page for Template:Collaboration
Scope of Use
Purpose
- This template was originally intended to present a standardized header for only the US State pages in the collaboration area. However, others have also used it to provide this header on US County pages.
- There are similar templates already coded for Canada and Australia. Please return to the Templates-List: General Use Only page to view these
Directly Invoked By
- All US State pages in the collaboration area, as well as some US county pages
- The Color template is invoked to make certain text in the table white.
Parameters
- There are 3 paramters to this template, all of which can be found on the respective database state page
- Statename - The full name of the state
- StateDB - The URL in the database for this state
- Stateforum - The URL of the state's forum area
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
{{Collaboration |Statename=Ohio |StateDB=[http://www.radioreference.com/apps/db/?stid=39 {{color|white|Ohio DB]}} |Stateforum=[http://www.radioreference.com/forums/ohio-radio-discussion-forum/ {{color|white|Ohio Forum}}] }}
Result
- See the Ohio (US) article for an example of this template called at a state level
- See the Grayson County (VA) for an example of this template called at a county level
Return to: Template:Collaboration
Documentation Sub-page for Template:Color
Scope of Use
Purpose
- This template should be used to change the text color for some specific purpose. One way to use this is to mimic the red/green color scheme used in the database to indicate primary and alternate control channels of a trunk system.
Directly Invoked By
- Any article that requires colored text. The reason should be mentioned in the article, unless it is mimicing the database usage
Parameters
- There are 2 tokens that are required to execute this template
- 1 - Put the desired color here. Red, green, blue are most common, but others are possible. Black is the default text color, and should not be used with this template
- 2 - The text that will be presented
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
{{color|red|477.8875}} {{color|green|477.8875}}
Result
- 477.8875
- 477.8875
Return to: Template:Color
Documentation Sub-page for Template:DBSiteMap FCC
Scope of Use
Purpose
- This template is to be used when a single TRS has many sites, each with their own callsign
- It invokes a function in the database that calls FCC data which is periodically loaded into the database
- The result creates a map with locations marked with red pinheads. Clicking on the pinhead will reveal the FCC callsign as well as other data
- This template should NOT be used when working on a Multi County or Multi State TRS. A version of this template has already been installed for this purpose
Directly Invoked By
- Any TRS within a county / state that has sites that has multiple callsigns. See the warning above.
Parameters
- Sidnum - The SID can be found as the last token in the URL for the particular TRS being documented.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be used as a model.
{{DBSiteMap_FCC|Sidnum=768}}
Result
Click on the link (in blue) to see the resulting map
- See the RRDB FCC Site Map for additional sites and callsigns.
Return to: Template:DBSiteMap FCC
Documentation Sub-page for Template:Infobox TRS
Scope of Use
Purpose
- This template presents a standardized index with information describing a particular TRS. It includes the FCC callsign as well as links to the database and, where needed, maps showing site locations
- This template should only be used for a TRS that is regional in nature, and does not cover multiple areas. In addition, these types and states have their own Infobox. Please return to the Templates-List: General Use Only page for coding examples;
- TRS that cover multiple counties
- TRS that covers multiple states
- Military TRS
- Federal TRS
- Canadian TRS (Alberta has one specific to them)
- TRSs in the following states / regions;
- District of Columbia
- Minnesota
- Wisconsin
- Iowa
- Illinois
- Michigan
- Ohio
- Oklahoma
Directly Invoked By
- TRSs that cover a single area, county or region
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- SysType - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- WACN - The Wide Area Communications ID, if known. Blanks are acceptable if it's not
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Ccode - If this TRS is a MOTOTRBO type, and the DMR color code is known, place it here. See the notes below for further information. Blanks are acceptable if not known
- RAN - If this TRS is a NXDN type, and the RAN is known, place it here. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- Owner - Who owns this TRS? If not known, it can be left blank. You can also use Public or Private to describe its ownership type
- FCC - The FCC license of this TRS. This can be found using the FCC Callsigns link that can be found in the database immediately above the frequencies grid. See the notes below
- Use the FCC parameter for the first callsign only, and do not use the Template:Callsign for the FCC value. The FCC value is used to build the FCC link in the lower portion of the InfoBox.
- MoreCallsigns - after assigning the first callsign to the FCC parameter, please use the MoreCallsigns parameter to display additional callsigns related to the TRS; Template:Callsign can be used to link each of the additional callsigns to the database. A <br/> html-command should be placed before each callsign to list it on a separate row.
- City - Self Explanatory. If there are multiple cities used as sites, Various can be placed here. See the notes below
- County - The wiki link for the county (if known), with a substitution for the more English looking name for readability. See the example below
- State - The name of the state, first letter capitalized
- StateB - Same as State
- state - The name of the state forum where this TRS can be discussed. Note that some names are hyphenated (as shown in the example below) and is NOT capitalized
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
- Some TRS have multiple callsigns, one for each site. You can use the parameter "MoreCallsigns" and the Callsign template to document them, or better, use the DBsitemap FCC template to use the FCC driven map function to graphically display each site on a map
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS |SysName = New York City Transit Authority |SysType = [[Motorola Type II Smartnet]] |SysID = 0E0A |CTone = 90.00 |NAC = |CCode = |Band = 800 |Owner = City of NY |FCC = KNEH690 |City = NY |County = [[New York (NY)|New York]] |State = New York |StateB = New York |state = new-york |sid = 128 }}
Result
See the Denver Public Safety for an example, which also shows the use of a template to warn about an unmonitorable system
Return to: Template:Infobox TRS
Documentation Sub-page for Template:Infobox TRS Canada
Scope of Use
Purpose
- This template presents a standardized page for Canadian Trunked Radio Systems (TRS).
- Data from Industry Canada - the Canadian equivalent of the FCC - is not downloaded to our database. Therefore do not use the callsign templates or anything that would invoke the FCC mapping functions
Directly Invoked By
- Canadian TRSs
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- SysType - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- WACN - The Wide Area Communications ID, if known. Blanks are acceptable if it's not
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Ccode - If this TRS is a MOTOTRBO type, and the DMR color code is known, place it here. See the notes below for further information. Blanks are acceptable if not known
- RAN - If this TRS is a NXDN type, and the RAN is known, place it here. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- Owner - Who owns this TRS? If not known, it can be left blank. You can also use Public or Private to describe its ownership type
- City - Self Explanatory. If there are multiple cities used as sites, Various can be placed here.
- County - The wiki link for the county (if known), with a substitution for the more English looking name for readability. Various can be used here if the TRS has sites in multiple counties.
- Province - The province where the TRS resides, written with a wiki link along with a more English description. See the example below.
- ForumTitle - The title of the forum that covers this province, as found in the Forums on this website
- ForumPath - The forum's province name which can be found in the URL. It can be hyphenated, and is always written in lower case.
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS_Canada |SysName = Bell FleetNet - Ontario Provincial Government Zone 1 |SysType = [[Motorola Type II]] and [[APCO Project 25]] |SysID = 782D |CTone = 105.88 |WACN = ? |NAC = ? |CCode = ? |Band = VHF |Owner = Bell Fleetnet |City = Various |County = Various |Province = [[Ontario (CA)|Ontario]] |ForumTitle = Ontario |ForumPath = ontario |sid = 861 }}
Result
See the Bell FleetNet - Ontario Provincial Government Zone 1 article
Return to: Template:Infobox TRS Canada
Documentation Sub-page for Template:Infobox TRS DC
Scope of Use
Purpose
- This template presents a standardized index with information describing Trunked Radio Systems (TRS) in the District of Columbia only
- This template should NOT be used for describing Military or Federal TRSs. There are other templates defined for this purpose. See the Templates-List: General Use Only page
- Note that because DC is not a city, state or county, these entries have been hard-coded into the template and should not be changed.
Directly Invoked By
- TRSs in the District of Columbia that are not Federal or Military
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- SysType - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Ccode - If this TRS is a MOTOTRBO type, and the DMR color code is known, place it here. See the notes below for further information. Blanks are acceptable if not known
- RAN - If this TRS is a NXDN type, and the RAN is known, place it here. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- Owner - Who owns this TRS? If not known, it can be left blank. You can also use Public or Private to describe its ownership type
- FCC - The FCC license of this TRS. This can be found using the FCC Callsigns link that can be found in the database immediately above the frequencies grid. See the notes below
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
- Some TRS have multiple callsigns, one for each site. You can use the Callsign template to document them, or better, use the DBsitemap FCC template to use the FCC driven map function to graphically display each site on a map
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The lines below (between the pre tags) can be used as a model.
{{Infobox TRS DC |SysName = Verizon Center |SysType = [[MOTOTRBO|DMR Motorola Capacity Plus (TRBO)]] |SysID = N/A |CTone = N/A |NAC = N/A |CCode = See DMR Bandplan |Band = UHF |Owner = Private |FCC = WQTI477 |sid = 7845 }}
Result
See the Verizon Center article for an example
Return to: Template:Infobox TRS DC
Documentation Sub-page for Template:Infobox TRS Federal
Scope of Use
Purpose
- This template presents a standardized index that describes a US Federal Trunked Radio System (TRS)
- As with the military, the FCC does not keep callsign or location data. It is instead kept by the NTIA and is not available to the public. You should not code any templates that invoke callsigns or location mapping.
- There is a dedicated Federal forum to discuss these TRSs
Directly Invoked By
- TRSs that are run or administered by the US Federal Government.
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- SysType - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- Agency - The US Federal Branch that administers or uses this system
- City - Self Explanatory. If there are multiple cities used as sites, Various can be placed here. See the notes below
- County - The wiki link for the county (if known), with a substitution for the more English looking name for readability. See the example below
- State - The name of the state, first letter capitalized
- StateB - Same as State
- state - The name of the state where this TRS resides. You can say Various if it is a multi state system. Note that some names are hyphenated and is NOT capitalized
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS_Federal |SysName = Federal Detention Center Houston |SysType = [[Motorola Type II]] |SysID = E726 |CTone = 116.13 |NAC = 265 |Band = Federal UHF |Agency = U.S. Bureau of Prisons |City = Houston |County = [[Harris County (TX)|Harris]] |State = [[Texas (US)|Texas]] |StateB = Texas |state = texas |sid = 2791 }}
Result
See the Federal Detention Center Houston article for an example
Return to: Template:Infobox TRS Federal
Documentation Sub-page for Template:Infobox TRS Military
Scope of Use
Purpose
- This template presents a standardized index that describes a military Trunked Radio System (TRS).
- You should not use any template to invoke looking up callsigns or mapping data for these TRSs. They are not found on the FCC database, but are kept by the NTIA and is not available to the public
- As there is a dedicated Military forum, the link for it is hard coded into the template
Directly Invoked By
- Military directed or administered TRSs
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- SysType - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- Agency - The military branch(es) that utilize and administer this system
- City - Self Explanatory. If there are multiple cities used as sites, Various can be placed here. See the notes below
- County - The wiki link for the county (if known), with a substitution for the more English looking name for readability. See the example below
- State - The name of the state, first letter is capitalized
- StateB - Same as State, but the first letter is capitalized
- state - The name of the state where this TRS resides. You can code Various if it is a multi state system. Note that the first letter of the name is capitalized. Some state names are also hyphenated.
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS_Military |SysName = Fort Hood |SysType = [[Project 25]] Phase I |SysID = 28A86-046 |CTone = N/A |NAC = 047, 048, 049, 04A |Band = 380 |Agency = U.S. Army |City = Killeen |County = [[Bell County (TX)|Bell]] & [[Coryell County (TX)|Coryell]] |State = [[Texas (US)|Texas]] |StateB = Texas |state = texas |sid = 5738 }}
Result
See the Fort Hood article for an example
Return to: Template:Infobox TRS Military
Documentation Sub-page for Template:Infobox TRS MultiCounty
Scope of Use
Purpose
- This template presents a standardized index with information describing a TRS that covers multiple counties.
Directly Invoked By
- TRSs that cover multiple counties
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- Flavor - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- WACN - The Wide Area Communications ID, if known. Blanks are acceptable if it's not.
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Ccode - If this TRS is a MOTOTRBO type, and the DMR color code is known, place it here. See the notes below for further information. Blanks are acceptable if not known
- RAN - If this TRS is a NXDN type, and the RAN is known, place it here. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- OwnerTy - Who owns this TRS? If not known, it can be left blank. You can also use Public or Private to describe its ownership type
- City - Self Explanatory. Various can be placed here. See the notes below
- County - If possible, when there's only 1 or 2, insert them here. If there are more than that, put Various
- State - The name of the state, first letter capitalized
- fstate - The name of the state forum where this TRS can be discussed. Note that some names are hyphenated (as shown in the example below) and is NOT capitalized
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
- This template has a built in function to call the database function to map individual sites using the FCC data. Using other templates (such as Callsign) are not needed.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS_MultiCounty |SysName=Louisiana Wireless Information Network (LWIN) |Flavor=[[Project 25]] Phase I |SysID=BEE00-1BD |CTone=? |NAC=? |Band=700 / 800 |County=Various |State=Louisiana |fstate=louisiana |OwnerTy=Public |sid=4347}}
Result
See the Louisiana Wireless Information Network (LWIN) article for an example
Return to: Template:Infobox TRS MultiCounty
Documentation Sub-page for Template:Infobox TRS MultiState
Scope of Use
Purpose
- This template presents a standardized index with information describing a TRS that covers multiple states.
Directly Invoked By
- TRSs that cover multiple states
Parameters
- Many of these parameters may be filled in with data from the database or other wiki pages, as shown.
- SysName - The name of the TRS being documented
- Flavor - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
- SysID - The system ID of the TRS, if known. Blanks are acceptable if not known
- CTone - The connect tone needed for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- NAC - If this is a Project 25 system, the Network Access Code (NAC) for an actual user to access this system. It's not needed for scanners. Blanks are acceptable if not known
- Ccode - If this TRS is a MOTOTRBO type, and the DMR color code is known, place it here. See the notes below for further information. Blanks are acceptable if not known
- RAN - If this TRS is a NXDN type, and the RAN is known, place it here. Blanks are acceptable if not known
- Band - Generic description of the band this TRS uses; examples like 'VHF', 'UHF', '700 Mhz' are fine. If there is more than one band, seperate them with a '/'
- State - Place the standard abbreviation, with the wiki link, here. If there are too many, code Various
- OwnerTy - Who owns this TRS? If not known, it can be left blank. You can also use Public or Private to describe its ownership type
- sid - The SID can be found as a token in the last part of the URL for this TRS in the database.
- Notes
- Not all of these tokens are required, but every effort should be made to fill them in. Many can be left blank, and it will not cause the template to fail
- These items should be installed, when needed, in a new section to be called 'Related Links' or 'Related Pages'. Templates mentioned here can all be found on the Templates-List: General Use Only page
- If the TRS is of a type that can't be trunked or scanned, a warning to that effect is required. Use the Tracker-Related templates
- If the TRS is a MOTOTRBO type, and uses multiple color codes, put See DMR Bandplan in the DMR Color Code field. You must then supply a link to an article with the corrected bandplan that shows each color code by frequency (when known). The Table Trbosys template is designed for this purpose.
- This template has a built in function to call the database function to map individual sites using the FCC data. Using other templates (such as Callsign) are not needed.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Infobox_TRS_MultiState |SysName = Basin Electric Power Cooperative |Flavor = [[MPT-1327]] Standard |SysID = N/A |CTone = N/A |NAC = N/A |Band = UHF |State = [[Colorado (US)|CO]], [[Iowa (US)|IA]], [[Minnesota (US)|MN]], [[North Dakota (US)|ND]] |OwnerTy = Public |sid = 5271 }}
Result
See the Basin Electric Power Cooperative article
Return to: Template:Infobox TRS MultiState
Documentation Sub-page for Template:Refreshpage
Scope of Use
Purpose
- This template is required whenever the RR Wiki Extensions are invoked. It forces the wiki to flush its internal cache and refresh any data pulled from the database
Directly Invoked By
- Any page that invokes the RR Wiki Extensions.
Parameters
There are no user-specified parameters. The template relies upon system-variables that automatically determine the specific page's title.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the pre tags) can be used as a model.
{{Refreshpage}}
Result
See the very bottom of the Maryland State Police and the FiRST Migration for an example
Return to: Template:Refreshpage
Documentation Sub-page for Template:Table_ELTRfreqs
Scope of Use
Purpose
- This template is to be used to define the Frequencies (by Logical Channel Number, or LCN) of any EDACS or LTR system that is being researched.
- This template was designed to mimic (to some degree) the frequency grid in the database. This should make it easier for the DBAs to copy the data when it's appropriate.
Directly Invoked By
Parameters
Parameter Name | Var Description | Expected Value(s) | Default Value | Notes |
---|---|---|---|---|
Sitenumber |
|
Start with 01 | ||
Sitename |
|
|||
Freqxx | Freq01 - Freq32 |
|
000.00000 | default value displays subdued as 000.00000 |
HideLCN | Hide the LCN numbers and title-prefix |
|
|
Please do not specify a value for this parameter |
Future-Design Notes
- Please note: Another template is derived from this template. Before changing this template's design, be sure to identify the impact those changes will have on each derivative template. If you have questions, please ask either in the Wiki Forum, or by sending a PM to the Wiki Admin, W9BU.
Usage Notes
- If there are multiple sites to this system, define 1 page for each site.
- There is space in the template for a total of 32 channels. Not all channels need to be filled - if there's only 10 frequencies in the system, then the rest should be removed from the copy of the template being applied. The rest will be resolved automatically. XX should vary from 1 to 32.
- It is possible that the frequencies and LCNs may not be in sequential order. This is common with LTR systems, but can happen in EDACS systems, too
- The COLOR template can be used to make the frequencies red or blue, to correspond with known primary or alternate control (or home) channels.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
It is unncecessary to fill in usued frequencies with zeros
{{Table ELTRfreqs |Sitenumber=01 |Sitename=? |Freq01=000.0000 |Freq02=000.0000 |Freq03=000.0000 |Freq04=000.0000 |Freq05=000.0000 |Freq06=000.0000 |Freq07=000.0000 |Freq08=463.5875 |Freq09=000.0000 |Freq10=000.0000 |Freq11=000.0000 |Freq12=000.0000 |Freq13=000.0000 |Freq14=000.0000 |Freq15=000.0000 |Freq16=454.6375 |Freq17=000.0000 |Freq18=000.0000 |Freq19=000.0000 |Freq20=000.0000 |Freq21=000.0000 |Freq22=000.0000 |Freq23=000.0000 |Freq24=000.0000 |Freq25=000.0000 |Freq26=000.0000 |Freq27=000.0000 |Freq28=000.0000 |Freq29=000.0000 |Freq30=000.0000 |Freq31=000.0000 |Freq32=000.0000 }}
Result
- See the S & P Communications (LTR Regular) article for the result of this template.
Return to: Template:Table_ELTRfreqs
Documentation Sub-page for Template:Table_Motofreqs
Scope of Use
Purpose
- This template is to be used to define the frequencies of any Motorola system that is being researched.
- This template was designed to mimic (to some degree) the frequency grid in the database. This should make it easier for the DBAs to copy the data when it's appropriate.
- This template should NOT be used for defining a MOTOTRBO TRS. Use the Trbosys template for this purpose. This template is not designed to take into account slots and color codes.
Directly Invoked By
- Any Motorola TRS (not MOTOTRBO) that is being researched.
Parameters
- This template is derived from, and will be effected by changes made to, Template:Table_ELTRfreqs.
- This template does not show LCN numbers 01-32.
Parameter Name | Var Description | Expected Value(s) | Default Value | Notes |
---|---|---|---|---|
Sitenumber |
|
Start with 01 | ||
Sitename |
|
|||
Freqxx |
|
Usage Notes
- If there are multiple sites to this system, define 1 page for each site.
- There is space in the template for a total of 32 channels. Not all channels need to be filled - if there's only 10 frequencies in the system, then the rest should be removed from the copy of the template being applied. The rest will be resolved automatically. XX should vary from 1 to 32.
- The COLOR template can be used to make the frequencies red or blue, to correspond with known primary or alternate control channels.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
{{Table_Motofreqs |Sitenumber=01 |Sitename=Unknown |Freq01=866.0125 |Freq02=867.0125 |Freq03=867.5125 |Freq04=868.1250 |Freq05=868.2000 |Freq06=868.2750 |Freq07=868.3375 |Freq08=868.4000 |Freq09=868.4500 |Freq10=868.5875 |Freq11=868.7125 |Freq12=868.7750 |Freq13=868.8125 |Freq14=n/a |Freq15=n/a |Freq16=n/a |Freq17=n/a |Freq18=n/a |Freq19=n/a |Freq20=n/a |Freq21=n/a |Freq22=n/a |Freq23=n/a |Freq24=n/a |Freq25=n/a |Freq26=n/a |Freq27=n/a |Freq28=n/a |Freq29=n/a |Freq30=n/a |Freq31=n/a |Freq32=n/a }}
Result
- See the Chautauqua County (NY) Unknown Trunking article for the result of this template.
Return to: Template:Table_Motofreqs
Documentation Sub-page for Template:Table_Trbosys
Scope of Use
Purpose
- This template is to be used to define the Frequencies, slots, color codes of any DMR / MOTOTRBO trunked system. In addition, each frequency can be appended with a short comment. If longer descriptions are necessary, add a new section at the bottom of the table, and describe in detail.
- This template is required because the current version of the RRDB does not display this information correctly, if at all.
Directly Invoked By
- Any TRS that contains the Tracker_DMR template.
Parameters
Parameter Name | Var Description | Expected Value(s) | Default Value | Notes |
---|---|---|---|---|
TrunkName |
|
A value is Required | ||
SiteName |
|
A value is Required | ||
ChanNumxA |
|
|||
ColorCodexA |
|
|||
TrunkFreqxA |
|
A value is Required | ||
CommentsxA |
|
|||
ChanNumxB |
|
|||
ColorCodexB |
|
|||
TrunkFreqxB |
|
A value is Required | ||
CommentsxB |
|
|||
StateName |
|
A value is Required |
Usage Notes
- If there are multiple sites to this system, define 1 page for each site.
- Slot numbers in the template are stated as A or B, but in reality they are slots 1 and 2. This convention was chosen to avoid confusion when reading channel numbers and slots together - for example, if we wish to define channel 01 slot 1, if someone printed 011, it would be very easy to think this was channel 11. The letters A and B reinforce the 2 slot principle without sacrificing accuracy.
- CAUTION - The entry of frequencies in the RRDB has been highly variable in its accuracy. Many are attempting to represent the same frequency twice in an attempt to display slots 1 and 2. This results in the system showing the frequencies repeated twice.
- There is space in the template for a total of 64 channels (32 channels x 2 slots / channel). Not all channels need to be filled - if there's only 10 frequencies in the system, then the rest should be removed from the copy of the template being applied. The rest will be resolved automatically. x should vary from 1 to 32.
- The COLOR template can be used to make the frequencies red or blue, to correspond with known primary or alternate control channels.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
Note that there are only 2 frequencies, with 2 slots, in this system. The Hide statement indicates the rest of the template is not needed, and is dropped.
{{Table_Trbosys |TrunkName=Vernon Independent School District |StateName=Texas |SiteName=Vernon |ChanNum1A=01 |ColorCode1A=5 |TrunkFreq1A=452.2750 |- |ChanNum1B=01 |ColorCode1B=5 |TrunkFreq1B=452.2750 |- |ChanNum2A=02 |ColorCode2A=5 |TrunkFreq2A=452.9750 |- |ChanNum2B=02 |ColorCode2B=5 |TrunkFreq2B=452.9750 |Hide3= }}
If you do not want the "See the Monitoring DMR and Monitoring TRBO sections of the DMR MOTOTRBO articles for compatible receivers, scanners and applications" statement at the top of the table, include the following line in your configuration:
|HideTrackerDMR=
If you don't want the categories added to the page automatically, include the following line:
|NoCategory=
Result
- See the Vernon Independent School District DMR Bandplan article for the result of this template.
Return to: Template:Table_Trbosys
Documentation Sub-page for Template:Text Airshow
Scope of Use
Purpose
- This template should be used to supply a standardized header for articles documenting frequency and talkgroup usage (where applicable) at airshows
Directly Invoked By
- Any article that documents freqs and talkgroups used at airshows
- The Text_MTairhow template is also called within this template to provide a standardized link to the Airshow Guide that Amazon sells and is published by Teak Publishing
- The DB template is used to build a link to the database entry for a given ARTCC center.
Parameters
- There are 2 tokens that are required to execute this template
- Airshowname - The name of the airshow, with the year if needed
- ARTCCname - The name of the ARTCC center in which this show takes place. Often flights have to traverse a Center's airspace to arrive at the show, making it a point of interest.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
{{Text_Airshow |Airshowname=Vectren Dayton International Airshow |ARTCCname={{DB|a|2234|Indianapolis}}}}
Result
- See the Vectren Dayton International Airshow article
Return to: Template:Text Airshow
Documentation Sub-page for Template:Text_CatGeneral
Scope of Use
Purpose
- Template:Text_CatGeneral is designed to be a single-source text-template that provides a common and uniform structure for the text that is displayed in the mid-sections of Template:Text_CatStateOther, Template:Text_CatStateOtherFreq, Template:Text_CatStateOtherNonRRDB.
- Parameters listed below allow the default message to be shown or hidden, and/or custom-messages to be displayed when provided.
- The default message is intended for frequencies-related categories, and contains instructions about submitting information to the Frequency Database.
Directly Invoked By
- Template:Text_CatGeneral should be directly invoked only by Template:Text_CatStateOther, Template:Text_CatStateOtherFreq, and Template:Text_CatStateOtherNonRRDB.
Not Intended For
- Template:Text_CatGeneral should not be directly invoked by any other template or category, although all templates and categories that invoke either Template:Text_CatStateOther or Template:Text_CatStateOtherFreq or Template:Text_CatStateOtherNonRRDB will indirectly invoke Template:Text_CatGeneral by transclusion.
Parameters
- Specified values will override default values.
- Specified values, Default values, and Parameter Names are all case-sensitive.
Parameter Name | Var Description | Expected Value(s) | Default Value | Notes |
---|---|---|---|---|
HideRRDBText |
|
unspecified |
| |
HideFreqText |
|
unspecified |
| |
MoreText |
|
unspecified |
|
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template to show only the default message
- {{Text_CatGeneral}}
Result
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
How to invoke this template to show both default and custom messages
-
{{Text_CatGeneral|MoreText=<br/><br/>This is a custom message.}}
Result
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
The data in the articles listed below:
- should not be submitted to the data base team until the data have been validated.
- Please read RR Database Submission Guidelines before submitting validated data to the Frequency Database.
- Please read Wiki Extensions to learn how to incorporate Database-data into a Wiki page.
- Please use tables if there are more than a couple lines of data.
- This enables several applications to capture this data, copy it into Windows clipboard, and from there to your scanner programming software. This helps to avoid a large amount of tedious (and error prone) manual typing and copying. See the Applications that can copy Frequency Data from the Wiki article for more information.
This is a custom message.
How to invoke this template to show only a custom message
-
{{Text_CatGeneral|HideFreqText=|MoreText=<br/><br/>This is a custom message.}}
Result
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
This is a custom message.
How to invoke this template to show neither the default nor a custom message
-
{{Text_CatGeneral|HideFreqText=|MoreText=|}}
Result
In general, data in any Wiki article:
- should be used to supplement the data in our Frequency Database.
- may not be accurate. Members are encouraged to listen and validate it, and to edit the articles.
Return to: Template:Text_CatGeneral
Documentation Sub-page for Template:Text Deprecated
Scope of Use
Purpose
- This template will flag a particular TRS as having been marked as Deprecated in the RR database
- This system should then be added to that state's Deprecated trunk system list, and removed from the active table.
Directly Invoked By
- Any system marked as Deprecated in the RR database.
Parameters
- There are no parameters for this template
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Text Deprecated}}
Result
NOTE: This system has been marked as deprecated in the RRDB.
Return to: Template:Text Deprecated
Template:Text DeprecatedStateTRS/doc
Documentation Sub-page for Template:Text MTairshow
Scope of Use
Purpose
- This template should be used to point to the most current version of the Air Show Monitoring Guide distributed by Amazon. It was originally published by Monitoring Times magazine (hence the MT in the name) but is now published by The Spectrum Monitor magazine.
Directly Invoked By
- Any article that documents airshows where military flights would be involved
Parameters
- This template has no parameters. However, the link to the Spectrum Monitor issue should be updated each year to point to the most current version of the guide.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim.
{{Text_MTairshow}}
Result
- See the March 2017 issue of the Spectrum Monitor magazine
Return to: Template:Text MTairshow
Documentation Sub-page for Template:Tracker_DMR
Scope of Use
Purpose
- This template is designed to warn users that DMR / MOTOTRBO trunked systems can be tracked using certain scanners and applications. A list of these is linked to in the text.
Directly Invoked By
- Any Trunked Radio System article that is defined as MOTOTRBO (of any type, including Capacity Plus or Connect Plus) should install this template.
- This template is auto-invoked with defining a TRBO networked conventional frequency by using the table_trboconventional template
- This template is also auto-invoked when defining a DMR Bandplan using the table_trbosys template.
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_DMR}}
Result
- See FleetTalk (Houston Connect Plus) for an example of this template flagging a Connect Plus system
- See FleetTalk (Houston Capacity Plus) for an example of this template flagging a Capacity Plus system
Return to: Template:Tracker_DMR
Documentation Sub-page for Template:Tracker_LTR
Scope of Use
Purpose
- This template is designed to warn users that LTR MultiNet and LTR Passport trunked systems can't be trunktracked by any scanner. The frequencies, however, can be scanned conventionally. A link to compatible applications is also supplied.
Directly Invoked By
- Any Trunked Radio System article that defines LTR Multinet or Passport as the system type as defined in the RRDB
Parameters
- LType - Should be filled in with Multinet or Passport
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
These examples can be used nearly verbatim to flag appropriate systems. Remove the nowiki tags and the asterisk in the leftmost position.
- {{Tracker_LTR|LType=Multinet}}
- {{Tracker_LTR|LType=Passport}}
Result
- LTR-Multinet systems and/or talkgroups cannot be trunktracked with any scanner. However you can listen to the frequencies conventionally. See our Trunked Radio Decoders page for compatible applications
- LTR-Passport systems and/or talkgroups cannot be trunktracked with any scanner. However you can listen to the frequencies conventionally. See our Trunked Radio Decoders page for compatible applications
Return to: Template:Tracker_LTR
Documentation Sub-page for Template:Tracker_MPT-1327
Scope of Use
Purpose
- This template is designed to warn users that MPT-1327 trunked systems can't be trunktracked by any scanner. A link to compatible applications is also supplied.
Directly Invoked By
- Any Trunked Radio System article that is defined as MPT-1327
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_MPT-1327}}
Result
- Note: MPT-1327 systems cannot be trunktracked by any scanner. See our Trunked Radio Decoders article for a list of compatible applications.
Return to: Template:Tracker_MPT1327
Documentation Sub-page for Template:Tracker_NXDN
Scope of Use
Purpose
- This template is designed to warn users that NXDN (NEXEDGE or IDAS) systems can be monitored using certain scanners and applications. A link to compatible scanners and applications is supplied.
Directly Invoked By
- Any Trunked Radio System article that is defined as NXDN (either flavor)
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_NXDN}}
Result
See the General Communications article to view an example of what this looks like when the template is invoked.
Return to: Template:Tracker_NXDN
Documentation Sub-page for Template:Tracker_OpenSky
Scope of Use
Purpose
- This template is designed to warn users that OpenSky trunked systems can't be trunktracked by any scanner.
Directly Invoked By
- Any Trunked Radio System article that is defined as OpenSky
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_OpenSky}}
Result
- NOTE: This system cannot be trunked or monitored by any scanner
Return to: Template:Tracker_OpenSky
Documentation Sub-page for Template:Tracker_Phase2
Scope of Use
Purpose
- This template is designed to warn users that Project 25 Phase II (or X2-TDMA) trunked systems can't be trunktracked by all trunktrackers. A link to compatible scanners that can trunktrack these systems is supplied.
Directly Invoked By
- Any Trunked Radio System article that is defined as Project 25 Phase II or X2-TDMA in the RRDB
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_Phase2}}
Result
- Some talkgroups on this system may be using P25 Phase II TDMA modulation, which can only be monitored using a P25 Phase II capable scanner or receiver.
- Click HERE for a list of scanners capable of monitoring those talkgroups.
Return to: Template:Tracker_Phase2
Documentation Sub-page for Template:Tracker_Provoice
Scope of Use
Purpose
- This template is designed to inform users that only some Uniden scanners (with a firmware update) can decode this mode. It also supplies links to compatible applications.
Directly Invoked By
- Any Trunked Radio System article that is defined as EDACS ProVoice
Parameters
- There are no parameters for this template.
Examples
- The horizontal lines below separate examples for clarity and do not appear when template is invoked.
How to invoke this template
The line below (between the nowiki tags) can be copied verbatim to flag the page with the appropriate warning.
{{Tracker_Provoice}}
Result
See the Harnett County Public Safety article for an example of how to invoke the template and the resulting message.
Return to: Template:Tracker_Provoice