Rules for entering data into this database

Thank you for taking the time to add your digital station information to our database. We want to take this opportunity to ensure that the data you enter conforms to the proper format. Below, we will go ever each field that the database uses, and describe what information is valid for the field, and what information is considered incorrect. Most fields are self-explanatory. But, some fields do require you to have a little understanding of what we are looking for.


As a general rule, most data (not all) pertains to the digital equipment, and not the sysop.


Special note for stations that use multiple frequencies. Please make a separate entry for every frequency your station uses. So, if you’re a BBS and you have three total frequencies, then you should have three total entries for that BBS.



This field is a drop down menu. All you have to do is select what category your station is.



Sysop First Name

Self-explanatory – Required field.



Sysop Last Name

Self-explanatory – Required field.



Sysop Email Address

Self-explanatory – Required field.



Node Call

In this field, you enter the callsign, and SSID (if any) of what your station answers to over the air. For an example, my BBS answers to KG6BAJ-1. So my NODE CALL would be exactly that. If I did not use an SSID, then my NODE CALL would be just KG6BAJ. Please enter the callsign in CAPITALS.

This is a required field.



Node Alias

In this field you enter any ALIAS that your station uses (if any). Some stations use multiple frequencies, and some of those frequencies answer to an ALIAS and some of those frequencies do not use an ALIAS. Make sure you enter the station ALIAS for each frequency that actually uses it. Please enter any ALIAS in CAPITALS. Some stations do not use an ALIAS at all. They only answer to just the node call. In any record you enter where your station does NOT use an ALIAS, please just enter a HYPHEN. A hyphen is the preferred way of indicating that your station does not use this feature, while telling everyone that you just didn’t forget to enter something.

This is a required field.




While most would think this is self-explanatory, I have seen different. First, please remember that only one frequency per record. If you use more than one frequency, you need more than one record. As for the format, the trailing digits after the decimal point should be at least three characters long. My BBS is on “145.090”.  Not “145.09”.   If your station were on a frequency that ended in all zeros, then it better show all three zeros after the decimal point. An entry of  “145” is incorrect. An entry of “145.000” is correct. Knowing this rule means others will find your record faster during a search of the database. If a (very rare) circumstance were to occur where your station were to have four digits after the decimal point, then please enter all four digits.

This is a required field.



Baud Rate

Self-explanatory – Required field.



Digi Call

Some stations can act as a “digi-peater” and chose to turn on this feature. Some stations either don’t have the capability to digipeat, or just chose not to. If your station has this ability, and you chose to activate it, then in this field, you enter the callsign, and any SSID (if any) of what your stations “digi” answers too over the air. For an example, my keyboard only node on Wolf Mountain uses a Digi Call of N1OES-1. So my DIGI CALL would be exactly that. Again, if I did not use an SSID, then my DIGI CALL would be just N1OES. Please enter any DIGI CALL in CAPITALS. If your station does not use a DIGI CALL, then please enter a HYPHEN in this field.

This is a required field.



Digi Alias

Stations that do activate the digipeat feature may also have the ability to use a “Digi-Alias” as well. This works very much the same as the NODE ALIAS does. If your station does use a DIGI ALIAS, then please enter it in this field. Please enter any DIGI ALIAS in CAPITALS. If your station does not use a DIGI ALIAS, then please enter a HYPHEN in this field.

This is a required field.



Transmitter Location

In this field, please enter the location of where your station transmitter is located. Please do not enter your home city if your station in located somewhere else. Some stations are located at the sysops home, while other stations are located, say, on a hilltop. If your station is located on top of a mountain that has a commonly referred to geographical name, then please use it. For example, I have the GVCITY node here at my house, and it is located inside the city of Grass Valley. So my transmitter location would be entered as “Grass Valley”. Now, I also have a keyboard node located on Wolf Mountain, just south of Grass Valley. For this node the transmitter location is entered as “Wolf Mountain”.

This is a required field.




Please select the county that your transmitter is located in.

This is a required field.



TNC Mailbox Call

Some stations use TNC’s that have a built-in mailbox for message storage capabilities. (If you are a ‘MAILDROP-ONLY’ station, then this is where you would enter the callsign or alias of the mailbox.) A common practice is for packet radio operators at home to use theses types of TNC’s so their friends can leave messages for them if they are not home, or maybe not sitting at the keyboard when someone tries to reach them. Some stations in remote areas also use this feature as well. Some mobile packet stations use this feature in their vehicles too. If you use this feature, please enter your TNC’s Mailbox callsign and SSID (if any). Please enter the Callsign in CAPITALS. If you do not use this feature, please enter a HYPHEN.

This is a required field



Lat/Lon (APRS Format)

Please enter the Latitude and Longitude of your transmitter location. Please use the APRS format of latitude/longitude. While, at this time, we do not use this data to broadcast the location of your station, there could, at some point in the future, be a feature added to allow you to ‘opt-in’ to have this data broadcast once every 24 hours so your station appears on the global APRS maps. This future feature is still a long way off. The format is "ddmm.hhN/dddmm.hhW" without the quotation marks, where d is degrees, m is minutes and h is hundredths of minutes. The first eight characters represent latitude (north in this case), and the last nine characters represent longitude (west in this case). If you are not sure of your Lat/Lon, you can easily search Yahoo and Google for Latitude Longitude Maps, and zoom in on your station location to determine your settings to enter into the database.

This is a required field



AMPR 44 IP Address

If you have an assigned AMPR.ORG 44.x.x.x IP Address, then please enter the address in ‘dotted-form’. In my case, my GVCITY node is connected to the AMPR network, and the address is Please do not enter the ‘Domain Name’. Please use the IP Address. If you do not use a 44.x.x.x address, then please enter a HYPHEN.

This is a required field.



Coordination Status

This field is designed for use with BBS and DX Spotting stations in mind. Currently they are the only two categories that show a Coordination Status. In this field, you can only enter "n/a". If your station is either a Coordinated or Uncoordinated station, please email the Database Manager and have the Coordinated or Uncoordinated flag set. If your station does not qualify for this status, then the Database Manager will set the flag to ‘n/a’ for your record.

This is a required field



Please feel free to enter any web address (URL) that you would like other users to know about, to find out more information on your station. (Or your stations club website)

This field is not required




Please enter any additional comments you feel are important for users to see. If your station is affiliated with ARES, or RACES, that would be good information to include here. If your station has AXIP or UDP connectivity, or maybe you are a BBS that will forward to home TNC stations, those are also good things to include here. Include anything you feel is important.



If you have any further questions, please feel free to contact the database manager.



Copyright © 2010 - , Northern California Packet Association