About the NETSdb Project
The NETSdb is a project that came to mind one morning when I was talking to someone on a local repeater. He had mentioned something about one of the local nets, and the idea came to me. I haven’t seen any sort of database of Amateur Radio Nets, so why not create one? The information I've been able to find on nets has been scattered all over the place. A centralized location, a database, seemed like a good idea.
So, here we are. What you see here is version 0.1a, the very first version. As an alpha version, there are a lot of things that are not yet functional, or even implemnted, and a lot of things that aren’t working quite as expected, but as a proof–of–concept, I think it will do just fine. And if there is sufficient interest in the project, I will continue it, perhaps giving it it’s own domain. If there isn't sufficient interest in it, I will probably continue to develop it anyway, just for my own use, I’m just that way.
If you like the idea of NETSdb, please send me an email at <my callsign>@amsat.org and let me know. I’d love to hear from you. Or, you can just catch me on the air and let me know.
How to Use NETSdb
I’m trying to make NETSdb as simple and straight–forward as possible. So, hopefully, there shouldn’t be a need for very much in the way of a “how to use this site” type of thing. That being said, there are a few items, mostly related to terminology, that I should probably address.
- Net Name
- Should be pretty self–explanitory. What is the name of the net?
- Another easy one. What band does the net occur on?
- What is the frequency, in MHz, that the net usually occur on? I realize that if a frequency is already in use at the time of the net, that the net may need to QSY, but info about that can be left in the Comments section of the net listing.
- Yet another self–explanitory one.
- What day of the week does the net occur on? For nets that occur on multiple different days, I am requiring a seperate entry for each day. I’m thinking ahead on this one. I have future plans that will be easier to implement if I do things this way from the start.
- The time the net starts, in 24-hour format.
- Time Zone
- Another simple one. What time zone is associated with the start time for the net? I’m thinking about requiring UTC.
- This one is actually pretty straight–forward. Daylight Savings Time. Does the primary location of the listed net observe DST? Here in Arizona, at least most of the state, does not. And I think that there are a few other areas around the world that don’t observe it either. Good to know if you want to join the net ontime.
- Quite simply, how often does this particular net occur? Is it a monthly or weekly net, or does it only occur as needed, say a severe weather net?
- Is the net active? Has it been suspended? Has it been cancelled?
- Is the net open for any licensed Amatuer Radio Operator to join, or is it a closed net?
- Primary Location
- I’m still trying to finalize the term I want to use for this. It’s an especially difficult one to pin down do to the very nature of Amateur Radio. I’m thinking about the primary location/region/locale/coverage area of the net. If it's HF it could very well be an entire state, country, continent, or even, the entire world. if propagation allows. If the net is on VHF/UHF/SHF, etc., it will most likely be a very much smaller coverage area. Unless it is on a linked repeater system, then we're back to HF type coverage areas. See what I mean about trying to nail this one down? Just be aware that this term is likely to change, but I think you get the idea behind it.
- What are the usual topics covered by the net? Severe weather observations? Emergency Communications? Is it a club net? Genreal discussion?
- Who is this net’s sponsor? This also contains a link to get more information about either the net or the net sponsor.
- Additional information for the net. Things such as what to do if the frequency is busy, projected return time if the net is suspended, information that doesn’t already have a spot in the listing.
It’s not obvious just yet, but you can sort the listing by clicking on the column name. I still need to do a bit of work on the sorting, but the basic functionality is there. You can only sort on one column, but it’s a start.