Actions

User

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
InfoBox project related:
Template:ForTestingOnly
OLD: NEW:



. Test template(s) and "/doc" templates are "used" here simply to keep them from being included in the Special:Unused Templates list.

 Trunked Radio System
NameQDP2012/30/1/1
Owner
Owner Type
City
County
State
CountryUnited States
System Details
Band
Type
ID
Connect Tone
P25 WACN
P25 NAC
DMR / TRBO Color Code
NXDN / NEXEDGE RAN
TETRA MCC
TETRA MNC
TETRA SSI
FCC Callsign(s)
[1]
System-specific links
DatabaseFCC Site Map
ForumRR Site Map
Other Resources
Trunktracking
FAQ		Trunktracking
Glossary
Wiki FAQMediaWiki
QuickRefPDF Card


Wiki Home → Collaboration Gateway → United States → {{{State}}} → {{{County}}} County → QDP2012/30/1/1 TRS

Welcome to the QDP2012/30/1/1 collaboration article, a Trunked Radio System located in {{{County}}} County, {{{State}}}, United States.
This is where you, the user, may index any articles you develop for scanning related topics for this Trunked Radio System.


Contents

Documentation Sub-page for Template:Cat_State

Scope of Use

Purpose

  • Template:Cat_State should be used to build category-pages for individual US States, Territories, etc. and Canadian Provinces.
  • Template:Cat_State is designed to be a categories-template that provides a common and uniform structure for both the text that is displayed on, and the categories assigned to, specific "state"-level categories.

Directly Invoked By

Not Intended For

  • Template:Cat_State should not be directly invoked by any other template or category, including state-specific sub-categories below a primary "state"-level category.

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
CategoryName
  • the category-article's own name (not its parent's name).
 A value is Required
ParentCat (Parent Category)
  • name of the category-article's parent-category
 Collaboration
loctype (location type) (without quotes)
  • either "state"
  • or "province"
  • or "district".
 state
  • The value should be the noun that is grammatically correct for the specified "state" wiki article.
StateWikiArticle
  • the proper title for the related Wiki article.
 A value is Required

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_State
    |CategoryName=Texas
    |StateWikiArticle=Texas (US)}}
Result

Welcome to the "Category:Texas" category which is a sub-category of "Category:Collaboration". Please assign this category to all articles relating to information from entities in the state of Texas.

To assign this category to an article, please add [[Category:Texas]] as the last line.


You may find this state's Wiki article at Texas (US).

How to invoke this template for the US District of Columbia

  • {{Cat_State
    |CategoryName=District of Columbia
    |loctype=district
    |StateWikiArticle=District of Columbia (DC)}}
Result

Welcome to the "Category:District of Columbia" category which is a sub-category of "Category:Collaboration". Please assign this category to all articles relating to information from entities in the district of District of Columbia.

To assign this category to an article, please add [[Category:District of Columbia]] as the last line.


You may find this district's Wiki article at District of Columbia (DC).

How to invoke this template for a Canadian Province

  • {{Cat_State
    |CategoryName=Quebec
    |loctype=province
    |StateWikiArticle=Quebec (CA)
    |ParentCat=Canada}}
Result

Welcome to the "Category:Quebec" category which is a sub-category of "Category:Canada". Please assign this category to all articles relating to information from entities in the province of Quebec.

To assign this category to an article, please add [[Category:Quebec]] as the last line.


You may find this province's Wiki article at Quebec (CA).




Return to: Template:Cat_State

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

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:


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:


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:


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:


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

View the "Amateur Radio" tab on the related database page.

View the "Trunked Systems" tab on the related database page.

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


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

{{{County}}} County, Illinois
County Number {{{County Number}}}
ISP Troop {{{ISP District}}}
SOS District {{{IL SOS District}}}
IDOT District {{{IDOT District}}}
DNRE District {{{DNRE District}}}
FBI Division {{{FBI HQ}}}
FBI Resident Agency {{{FBI RA}}}
FIPS Code {{{FIPS}}}
ctid {{{ctid}}}
{{{County}}} County Database
Illinois Forum
MediaWiki
QuickRef
PDF Card

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


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

  • Any EDACS or LTR TRS that is being researched.


Parameters

Parameter Name Var Description Expected Value(s) Default Value Notes
Sitenumber
  • The number of the site transmitting this TRS
 Start with 01
Sitename
  • The name of the transmitting site (if known)
Freqxx Freq01 - Freq32
  • The frequency for this LCN - see Usage Notes below
 000.00000 default value displays subdued as
000.00000
HideLCN Hide the LCN numbers and title-prefix
  • Not specified (shows LCN numbers)
  • Specified, with no value (hides LCN numbers)
  • Not specified
 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

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
  • The number of the site transmitting this TRS
 Start with 01
Sitename
  • The name of the transmitting site (if known)
Freqxx
  • One of the TRS frequencies - see Usage Notes below


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

Return to: Template:Table_Motofreqs

Scope of Use

Purpose

  • This template is to be used to define the slots, groups (similar to talkgroups in a trunk system) and color codes of any DMR MOTOTRBO conventional frequency.
  • It can also be used for those RRDB entries that are defined as a DMR conventional network and found in the trunk system area.
  • This template is required because the current version of the RRDB does not display this information.

Directly Invoked By

  • Any frequency that is flagged as DMR in the RRDB


Parameters

The following lists the parameters as used by this template. Examples of coding are noted below

  • StateName - The name of the state, county or country
  • Freq - Self Explanatory. If there is more than 1 frequency for this organization, label the first one with Site 1 after the frequency, Site 2 for the second, and so on.
  • User - A short description of the organization using this frequency. See the Usage Notes section
  • CCode - The color code (CCode) used by this frequency
  • TimeSlotX - The Time Slot for this group. X must be 1-12. The actual value of the timeslot should be either 1 or 2. No other values are valid.
  • GroupNumberX - The group number that uses this slot. X must be 1-12
  • DescriptionX - A short description of the user of this group. See the Usage Notes section. X must be 1-12


Usage Notes

  • If there are multiple sites to this system, use the second example below as a guide. It will suppress the DMR warning from being displayed more than once
  • The number of available entries is currently 36, but can be easily expanded.
  • If longer descriptions are required, place a note in the variable to see the section below the table. Code this section and supply as much detail as desired.
  • If this entity points to a DMR conventional network in the trunked systems area, the use of the DB template is strongly encouraged to provide a link back to the database entity.


Examples

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

How to invoke this template

  • If you have only a single frequency to document, utilize the following code;
{{Table_Trboconventional 
|StateName=Iowa
|Freq=461.6375
|User=Drake University DMR
|CCode=1
|-
|TimeSlot1=1
|GroupNumber1=100
|Description1=Security Channel 1
|-
|TimeSlot2=2
|GroupNumber2=200
|Description2=Security Channel 3
}}
  • If there appears to be more than one frequency for the organization, this code should be used. The second call to the template has coding which will suppress the DMR warning from displaying more than once. Code that line exactly as shown
{{Table_Trboconventional
|StateName=Iowa
|Freq=154.505 site 1?
|User=Independence MHI  
|CCode=1
|-
|TimeSlot1=1
|GroupNumber1=315
|Description1=Unknown
|-
|TimeSlot2=2
|GroupNumber1=315
|Description1=Unknown
}}



{{Table_Trboconventional | HideTrackerDMR=|
|StateName=Iowa
|Freq=152.975 site 2?
|User=Independence MHI  
|CCode=1
|-
|TimeSlot1=2
|GroupNumber1=301 
|Description1=Unknown
|-
|TimeSlot2=1
|GroupNumber2=302 
|Description2=Unknown
|-
|TimeSlot3=2
|GroupNumber3=304 
|Description3=Unknown
}}
Result

Return to: Template:Table_Trboconventional

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
  • The name of the TRS as defined in the RRDB
 A value is Required
SiteName
  • The name of the site as defined in the RRDB
 A value is Required
ChanNumxA
  • The channel number for slot 1 - see Usage Notes below
ColorCodexA
  • The color code associated with this frequency and slot
TrunkFreqxA
  • The frequency as found in the RRDB - see Usage Notes below
 A value is Required
CommentsxA
  • A Short description or comment on usage
ChanNumxB
  • The channel number for slot 2 - see Usage Notes below
ColorCodexB
  • The color code associated with this frequency and slot
TrunkFreqxB
  • The frequency as found in the RRDB - see Usage Notes below
 A value is Required
CommentsxB
  • A Short description or comment on usage
StateName
  • The State (or Province) in which this TRS resides
 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

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


Return to: Template:Text Airshow

Documentation Sub-page for Template:Text_CatGeneral

Scope of Use

Purpose

Directly Invoked By

Not Intended For

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
  • either unspecified
  • or specified with no value
 unspecified
  • When unspecified, the default RRDB-related message displays (and will be listed as the second bullet item in the list).
  • When specified with no value, the RRDB-related message is hidden.
  • Caution: Please do not specify an actual value for this parameter, as the results will be beyond the designs of both this template and the templates that are expected to invoke this template.
HideFreqText
  • either unspecified
  • or specified with no value
 unspecified
  • When unspecified, the frequency-related message displays (and will be above any custom message specified by the MoreText parameter).
  • When specified with no value, the frequency-related message is hidden.
  • Caution: Please do not specify an actual value for this parameter, as the results will be beyond the designs of both this template and the templates that are expected to invoke this template.
MoreText
  • either unspecified
  • or specified with a custom-message
 unspecified
  • When unspecified, this parameter is hidden.
  • When specified, any custom message assigned to this parameter will be displayed. If the default message is not hidden (using the HideFreqText parameter), then the default message will be displayed above the custom message.

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

Documentation Sub-page for Template:Text Disambiguation

Scope of Use

Purpose

  • This template will create an indexed article that will list the various possibilities for the correct definition of this term, whether it's a region, county, city, system name or a specific place name.
    • The database does not always conform to unique naming standards, and can have multiple entries for the same name in different regions. It may also define the same trunked system, with an identical name and location, but the system has 2 distinctly different system types.


Directly Invoked By

  • Any region, county, city, system name or place name that has more than one identical entry in the database.


Parameters

  • RegionName - Place the name of the region, county, city or place name here. This should be followed by as many links as are necessary to establish an unique entry in the wiki for each entity.


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 copied verbatim 

{{Text_Disambiguation
|RegionName=Boca Raton Resort and Club}}

* [[Boca Raton Resort and Club (LTR System)]]
* [[Boca Raton Resort and Club (DMR System)]]
Result

Welcome to the Boca Raton Resort and Club disambiguation article. This article will link all entities in the database with Boca Raton Resort and Club as a location. Please select the appropriate link from the list below



Return to: Template:Text Disambiguation

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

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

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

Documentation Sub-Page for Set of "Text_CatStateOther..." Templates

Introduction

  • This page compares the parameter-lists of the "Text_CatStateOther..." templates listed below, which are designed to use many of the same parameters, and to invoke template "Text_CatGeneral" in different ways.

Parameter-List Comparison

  • The parameters below are listed in the order of "likely importance" or "most often used".
  • To sort by a particular column, click the arrow beside that column's title. Click the arrow again to reverse the sort.
Parameter Name Exists in
Text_CatStateOther		 Exists in
Text_CatStateOtherFreq		 Exists in
Text_CatStateOtherNonRRDB
State Yes Yes Yes
State2 Yes Yes Yes
StateParentNotFreq -- Yes --
Other Yes Yes Yes
Other2 Yes Yes Yes
OtherIsNotFreq -- Yes --
HideOtherInTitle Yes Yes Yes
HideOtherInList Yes Yes Yes
OtherInState Yes -- Yes
OtherFreqInState -- Yes --
HideParent3 -- Yes (Note 2) --
Country Yes Yes Yes
Articles Yes Yes Yes
MoreText Yes (Note 1) Yes (Note 1) Yes (Note 1)
Parent4 Yes Yes Yes
Parent5 Yes Yes Yes
Parent6 Yes Yes Yes
Parent7 Yes Yes Yes
HideParent4 Yes Yes Yes
HideParent5 Yes Yes Yes
HideParent6 Yes Yes Yes
HideParent7 Yes Yes Yes
TextHasNoParent -- -- Yes (Note 3)
HideAllParents -- -- Yes (Note 3)
SubmittedBy -- -- Yes (Note 4)

Invoking Template:Text_CatGeneral

Text_CatGeneral
Parameter Name		 Used By Template
Text_CatStateOther		 Used By Template
Text_CatStateOtherFreq		 Used By Template
Text_CatStateOtherNonRRDB
HideRRDBText -- -- Yes
HideFreqText Yes -- Yes
MoreText Yes (Note 1) Yes (Note 1) Yes (Note 1)

Notes

  • Note 1
    • Parameter MoreText exists as a parameter in the templates that invoke Text_CatGeneral, thus allowing a "pass-through" effect so that custom messages can be displayed uniformly in all templates and categories that use Text_CatGeneral.

  • Note 2
    • Parameter HideParent3 hides the value of "Parent3" which is a parameter that is not user-defined, but is automatically created by the template's logic. Please see Text_CatStateOtherFreq/doc for more information.

  • Note 3
    • Parameters TextHasNoParent and HideAllParents should be used only with the top-category for an entire category-tree; and should be used as a pair, not just one. Example: Category:Gateways.

  • Note 4
    • Parameter SubmittedBy should be used only when the category's articles are submitted only by administrators, not by regular members. Examples: Category:Gateways, Category:Legal

View the corresponding Sub-Category Location report.

View the corresponding Sub-Category Details report.

View the corresponding TRS System Site Location report.

View the corresponding TRS Talkgroup Category Location report.

Documentation Sub-page for Template:Text_CatStateOtherFreq

Scope of Use

Purpose

  • Template:Text_CatStateOtherFreq is designed to be a "text"-template which:
    • functions as the base upon which individual "...Frequencies" categories, and simpler "...Frequencies" categories-templates are built.
      • This creates a standardized presentation-style for the text displayed on all individual "...Frequencies" categories and all "...Frequencies" category-templates. Exceptions should be few.
    • naturally applies to state-, county-, and country-based "...Frequencies" categories
    • is also intended to be used to create "...Frequencies" categories that are not state-, county-, or country-based, such as top-level theme-based "...Frequencies" categories.

Directly Invoked By

  • Template:Text_CatStateOtherFreq should be directly invoked only by
    • simpler "...Frequencies" categories-templates, or
    • top-level theme-based "...Frequencies" categories, or
    • individual "...Frequencies" categories for which a simpler "...Frequencies" categories-template does not exist.

Not Intended For

  • Template:Text_CatStateOtherFreq should not be directly invoked by anything other than "...Frequencies" "categories" pages, or simpler "...Frequencies" "categories"-templates.

Parameters

Parameter Name Parameter Details
State Notes:
  • A value is Required
    This template's use is not limited to politically-defined "states". The parameter State can be assigned a theme-based value instead. See any of Category:Special Topics' sub-categories for example.
State2 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When not specified, State value is used in the categories-list
  • When specified with a specific value, the specific value is used to override State in the categories-list, but not in the title.
    • State2's value should be the name of the State-category's primary parent, and should have a value very similar to State's value when possible.
StateParentNotFreq Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the word "Frequencies" is appended to the State (or State2 if used) value in the categories-list.
  • When specified with no value, the word "Frequencies" is NOT appended to the State (or State2 if used) value in the categories-list.
  • Please do not assign a specific value to this parameter.
Other Notes:
  • A value is Required unless BOTH HideOtherInTitle and HideOtherInList are utilized to hide the value of Other
Other2 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When not specified, Other value is used in the categories-list
  • When specified with a specific value, the specific value is used to override Other in the categories-list, but not in the title.
  • Also, see notes about parameter HideOtherInList
OtherIsNotFreq Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the word "Frequencies" is appended to the Other (or Other2 if used) value in the title and in the categories-list.
  • When specified with no value, the word "Frequencies" is NOT appended to the Other (or Other2 if used) value in the title and in the categories-list.
  • With rare exception, Please do not assign a specific value to this parameter.
OtherFreqInState Expected Value(s):
  • not specified (Default value)
  • specified with a State-parameter related value. Examples:
    • OtherFreqInState=US {{{Agency}}} Frequencies in {{{State}}}|
    • OtherFreqInState=United States {{{MilBranch}}} Frequencies in {{{State}}}|
Notes:
  • This overrides the value displayed in the title and the page's example category-statement.
  • This does not influence the list of parent-categories.
  • Values for State and Other still should be assigned appropriately.
Country Expected Value(s):
  • not specified (Default value)
  • specified with specific value, followed by a non-breaking space (&nbsp;)
    • Example: Country=Canada&nbsp;|
Notes:
  • This allows a country-name to be assigned as the prefix to the Other (or Other2) value in the categories-list only. It does not influence the value of Other (or Other2) in the title.
  • When specified, the Country value is displayed in the categories-list immediately prior to the value of Other (or Other2).
  • When not specified, no value is displayed.
  • Also, see notes about parameter HideOtherInList
Parent3 Automatic Value(s):

Using values from parameters above, either:

  • State Other, or State2 Other, or State Other2, or State2 Other2
Notes:
  • Parent3's value is automatically created using the values of State (or State2 if used) and Other (or Other2 if used).
  • Parent3's value cannot be manually assigned by the Wiki-editor; but can be hidden using HideParent3 listed below.
Parent4 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When specified, the Parent4 value is displayed in the categories-list.
  • When not specified, please use HideParent4 to hide Parent4.
Parent5 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When specified, the Parent5 value is displayed in the categories-list.
  • When not specified, please use HideParent5 to hide Parent5.
Parent6 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When specified, the Parent6 value is displayed in the categories-list.
  • When not specified, please use HideParent6 to hide Parent6.
Parent7 Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When specified, the Parent7 value is displayed in the categories-list.
  • When not specified, please use HideParent7 to hide Parent7.
Articles Expected Value(s):
  • not specified (Default value)
  • specified with specific value, that begins with a non-breaking space (&nbsp;). Example:
    • Articles=&nbsp;that list amateur radio repeaters in {{{State}}},|
Notes:
  • Below the categories-list is the following statement (without quotes):

    "Lists all the articles...as submitted by the members."
    • The ... in the line quoted above represents the position of the default article-description which is (without quotes):

      " for Category:State that contain Other Frequencies"

  • When Articles is not specified, the default article-description is displayed.
  • When Articles is specified, the specific value replaces the default article-description.
    • Note: Usually, a non-breaking space (&nbsp;) should be used as the first character of the specific value.
MoreText Expected Value(s):
  • not specified (Default value)
  • specified with specific value
Notes:
  • When not specified, nothing is displayed
  • When specified, the specific value is displayed above the example category-statement, approximately in the middle of the page.
  • Horizontal lines and html-breaks are often used to provide visual separation and bring attention to this parameter's value.
HideOtherInTitle Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Other is displayed in the title
  • When specified with no value, the value of Other is not displayed in the title
  • Please do not assign a specific value to this parameter.
HideOtherInList Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Country, if used, and the value of Other (or Other2 if used) are displayed in the categories-list
  • When specified with no value, the value of Country, if used, and the value of Other (or Other2 if used) are not displayed in the categories-list
  • Please do not assign a specific value to this parameter.
HideParent3 Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Parent3 is displayed
  • When specified with no value, the value of Parent3 is not displayed
  • Please do not assign a specific value to this parameter.
HideParent4 Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Parent4 is displayed
  • When specified with no value, the value of Parent4 is not displayed
  • Please do not assign a specific value to this parameter.
HideParent5 Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Parent5 is displayed
  • When specified with no value, the value of Parent5 is not displayed
  • Please do not assign a specific value to this parameter.
HideParent6 Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Parent6 is displayed
  • When specified with no value, the value of Parent6 is not displayed
  • Please do not assign a specific value to this parameter.
HideParent7 Expected Value(s):
  • not specified (Default value)
  • specified with no value
Notes:
  • When not specified, the value of Parent7 is displayed
  • When specified with no value, the value of Parent7 is not displayed
  • Please do not assign a specific value to this parameter.
  • Please note:
    • The entire list of user-specified parameters is listed here for convenient copy-pasting.
    • Please read the above table for instruction, and see the examples later in this page, on how to use the appropriate parameters.
    • There will never be a case when all of the following parameters are used at the same time. Only use the needed parameters. Thanks.
    • Parameter "Parent3" is not listed here because its value is automatic, not user-specified.
{{Text_CatStateOtherFreq|
State=|
State2=|
StateParentNotFreq=|
Other=|
Other2=|
OtherIsNotFreq=|
OtherFreqInState=|
HideOtherInTitle=|
HideOtherInList=|
Country=|
Articles=|
MoreText=|
Parent4=|
Parent5=|
Parent6=|
Parent7=|
HideParent3=|
HideParent4=|
HideParent5=|
HideParent6=|
HideParent7=}}

Parameter-Use Examples: Categories-Templates

  • Selected examples that illustrate various combinations of parameters:

Categories-Templates: Emergency Services Frequencies

Categories-Templates: Emergency Services Frequencies} Parameters used
Categories-Template example: Template:Cat_StateFireSvcsFreq State, Other, Country,
HideParent4, HideParent5,
HideParent6, HideParent7
State-specific example(s): Category:Texas_Fire_Services_Frequencies
Category:Canada_Fire_Services_Frequencies
Category:Ontario_Fire_Services_Frequencies
   Template(s) with similar syntax: Template:Cat_StateLawEnfFreq
Template:Cat_StateMedicalFreq
Categories-Template example: Template:Cat_StateFireSvcsAvFreq State, State2, Other, Country, Articles, HideParent3, Parent4, Parent5, HideParent6, HideParent7
State-specific example(s): Category:Texas_Fire_Services_Aviation_Frequencies
   Template(s) with similar syntax: Template:Cat_StateLawEnfAvFreq
Template:Cat_StateMedAvFreq

Categories-Templates: General Services Frequencies

Categories-Templates: General Services Frequencies} Parameters used
Categories-Template example: Template:Cat_StateAvFreq State, Other, Country,
HideParent4, HideParent5,
HideParent6, HideParent7
State-specific example(s): Category:Texas_Aviation_Frequencies
Category:Bermuda_Aviation_Frequencies
Category:Canada_Aviation_Frequencies
Category:Ontario_Aviation_Frequencies
   Template(s) with similar syntax: Template:Cat_StateAmateurFreq
Template:Cat_StateMjrEvtDisFreq
Categories-Template example: Template:Cat_StateAmateurRptr State, State2, Other, Country, OtherIsNotFreq, HideOtherInList, Articles, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:Texas_Amateur_Radio_Repeaters
Category:Canada_Amateur_Radio_Repeaters
Category:British_Columbia_Amateur_Radio_Repeaters
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateBusFreq State, Other, Country, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:Texas_Business_Frequencies
Category:Canada_Business_Frequencies
Category:Ontario_Business_Frequencies
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateBusComPrvFreq State, State2, StateParentNotFreq, Other, Country, HideParent3, MoreText, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:California_Communications_Providers_Frequencies
Category:Australia_Communications_Providers_Frequencies
Category:New_South_Wales_Communications_Providers_Frequencies
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateBusFastFoodFreq State, State2, StateParentNotFreq, Other, Country, HideParent3, HideParent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:New_York_Fast_Food_Frequencies
Category:Canada_Fast_Food_Frequencies
Category:Alberta_Fast_Food_Frequencies
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateCivilAvFreq State, State2, Other, Country, Articles, HideParent3, MoreText, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:Idaho_Civil_Aviation_Frequencies
Category:Canada_Civil_Aviation_Frequencies
Category:Nova_Scotia_Civil_Aviation_Frequencies
   Template(s) with similar syntax: Template:Cat_StateUtilComCarFreq
Categories-Template example: Template:Cat_StateCSXFreq State, State2, StateParentNotFreq, Other, Country, HideParent3, Parent4, Parent5, Parent6, HideParent7
State-specific example(s): Category:Florida_CSX_Transportation_Frequencies
Category:Canada_CSX_Transportation_Frequencies
Category:Quebec_CSX_Transportation_Frequencies
   Template(s) with similar syntax: Template:Cat_StateUtilComCarFreq
Categories-Template example: Template:Cat_StateEducFreq State, Other, Country, Articles, HideParent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:Michigan_Education_Frequencies
   Template(s) with similar syntax: Template:Cat_StateMediaFreq
Template:Cat_StateSportsFreq
Categories-Template example: Template:Cat_StateGrndTransFreq State. Other. Country. MoreText. HideParent4. HideParent5. HideParent6. HideParent7
State-specific example(s): Category:New_York_Ground_Transportation_Frequencies
Category:Canada_Ground_Transportation_Frequencies
Category:Quebec_Ground_Transportation_Frequencies
   Template(s) with similar syntax: Template:Cat_StateMarineFreq
Categories-Template example: Template:Cat_StateMotorFrtFreq State, State2, StateParentNotFreq, Other, Country, HideParent3, Articles, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:New_York_Motor_Freight_Frequencies
Category:Canada_Motor_Freight_Frequencies
Category:Quebec_Motor_Freight_Frequencies
   Template(s) with similar syntax: Template:Cat_StateRailFreq
Categories-Template example: Template:Cat_StateRecAtrFreq State, Other, Country, Articles, MoreText, HideParent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:North_Carolina_Recreation_or_Attractions_Frequencies
Category:Canada_Recreation_or_Attractions_Frequencies
Category:Alberta_Recreation_or_Attractions_Frequencies
   Template(s) with similar syntax: Template:Cat_StateSpcEvtsFreq
Template:Cat_StateUtilFreq
Template:Cat_StateWeatherFreq

Categories-Templates: Federal/Military Frequencies

Categories-Templates: Federal/Military Frequencies} Parameters used
Categories-Template example: Template:Cat_StateAirShowsFreq State, State2, StateParentNotFreq, Other, Country, HideParent3, Parent4, Parent5, HideParent6, HideParent7
State-specific example(s): Category:New York Air Show Frequencies
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateMilAvFreq State. State2, Other, Country, HideParent3, Articles, MoreText, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:California Military Aviation Frequencies
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_StateANGFreq State, Other, Country, HideParent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:Maryland Air National Guard Frequencies
   Template(s) with similar syntax: Template:Cat_StateARNGFreq
Categories-Template example: Template:Cat_USFedFreqInState OtherFreqInState, Agency, State, Other, Other2, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:US Land Management Frequencies in Nevada
   Template(s) with similar syntax:
Categories-Template example: Template:Cat_USMilFreqInState OtherFreqInState, MilBranch, State, Other, Other2, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
State-specific example(s): Category:United States Air Force Frequencies in New York
   Template(s) with similar syntax:

Parameter-Use Examples: Categories

  • Selected examples that illustrate various combinations of parameters:

Categories: Top-level "Theme"-Frequencies

Categories: Top-level "Theme" Frequencies} Parameters used
Categories example: Category:Wiki Frequencies State, State2, StateParentNotFreq, HideOtherInTitle, HideOtherInList, Articles, HideParent3, MoreText, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:
Categories example: Category:Air Show Frequencies State, State2, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Articles, Parent4, Parent5, HideParent6, HideParent7
   Categories with similar syntax: Category:Business Frequencies
Categories example: Category:Amateur Radio Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Articles, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax: Category:Education Frequencies
Categories example: Category:Amateur Radio Repeaters State, Other, OtherIsNotFreq, HideOtherInTitle, HideOtherInList, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax: Unique Special Case
Categories example: Category:Air National Guard Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:
Categories example: Category:Medical Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:
Categories example: Category:Railroads Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Articles, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:

Categories: Aviation Frequencies for a Specific Theme

Categories: Aviation Frequencies for a Specific Theme} Parameters used
Categories example: Category:Fire Services Aviation Frequencies State, Other, Articles, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax: Category:Law Enforcement Aviation Frequencies
Category:Medical Aviation Frequencies
Categories example: Category:Military Aviation Frequencies State, State2, Other, HideOtherInTitle, Articles, MoreText, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:

Categories: CSX Transportation Frequencies

Category:CSX Transportation Frequencies} Parameters used
Categories example: Category:CSX Transportation Frequencies State, State2, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Articles, Parent4, Parent5, HideParent6, HideParent7
   Categories with similar syntax:

Categories: US Agency Frequencies

Categories: US Agency Frequencies} Parameters used
Categories example: Category:US Federal Government Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, MoreText, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:
Categories example: Category:US Civil Air Patrol Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Articles, Parent4, Parent5, Parent6, HideParent7
   Categories with similar syntax:
Categories example: Category:US Federal Prisons Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax: Category:US Bureau of Reclamation Frequencies
Categories example: Category:US Land Management Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, Parent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax:

Categories: United States Military Branch Frequencies

Category:United States Air Force Frequencies} Parameters used
Categories example: Category:United States Air Force Frequencies State, StateParentNotFreq, Other, HideOtherInTitle, HideParent3, HideParent4, HideParent5, HideParent6, HideParent7
   Categories with similar syntax: Category:United States Army Frequencies
Category:United States Coast Guard Frequencies
Category:United States Navy Frequencies

How To...

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

How to invoke this template for a simpler (state) frequencies TEMPLATE

  • Template_CatStateFreq is an example of a simpler category-template that is used to build state-level, district-level, province-level, or country-level, "Frequencies" categories:
{{Text_CatStateOtherFreq|
State={{{State}}}|
StateParentNotFreq=|
Other={{{FreqParent|Wiki}}}|
HideOtherInTitle=|
HideParent3=|
MoreText={{{MoreText|}}}|
HideParent4=|
HideParent5=|
HideParent6=|
HideParent7=}}
Result

How to invoke this template for a simpler US (Agency) Frequencies in (State) TEMPLATE

  • Template:Cat_USFedFreqInState is an example of a simpler category-template that is used to build (US Federal Government) agency-level "Frequencies" categories:
{{Text_CatStateOtherFreq|
OtherFreqInState=US {{{Agency}}} Frequencies in {{{State}}}|
Other={{{Agency}}}|
State={{{State}}}|
Other2=US {{{Agency}}}|
HideParent3=|
Parent4=US {{{Agency}}} in {{{State}}}|
HideParent5=|
HideParent6=|
HideParent7=}}
Result

How to invoke this template for a simpler United States (MilBranch) Frequencies in (State) TEMPLATE

  • Template:Cat_USMilFreqInState is an example of a simpler category-template that is used to build (United States Military) Branch-level "Frequencies" categories:
{{Text_CatStateOtherFreq|
OtherFreqInState=United States {{{MilBranch}}} Frequencies in {{{State}}}|
Other={{{MilBranch}}}|
State={{{State}}}|
Other2=United States {{{MilBranch}}}|
HideParent3=|
Parent4=United States {{{MilBranch}}} in {{{State}}}|
HideParent5=|
HideParent6=|
HideParent7=}}
Result

How to invoke this template for a (theme) frequencies CATEGORY

  • Category:Air_National_Guard_Frequencies is an example of a Theme-level "Frequencies" category:
{{Text_CatStateOtherFreq|
State=Air National Guard|
StateParentNotFreq=|
Other=United States Air Force|
HideOtherInTitle=|
HideParent3=|
Parent4=United States National Guard Frequencies|
Parent5=Military Aviation Frequencies|
HideParent6=|
HideParent7=|}}
Result

How to avoid common error(s) while invoking this template

  • Purpose: To avoid unintended spaces in parameter-values
    • Technique: Place the vertical bar at end of parameter-value, not at left-margin.


  • Purpose: To correctly assign no-value to a parameter
    • Technique: Place the vertical bar at end of parameter-value, not at left-margin.


  • Purpose: To avoid confusion with template's closing braces
    • Technique: Put "Hide..." parameters at end of template-call to help ensure the closing braces are used and not confused with the value of another parameter.


  • Example: Category:Air_National_Guard_Frequencies
    • The following template-code is correct, because
    1. The vertical-bar ends immediately after each parameter-value, or immediately after an equal-sign thereby indicating "no value":
    2. The template's closing pair of braces immediately follows the last parameter-value and is not on a separate line where it could become confusing and orphaned or even deleted during later editing.
    3. The "HideParent..." parameters are placed at the end and immediately followed by the template's closing braces. This becomes more apparent when using parameters "Articles" and "MoreText".
{{Text_CatStateOtherFreq|
State=Air National Guard|
StateParentNotFreq=|
Other=United States Air Force|
HideOtherInTitle=|
HideParent3=|
Parent4=United States National Guard Frequencies|
Parent5=Military Aviation Frequencies|
HideParent6=|
HideParent7=|}}
  • The following template-code is not correct, because it introduces unintended spaces and risks the closing braces becoming orphaned, lost, or deleted during later editing, especially if values are assigned later to parameters "Articles" and/or "MoreText":
{{Text_CatStateOtherFreq
|State=Air National Guard
|StateParentNotFreq=
|Other=United States Air Force
|HideOtherInTitle=
|HideParent3=
|Parent4=United States National Guard Frequencies
|Parent5=Military Aviation Frequencies
|HideParent6=
|HideParent7=
}}




Return to: Template:Text_CatStateOtherFreq, Template:Text_CatStateOther/doc/Compare

Documentation Sub-page for Template:Forum

Scope of Use

Purpose

  • This template creates a stand alone link that points to a specific forum on RadioReference


Directly Invoked By

  • Any article where a direct reference to a RadioReference forum is useful


Parameters

The parameters are numbered as shown below;

[https://forums.radioreference.com/forums/{{{1}}}/ {{{2}}}{{{3| Forum}}}]

  1. - Name of the forum from the URL on RadioReference
  2. - English name of the forum
  3. - (optional) additional identifier for the forum name


Examples

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

{{Forum|aircraft-monitoring-forum.87|Aircraft Monitoring}} results in:

[http://forums.radioreference.com/aircraft-monitoring-forum.87/ Aircraft Monitoring Forum]

which then creates a link called 'Aircraft Monitoring Forum' See the result section.


How to invoke this template

As shown in the above text, you only need to supply the URL reference of the name of the forum and the name you want to use. The template will fill in (or default) the rest

Result

Aircraft Monitoring Forum


Return to: Template:Forum

Documentation Sub-page for Template:DB

Scope of Use

Purpose

  • This template creates a stand alone link for one database entry from the wiki


Directly Invoked By

  • Any article where database information can be referenced, and can be obtained from the database
  • There are various forms of this functionality in many of the trunk system infoboxes
  • This can also be used when documenting a MOTOTRBO conventional network system, where the database has this data in the trunked system area


Parameters

The parameters are numbered as shown below;

[https://www.radioreference.com/db/{{#switch:{{{1}}}|a|s=|browse/}}{{{1}}}id/{{{2}}} {{{3|View the corresponding database page for this article.}}}]

  1. - Should have any of the following values that comes directly from the URL of the database entry.
    • a for agency id (aid).
    • co for country id (coid).
    • ct for county id (ctid).
    • m for metro id (mid).
    • s for system id (sid).
    • st for state id (stid).
  2. - The id number that comes from the URL of the entry.
  3. - Identifying text. The default text is shown after the number, and will display if nothing is assigned.


Examples

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

{{DB|s|1111|This is an example}}

results in:

[https://www.radioreference.com/db/sid/1111 This is an example]

which creates a link that says 'This is an example'


How to invoke this template

Just copy the id identifier and number from the URL for the database entry, and supply an English sounding name.

Result

Embassy Suites


Return to: Template:DB

Documentation Sub-page for Template:Callsign

Scope of Use

Purpose

  • This template creates a stand alone link to the FCC data found in the RR database via the supplied callsign


Directly Invoked By

  • Any article that needs to create a link for obtaining FCC data
  • Some of the Infobox templates either use this explicitly or issue a call for it


Parameters

There are 2 parameters for this template;

  • FCC Callsign - The FCC callsign that use wish touse in the search
  • Optional text - additional identifying text (not required)


Examples

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

* {{Callsign|WQXX778}}


How to invoke this template

  • Just supply the desired FCC callsign for the template. Note that we have a seperate template for looking up amateur radio callsigns
  • This template can't be used with military or federal listings, as that information is maintained in the NTIA, which is unavailable to the general public.


Result


Return to: Template:Callsign

Documentation Sub-page for Template:Thread

Scope of Use

Purpose

  • This template creates a direct link to a specific thread in the RR forums area


Directly Invoked By

  • Any time a discussion can be linked to a topic for better clarity and to provide a place for discussion
  • The wiki talk pages should not be used for this purpose, as not everyone is aware that they exist


Parameters

There are 3 parameters, two of which are pulled directly from the URL of the discussion thread

  • The name of the forum
  • The message number and identifier
  • You can then supply a more meaningful English name for the thread. You should use the actual name of the thread here


Examples

  • The horizontal lines below separate examples for clarity and do not appear when template is invoked.

How to invoke this template

If you wish to point to a thread using this template, follow the steps outlined below


https://forums.radioreference.com/threads/sds200-hum-reports.383938/


Note: Each parameter for the template is separated by a pipe symbol (|). This can be found as the shift of the backslash character ( \ )

  • First, type 2 left curly brackets ( {{ }. This is the shift of the left square bracket ( [ ). Then insert the name of the template.
  • Next, the forum name is required. If you are using a thread in a sub-forum, use the highest level (the parent) for that forum. The thread above comes from the Tech Support sub forum of the Uniden Scanners forum, so we must use that forum's identifier. Thus the forum name is shown below, along with a numeric identifier


https://forums.radioreference.com/forums/uniden-forums.82/


  • The last token of the URL has the data required for the next portion.
    • Take the number found at the very end of the URL and place it in front, followed with a dash.
    • Take the rest of the token and place it after the dash you just entered
    • Put the identifier '.html' at the very end.
  • The last part of the template is a free forum area for a description.
  • Terminate it with 2 right curly brackets ( }} ). This is the shift of the right square bracket ( ] ). Note that the template will hard code 'Thread' at the very end. The result is shown below


{{Thread|uniden-scanners.82|383938-sds200-hum-reports.html|SDS200 Hum Reports}}

Result


Return to: Template:Thread

Documentation Sub-page for Template:Infobox TRS MN

Scope of Use

Purpose

  • This template presents a standardized index with information describing Trunked Radio Systems (TRS) in Minnesota 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


Directly Invoked By

  • TRSs in Minnesota 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
    • Flavor - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
    • 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 '/'
    • FCCLic - 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
    • City - The name of the city from the RRDB where the TRS is based
    • County - The county where the TRS is based (from the RRDB)
    • 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
    • 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.
    • 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_MN
|SysName = Granite Electronics - Avon 
|Flavor  = [[LTR Standard]] 
|Band    = UHF 
|FCCLic  = WPNT360 
|City    = Avon 
|County  = [[Stearns County (MN)|Stearns]] 
|OwnerTy = Private 
|sid     = 3917 
}}
Result

See the Granite Electronics - Avon article for an example


Return to: Template:Infobox TRS MN

Documentation Sub-page for Template:Infobox TRS WI

Scope of Use

Purpose

  • This template presents a standardized index with information describing Trunked Radio Systems (TRS) in Wisconsin 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


Directly Invoked By

  • TRSs in Wisconsin 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
    • Flavor - The type of the TRS being documented. Use the terminology found in the Glossary whenever possible. See the notes below
    • 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 '/'
    • FCCLic - 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
    • City - The name of the city from the RRDB where the TRS is based
    • County - The county where the TRS is based (from the RRDB)
    • 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
    • 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.
    • 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 WI
|SysName = Ozaukee County 
|Flavor  = [[EDACS Standard]] w/[[ProVoice]] 
|Band    = 800  
|FCCLic  = WNWS961 
|City    = ? 
|County  = [[Ozaukee County (WI)|Ozaukee]] 
|OwnerTy = Public 
|sid     = 2623   
}}
Result

See the Ozaukee County Public Safety article for an example


Return to: Template:Infobox TRS WI

Multi-State
Military Trunked Radio System

NameQDP2012/30/1/1
Ownermilitary
Owner TypeMilitary
StatesMultiple
CountryUnited States
System Details
Band?
TypeProject 25 Phase II
ID?
WACN?
NAC?
System-specific links
DatabaseFCC Site Map
Multi State Forum
Military Forum		RR Site Map
Other Resources
Trunktracking
FAQ

Military FAQ		Trunktracking
Glossary

Military Glossary
Wiki FAQMediaWiki
QuickRefPDF Card

Wiki Home → Collaboration Gateway → United States → multiple states → QDP2012/30/1/1 TRS

Welcome to the QDP2012/30/1/1 collaboration article, a Multi-State Military Trunked Radio System located in multiple states, United States.
This is where you, the user, may index any articles you develop for scanning related topics for this Trunked Radio System.


  • 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.
Multi-County
Public Trunked Radio System

NameQDP2012/30/1/1
Ownermunicipality
Owner TypePublic
CountiesMultiple
State
CountryUnited States
System Details
Band?
TypeTETRA
ID?
MCC?
MNC?
SSI?
FCC Callsign(s)
[2]
System-specific links
DatabaseFCC Site Map
ForumRR Site Map
Other Resources
Trunktracking
FAQ		Trunktracking
Glossary
Wiki FAQMediaWiki
QuickRefPDF Card

Wiki Home → Collaboration Gateway → United States → {{{State}}} → multiple Counties → QDP2012/30/1/1 TRS

Welcome to the QDP2012/30/1/1 collaboration article, a Multi-County Public Trunked Radio System located in multiple Counties, {{{State}}}, United States.
This is where you, the user, may index any articles you develop for scanning related topics for this Trunked Radio System.


  • There are no scanners on the market currently that can copy TETRA systems. See the link for more information and apps that may be useable

Documentation Sub-page for Template:Tracker_TETRA

Scope of Use

Purpose

  • This template is designed to warn users that TETRA trunked systems can't be trunktracked by any scanner. However there are applications under development and they are being discussed in our forum.


Directly Invoked By

  • Any Trunked Radio System article that is defined as TETRA


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_TETRA}}

Result
  • There are no scanners on the market currently that can copy TETRA systems. See the link for more information and apps that may be useable



Return to: Template:Tracker_TETRA

GRE Radio Shack Whistler
PSR-7007 Pro-1077
Pro-181,5,8
PSR-8002,5,8 Pro-6682,5,8 WS10802,3,8
WS10882,3,6
TRX-12,3,4
PSR-9009 WS10952,3
WS10982,3,6
TRX-22,3,4
  1. Released around the time the PSR-800 was, but lacking additional/advanced features SEE #5.
  2. Project 25(P25) Phase I and II decoding.
  3. Capable of DMR decoding, with a free Upgrade to the latest Firmware via Whistler's EZ-Scan software.
  4. Capable of NXDN decoding, with a free Upgrade to the latest Firmware via Whistler's EZ-Scan software
  5. Ability to be Upgraded for DMR (and add P25 Phase II to Pro-18) decode with a Paid Upgrade with User paid shipment to Whistler, returned by them. Once, returned, continued forward support is possible via Whistler Repair and EZ-Scan Software, with all the newer additions and features of a WS1080.
  6. Variant with Keypad
  7. Trunking w Analog Voice Only
  8. ALL THE SAME after UPGRADE except silk screening
  9. Never released publicly, subsequently became WS1095
Chnl DEC HEX Mode Alpha Tag Description Tag

FCC License Frequency Summary 0000

Retrieved from "https://wiki.radioreference.com/index.php?title=User:QDP2012/30/1/1&oldid=237225"