"Raw" Database data format
A notice to users of the ARRL Repeater Directory and the "RF Finder" app - an updateThere is now a working agreement between the Utah Frequency coordinator and RF Finder (which also provides repeater data to the ARRL) in which it is now possible to make changes to the database. Because this update method is entirely manual (e.g. it is done online via forms and tables) it will take some time to go through the relevant Utah data and make the necessary corrections and updates. In the future, unless a means by which data may be synchronized is devised, updates to RF Finder data may lag those on the Utah VHF Society page.
Please note that the Utah VHF Society is responsible only for data related to Utah repeaters and that it will be up to other entities to keep their portions of the database current.
Note: This "raw" data file contains all information that is considered to be public. This not only refers to repeater information, but Simplex frequencies, Remote bases, Link, Control, and a few other uses. It does not contain information such as link frequencies, control frequencies, and other frequencies that, at the request of the trustee, is to be kept confidential. Owing to the critical nature of some of the uses of these frequencies, they are not listed here.
Remember: Just because a frequency is not listed, that does not mean that it is not used! If you see an entry that is incorrect or that you do (or do not) want listed (and you are the responsible party for that listing) then please notify the Frequency Coordinator.
This is the same data that is sent to the ARRL for publication in the repeater directories, and is the same data that is used in the UVHFS booklet. Some of the fields are formatted in the manner specified by the ARRL, and others have been added as deemed necessary by the frequency coordinator to aid in record keeping.
A Note about packet listings:
The packet database is no longer being actively maintained by the frequency coordinator on a station-by-station basis. The packet information is no longer being included in the raw data file as it was so far out of date that it was practically worthless For more information on packet operation, go to the 2 Meter Repeater Pair Utilization along the Wasatch Front page and look at the portion specific to packet operation.
If you wish to take a stab at providing reasonably up-to-date information on packet activity, then please contact the Frequency Coordinator.
The formats and abbreviations used in the database are defined below.
PLEASE NOTE that this format has changed as of January, 2004.
The raw file is in comma-delimted or “CSV” format. This format is accepted by many spread-sheet and database programs and is reasonably easy to work with if you wish to write a custom program.
Some fields may have embedded commas. When this happens, the entire field is enclosed in double quotation marks so that the embedded commas will not be confused with the field-separating commas:
Thus, fields may contain the entire printable character set.
Downloading for Windows Users
The file currently resides on a Linux-based server. Linux uses a different convention for line endings than do DOS and Windows systems. Some Windows applications (including Excel) will happily accept either format. But for maximum portability it is best to download the file in a way that causes it to be converted to the format native to your operating system. One way to accomplish this for Windows users is as follows:
Downloading the file without displaying it first will not cause the conversion of line endings to take place. Other browsers may not make the conversion. (Mac users, you're on your own here. You need yet a third convention.) It might seem tempting to rename the file to “.csv” while you're in the “Save As...” window. Don't do it. For some reason this causes the file to be converted to HTML!
The file on the server has a “.txt” extension to make the format conversion possible. Once the download is complete it is best to rename the file to end with “.csv” which more accurately reflects the type of data. The “.csv” extension will let you open it in more applications without having to answer as many questions.
If this scheme doesn't work for you and your downloaded file still needs its line endings converted, another solution is to get the free program flip, which will convert the downloaded file after the fact.
This field is used to specify both the amateur band on which the system operates and the use. It is defined as follows:
Output Frequency/Input Frequency:
These two fields show the output and input frequencies, in MHz, of the system. Where the system does not operate on split frequencies (i.e. packet or some "remote base" operations) only a single frequency appears. To figure the split, you'll have to do the math...
This field contains the standard 2-letter state abbreviation of the listed entry. Remember that this database contains some information relating to bordering states to allow for frequency use in these areas and how they impact Utah operations. Note that this database provides official coordination/repeater information only for UTAH listings!
This field contains the location of the repeater. This is may be the town/city closest to the system, or it may be the name of the actual site. The data in this field, while it may be significant to the frequency coordinator, may not be wholly useful to the user. Generally, the best-known local name for the location (or nearby city) is given. The "Site Name" field (see below) contains the name of the actual radio site (where known.)
This field contains the callsign used by the system in question for identification. This may not always be the callsign of the trustee.
This field may contain an abbreviation of the sponsoring group or club, the callsign of the trustee, or nothing at all (as in those cases where such information is unknown.)
This fields indicates the source of this data entry. In all cases here, it will be UVHFS.
This field indicates the general coverage area of this repeater. This data in this fields is very generic so that it may hopefully mean something to someone unfamiliar with the area. The data in this field, while it may be significant to the frequency coordinator, may not be wholly useful to the local user who may be more familiar with local place-names. A new field has been added that contains more user-relevant information (see the "Coverage Area" field below for more specific information.).
This is a boolean (Y/N) field. A "Y" indicates that this system is coordinated, "N" indicates that this system is not coordinated. If blank, assume "Y."
This is a boolean (Y/N) field. A "Y" indicates that this is an open system, available for all to use. Please note that "Open" doesn't necessarily mean that special repeater features such as an autopatch or linking system is also open as well. If blank, assume "Y."
This is a boolean (Y/N) field. A "Y" indicates that this is a closed system, available for the members only. If blank, assume "Y."
This is a boolean (Y/N) field. A "Y" indicates that this system has heavy multi-language use, or is open for multiple-languas use. If blank, assume "Y."
This is a boolean (Y/N) field. A "Y" indicates that this system is used for experimental or demonstration purposes. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this system supports a "Long-Tone Zero" emergency notification system. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that a subaudible (a.k.a. CTCSS) tone is used on this system. If blank, assume "N." See the "CTCSS_IN" and "CTCSS_OUT" fields below for overriding conditions.
This field contains the frequency of the subaudible tone(s) used for system access on the input. If this field contains a tone frequency, the "TONE" field (above) is ignored and always considered to be "Y" - no matter what it says.
This field contains the frequency of the subaudible tone(s) transmitted by the system. If this field contains a tone frequency, the "TONE" field (above) is ignored and always considered to be a "Y" - no matter what it says.
This is a boolean (Y/N) field. A "Y" indicates that this system requires a DCS (Digital Coded Squelch) code to be transmitted to access this system. If blank, assume "N."
This field contains the DCS access code. If this field contains a code, the "DCS" field (above) is ignored and always considered to be a "Y" - no matter what it says.
This is a boolean (Y/N) field. A "Y" indicates that some sort of DTMF sequence is required to access this system.
This is a boolean (Y/N) field. A "Y" indicates that this system has a "Remote Base" associated with it. Further details may appear in the "notes" column.
This is a boolean (Y/N) field. A "Y" indicates that this system resides on a repeater frequency pair that is coordinated, but is "Shared, Non-Protected." This means that other repeaters may be operational on this same frequency within the overlap area. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this system has an open autopatch available for all to use. Note: This field is ignored if the "Closed_Patch" field is "Y." If blank, assume "N."
This is the DTMF sequence required to access the autopatch, if such information is to be published. If this field contains information, then the "Autopatch" fields is ignored and assumed to be "Y."
This is a boolean (Y/N) field. A "Y" indicates that the autopatch on this system is closed to the general amateur population. Club membership and/or special permission is required for legitimate access of the autopatch on this system.
This is a boolean (Y/N) field. A "Y" indicates that this system has some sort of emergency power system. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this system is solar-powered and/or it has solar power as an emergency power source. If blank, assume "N." If this field is "Y" then the "Emerg_Power" fields is ignored and assumed to be "Y."
This is a boolean (Y/N) field. A "Y" indicates that this system is win-powered and/or it has wind power as an emergency power source. If blank, assume "N." If this field is "Y" then the "Emerg_Power" fields is ignored and assumed to be "Y."
This is a boolean (Y/N) field. A "Y" indicates that this system is links - at least the majority of the time - to another system(s.) If blank, assume "N."
This field contains frequencies to which this system is linked. If the UVHFS database, this may also include the name or acronym of a linked system. If this field contains information, the "Linked" field is ignored and assumed to by "Y."
This is a boolean (Y/N) field. A "Y" indicates that this repeater is used primarily for portable use and is usually not on the air. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this is a primary RACES system. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this is a primary ARES system. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this system has coverage that is significantly better than average. This would be due to its location atop a tall tower, on top of a mountain, or some other geographical property. If blank, assume "N."
This is a boolean (Y/N) field. A "Y" indicates that this system has direct access to law enforcement or emergency services. If blank, assume "N."
This field contains the DTMF sequence used for Law Enforcement access. Please note that the presence or lack of an autopatch (open or closed) does not necessarily mean that there is or is not law-enforcment access. Many system have autopatches, but have law-enforcement access blocked due to abuse. If this field contains information, the "Law" field is ignored and assumed to be "Y."
This is a boolean (Y/N) field. A "Y" indicates that there are provisions to access weather information on this system. If blank, assume "N."
This field contains the DTMF sequence to access weather information. If this field contains information, the "Weather" field is ignored and assumed to be "Y."
This field contains the Latitude of the
system's transmitter in decimal
degrees. Note that south latitude values are negative!
datum is recommended.)
All North-American coordinates will be positive.
This field contains the Longitude of the
system's transmitter in decimal
degrees. Note that west latitude values are negative!
datum is recommended.)
All North-American coordinates will be negative!
Note: The following fields are extensions to those in the ARRL format.
This is a boolean (Y/N) field. A "Y" indicates that there is an internet link to this system. If blank, assume "N."
This field contains information on which
internet system (e.g. IRLP
or Echolink) is connected to this system, along with the node
if known. If this field contains information, the
is ignored and assumed to be "Y."
This field formerly contained information about whether this repeater is open or not, subaudible tones, autopatch, and link information. This field may still contain such information as the conversion to the current format progresses. For the most part, this information is redundant and is contained in the previous fields. However, information that does not fit into existing fields may be placed here, such as HF gateway information, etc.
A brief explanation of some of the older abbreviations that had been used on this list in the NOTES column:
This field contains the date of the last modification to this entry. This is in MM/DD/YYYY format.
This field contains the date on which this system was originally coordinated. This is in MM/DD/YYYY format.
This field specifies the use of the coordinated frequency. The following list includes some entries that may not show up in the data owing to their nature (i.e. link frequencies, etc.):
This field is a remnant from the older format. Because current records are maintained in Degree-Minute-Seconds format, this field is used and converted to the decimal Degrees in the "Latitude" and "Longitude" fields above on the fly.
Where known, this field contains the Latitude and Longitude of the site. These are in DDMMSS format for latitude or DDDMMSS format for longitude. For example, coordinates of 40 deg, 17' 23" N by 112 deg, 29' 36" W would be written as 401723 and 1122936.
It is worth noting that Latitude is ALWAYS assumed to be North and Longitude is ALWAYS assumed to be West.
Where known, this field contains the altitude of the site Above Mean Sea Level in feet.
Where known, this is the transmit power, in watts, as measured at the antenna.
This is a free-form text field containing a brief description of the antenna, where known.
Where known, this field contains the Effective Radiated power in watts of the transmit system based on an Isotropic radiator.
By definition, all entries in this file will
contain a "Y" indicating
that the data is to be publicly available.
This field contains information pertaining to the state of the repeater as follows. Note that the status "T" and "P" aren't officially recognized in the ARRL format.:
This field contains the actual name of the
this refers to a mountain peak or particular radio site, the
name of which
may be familiar only to local residents or those maintaining the
This field contains abbreviations referring to the coverage area of a repeater. This list of abbreviations will continue to grow as more information is gathered. Someone using this data may refer to it in table or it may be used to highlight areas of a map to illustrate coverage. It is recommended that, if using this data in a tabular format to describe repeater coverage, that more complete descriptions are given for each coverage area. The descriptions below are intended primarily for one who is already familiar these coverage area. If there are any questions concerning the various attributes of (a) specific coverage area(s) then please send email to the address at the bottom of the page.
Notice that multiple coverage areas may be listed for a given repeater: As an example, the 146.62 repeater on Farnsworth Peak not only has a WF (Wasatch Front) coverage designation, but a TV (Tooele Valley) and an I80W (I-80 Western Corridor) designation as well, since it provides reasonable coverage these areas. When multiple coverage areas are given, they are delimited by a forward slash (/).
These coverage areas are based on known geographical coverage areas of existing systems and the limits of those various systems due to surrounding terrain. For example, it is known that a particular repeater in the NWF area (Northern Wasatch Front) does not cover well into the SLC area, and thus there are two distinct areas. Note, however, that some other areas such as WF (Wasatch Front) include numerous smaller coverage areas. These distinctions are done to better detail the actual coverage areas of a particular repeater. Note that there is has been an attempt to balance usefully-detailed information against overwhelming the user with too much detail and providing uselessly generalized data. It will no doubt be noticed that those areas with higher population density are the same ones with more coverage details (namely the Wasatch Front and its sub-areas.)
These coverage areas are those areas that, with an average mobile or home installation (e.g. up to 50 watts and a roof-mounted ground-plane) users can expect reliable coverage of the system. This does not include those area for which there may be known "hot spots" (i.e. coverage of the 146.94 repeater on Frisco Peak into Utah County, or the spotty coverage of the Logan repeaters in to the Salt Lake valley.) Handie-Talkie coverage coverage will comprise much smaller areas, of course.
The list of repeaters is continuously being updated. At the moment, not all repeaters have been classified as to their coverage area using this new "system". When this field was created, data was simply copied from the "Area" field (see above) and as it is being revised the new abbreviations below are used. Note: All of the new abbreviations are UPPERCASE while the old abbreviations and designations are a mixture of upper and lower case.
These abbreviations are defined as below. They are grouped according to their respective MapSel values (see the definition of this field farther down this page for more information) :
The following coverage areas are used to denote, in a very general way, their coverage area. No coverage maps are defined but these areas may be covered by overlap of one or more of the above areas.
(Additional abbreviations will be added as necessary)
This field contains numeric footnotes that explain certain attributes of the repeater/system. The letter "O" (Oh) is not used, as it could be confused with a 0 (zero.) These footnotes are defined as follows:
A - This repeater is part of the Intermountain Intertie (a.k.a. the Snowbird Link System.)
B - This repeater is part of the Sinbad Desert Amateur Radio Club system.
C - This repeater does may require a subaudible tone for access. Repeaters in this category are often run with no tone access, as conditions permit. This repeater does transmit the indicated tone and the user may program his/her tone squelch to use it.
D - These frequencies are available as Test Pairs and are intended for use on a temporary basis to test the suitability of a particular site, equipment, and/or for special events. Coordination and the use of a subaudible tone is required for use. These frequencies are shared and no protection from interference is afforded. The coordinated use of tone access is intended to help mitigate any interference issues.
E - This is for a portable repeater which may be operational at different times and locations as needed for special events or emergency situations.
F - The 146.62 Farnsworth repeater and the 146.62 Scott's Hill repeater are to be synchronously linked together to expand coverage of the system. These two repeaters together will function as a single repeater.
G - Note that this repeater has a -600 KHz offset.
H - Note that this repeater has a split direction that is reversed from standard.
I - This repeater is part of the Deseret Amateur Radio Society (DARS) a group affiliated with the Cactus intertie. This is a closed system. For more information on this system contact the Frequency Coordinator.
J - This is a "closed" repeater. For more information, refer to the trustee or the contact person.
K - This repeater, while normally linked into the system, may be unlinked at times to reduce local traffic and/or to conserve power. For more information, contact the person/group that operates it.
L - This repeater is linked to the WA6HXO (Las Vegas) group.
M - This repeater is affiliated with the Utah VHF Society.
(Additional footnote designations are reserved)
This field contains the email address of the "contact person" for the repeater/system, if such information is available.
This field contains the URL of a web page with information about the repeater/system/site, if such information is available.
When displaying an interactive coverage area map, this field indicates which "base" map to use for the coverage overlays - see the "Coverage Area" field, above. There are several maps in order to permit a reasonable level of detail for the various coverage areas. These maps also include a certain amount of overlap to adjacent areas as deemed appropriate. The general mapping areas are defined as follows:
This field contains telephone numbers for contacting the repeater owners. This field may be blank either due to lack of information, or if the contact person(s) do not choose to have their numbers published.
This field indicates the source of the data for the most recent update (noted in the Date of Last Update field.) This will often be just a name or callsign. For "minor" updates (i.e. that do not require re-coordination, etc.) a "reliable" second source is acceptable. For "major" changes (i.e. change of ownership, site move, etc.) direct contact with the owner/trustee is required.
This field contains miscellaneous notes pertaining to some aspect of of the system. These may have something to do with an operational aspect or pertaining to when a repeater is expected to be on the air (or back on...)
This field contains postal mail address for
the system's owner or other contact person.
END OF FIELD DEFINITION.
PLEASE NOTE that additional fields may be added in the future. Where possible, additional fields will be included in additional columns beyond the last field defined above.
If you are designing a system to import
this data, please make allowances for the possible existence
of these (possible) extra fields so that their addition does
not "break" your code! In other words, don't blame us
for your poorly-designed software!
The "raw" data file contains all repeaters - including "paper" repeaters. If you want your list to be accurate, you must process the list looking at the active state field (the 19th field - described above) and remove all entries that are inactive!
Failure to do this will result in your having a bloated list that does not accurately reflect what is actually on the air!
It is the recommendation of the Utah VHF society that only those entries with a "Y" in the active state field indicating that they are believed to be on the air and active to be put on an online list. If you are producing a printed list, you may wish to also include those with a "T" which indicates those that are temporarily off air, but are expected to return soon.
Repeaters with a "P" or "U" or "N" status should not be listed in any presented in a printed or online directory in a manner that may be possibly result with them as being construed as being on the air!
Those repeaters marked with "N" are typically those that have been proposed - but never built, or have left the air and are not expected to return. They are retained in the raw database solely for reference purposes. Repeaters in this listing that appear with an "N" may also include those that have lost their coordination due to inactivity or official notification by the trustee.
As of early 2004 the ARRL's "internal" format for maintaining repeater records was dramatically changed. In particular, the older "notes" field has been broken into individual boolean and data fields to improve handling and sorting capability. The Utah VHF Society has adopted a modified version of this format in early 2004.
Now (the moment you've been waiting for), here is the link to the raw file:
This page last updated on 20170213
Questions, updates, or comments pertaining to this web page may be directed to: firstname.lastname@example.org
Return to the UVHFS Repeater
list or the Utah VHF