Re: Repeater Maintenance Window

GTGallop - N5MKH Arizona Admin

#101

Exactly, Tom. And in AZ, we have been trying to make as many people (that we can legitimately verify) custodians of their repeaters.
Repeater Owners (repeater has the same call sign) get 180 months or 15 years
If it's a club officer, they get 1 year
Trustee's or board of directors for clubs (kinda rare) get 5 years.

The chief complaint I hear about RepeaterBook is that it's not accurate. But I find that while not perfect, it is far more accurate than any of the other resources out there. The fact that it is crowd sourced data is both the strength and the down fall. So to mitigate the downfall part, I like to get as many people involved and invested as possible.

So if someone has credentials on the RepeaterBook platform and has been validated by an admin as a custodian, then it makes sense to lay an increasing role on them to update their repeater.

Re: Repeater Maintenance Window

Tom Brew - Pennsylvania Admin

#100

What a great idea. Thank you for all you do to keep the system fresh.

Tom K3WS

Show quoted text

On Sep 15, 2018, at 11:41 AM, Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...> wrote:

Message received. I don’t have time to program it this weekend, but it wouldn’t take all that long to do.

There is a quick “on-air” “off-air” link available, but it doesn’t allow for a comment. I think I can leverage that to allow the user to add a quick comment at the same time.

Garrett

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> On Behalf Of Tom Brew - Pennsylvania Admin
Sent: Tuesday, September 11, 2018 6:20 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] Repeater Maintenance Window

I think it is a great idea. Security is the fact the registered user is verified by their log in.
Tom K3WS

On Sep 11, 2018, at 9:05 AM, GTGallop - KG7NDC Arizona Admin via Groups.Io <Greg.Gallop@...> wrote:
Was wondering about - for future enhancement - adding a maintenance window to the platform? Repeater Owners / Custodians could log on and set a maintenance window if they know their repeater will be off line for a day to a month.

Example, Today is Sept 11 and I know I'm taking my repeater off line next weekend for 48 hours.
I enter the window today and it appends a note to the repeater and sends out a tweet.
Then when the weekend gets here, it updates the status on the repeater to On Air / Maintenance or maybe just Maintenance and sends a tweet
Then when that period expires or sooner if I log in and change it, the repeater status reverts back to On-Air and sends a tweet that the maintenance window has been complete and the repeater has returned to duty.

Maybe put some limits out there.
Maintenance can't be scheduled more than 60 days out.
Maintenance can't last longer than 30 days (if so the repeater is in testing or off air).

Thoughts?
Likes?
Dislikes?
Comments?

Re: Repeater Maintenance Window

Garrett Dow - Site Admin/Owner (KD6KPC)

#99

Message received. I don’t have time to program it this weekend, but it wouldn’t take all that long to do.

There is a quick “on-air” “off-air” link available, but it doesn’t allow for a comment. I think I can leverage that to allow the user to add a quick comment at the same time.

Garrett

Show quoted text

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> On Behalf Of Tom Brew - Pennsylvania Admin
Sent: Tuesday, September 11, 2018 6:20 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] Repeater Maintenance Window

I think it is a great idea. Security is the fact the registered user is verified by their log in.

Tom K3WS

On Sep 11, 2018, at 9:05 AM, GTGallop - KG7NDC Arizona Admin via Groups.Io <Greg.Gallop@...> wrote:

Was wondering about - for future enhancement - adding a maintenance window to the platform? Repeater Owners / Custodians could log on and set a maintenance window if they know their repeater will be off line for a day to a month.

Example, Today is Sept 11 and I know I'm taking my repeater off line next weekend for 48 hours.
I enter the window today and it appends a note to the repeater and sends out a tweet.
Then when the weekend gets here, it updates the status on the repeater to On Air / Maintenance or maybe just Maintenance and sends a tweet
Then when that period expires or sooner if I log in and change it, the repeater status reverts back to On-Air and sends a tweet that the maintenance window has been complete and the repeater has returned to duty.

Maybe put some limits out there.
Maintenance can't be scheduled more than 60 days out.
Maintenance can't last longer than 30 days (if so the repeater is in testing or off air).

Thoughts?
Likes?
Dislikes?
Comments?

Re: Repeater Maintenance Window

Tom Brew - Pennsylvania Admin

#98

I think it is a great idea. Security is the fact the registered user is verified by their log in.

Tom K3WS

Show quoted text

On Sep 11, 2018, at 9:05 AM, GTGallop - KG7NDC Arizona Admin via Groups.Io <Greg.Gallop@...> wrote:

Was wondering about - for future enhancement - adding a maintenance window to the platform? Repeater Owners / Custodians could log on and set a maintenance window if they know their repeater will be off line for a day to a month.

Example, Today is Sept 11 and I know I'm taking my repeater off line next weekend for 48 hours.
I enter the window today and it appends a note to the repeater and sends out a tweet.
Then when the weekend gets here, it updates the status on the repeater to On Air / Maintenance or maybe just Maintenance and sends a tweet
Then when that period expires or sooner if I log in and change it, the repeater status reverts back to On-Air and sends a tweet that the maintenance window has been complete and the repeater has returned to duty.

Maybe put some limits out there.
Maintenance can't be scheduled more than 60 days out.
Maintenance can't last longer than 30 days (if so the repeater is in testing or off air).

Thoughts?
Likes?
Dislikes?
Comments?

Repeater Maintenance Window

GTGallop - N5MKH Arizona Admin

#97

Was wondering about - for future enhancement - adding a maintenance window to the platform? Repeater Owners / Custodians could log on and set a maintenance window if they know their repeater will be off line for a day to a month.

Example, Today is Sept 11 and I know I'm taking my repeater off line next weekend for 48 hours.
I enter the window today and it appends a note to the repeater and sends out a tweet.
Then when the weekend gets here, it updates the status on the repeater to On Air / Maintenance or maybe just Maintenance and sends a tweet
Then when that period expires or sooner if I log in and change it, the repeater status reverts back to On-Air and sends a tweet that the maintenance window has been complete and the repeater has returned to duty.

Maybe put some limits out there.
Maintenance can't be scheduled more than 60 days out.
Maintenance can't last longer than 30 days (if so the repeater is in testing or off air).

Thoughts?
Likes?
Dislikes?
Comments?

Repeaterbook.com - Blog - Repeater Database #feed

repeaterbook@repeaterbook.groups.io Integration <repeaterbook@...>

#96

Repeater Database

The repeater database is separated into two categories:

North America: This area includes the USA (including the US territories of Puerto Rico, Guan, and American Samoa), Canada, and Mexico.

Rest of World: This area includes all other countries and territories not covered under North America above.

The Repeater Subscriptions menu item leads to the Repeater Change Notification System.

Annually, Repeaterbook.com processes more than 18,000 repeater adds, edits, and deletes. That's a lot of change, and you want to know when these changes happen, so you can keep your radio programming current. What good is a memory in your radio if it tries to key up a dead repeater? What if the CTCSS code changed? And you certainly don't want to miss that new repeater that just went operational. You could memorize our database (40,000 repeaters) and then check back every so often to see what changed, or, you can let us just shoot you an email and let you know when it happens.

What is the Repeater Change Subscription System? This is the module we built to notify you when there is a repeater add, edit, or delete. You can subscribe to an entire state or province, and if you are tracking repeaters in the United States, you can even track down to the county level. We will let you filter down the results to a specific band (do you want to know about the 1.25 meter and 6 meter changes if you don't own those radios?) or even a specific operating mode. Maybe you have a DMR radio and you want to know when a new DMR repeater pops up in an area.

How often will I get an email? Every Monday morning, we will send you a single notification about any repeaters that were updated during the last 7 days. No matter how many areas you sign up for, you will receive a single email. Depending on how many updates there were, it could be long or short. If you feel you no longer need the emails, there is an option to delete your subscription here on this page, or from the email itself. You have full control of the areas you subscribe to.

What types of changes do you report? All changes! The way we compile the list is to look at the date the repeater was added or last updated. This update date cannot be manipulated, so whenever an admin submits the add or changes, the date is set by the server. We search for all repeaters with an update within the last 7 days, and if it matches one that you subscribed to, we let you know. Not all updates have a meaningful change, or in other words, a change that affects the operation of the repeater. It may have been a minor grammar adjustment or an admin just researching the repeater and updating that it is still operational. We apologize if that confuses anyone, but we wanted to make sure you were notified any time someone touches the repeater record.

How can I help? Now that you have received information from the site, we hope that you will be inspired to give a little. We depend on users like you to help us keep our database as up-to-date as possible. You might think that there was a national database or legal requirements to report repeater information, but there isn't! This all has to be gathered up and curated. We do all of this for you for free! If you find that there are any errors in the repeaters, please let us know right away.

Who can use the module? Anyone with a Repeaterbook.com account can use the module. Currently, the module is only available for countries in North America. We will be adding the rest of the world and the ability to subscribe to a location and search radius in the future.

A note about the Proximity Subscription Service The search radius is not a true circle, but rather a square. A box is drawn around the centerpoint of the location to the north, south, east, and west. This means the distance into the corners is slight further and may result in some results outside the intended radius. Also, the Google Maps API is used to geolocate your subscribed location. The service can only return results if it is able to determine a latitide and longitude from the location you entered.

What is geocoding? Geocoding is the process of converting addresses (like "1600 Amphitheatre Parkway, Mountain View, CA") into geographic coordinates (like latitude 37.423021 and longitude -122.083739).

Repeaterbook Wiki - RT Systems - [Background] #feed

repeaterbook@repeaterbook.groups.io Integration <repeaterbook@...>

#95

RT Systems - [Background]

By kd6kpc@... (kd6kpc)

RT Systems

RT Systems Radio Programming Software

Background

Repeaterbook and RT systems entered into a partnership several years ago to open an API for importing Repeaterbook data directly into the RT Systems app. This means that anyone who owns a copy of the RT Systems software can choose parameters and import data directly into programming software.

There is no subscription required to access the Repeaterbook data from the software. The data import is absolutely free.

Alternatively, owners of RT Systems software can also conduct searches on the Repeaterbook.com website and export the search results into a file compatible with importing into the RT Systems programming software, regardless of the radio the application was intended for. Some users may require more advanced or customized search options that can only be conducted on the Repeaterbook.com website. This does require an intermediate step to save the file to your computer and then import it into the RT Systems application but improves flexibility.

Importing Directly into RT Systems

Open the RT Systems Programming Software
Click File » External Data » RepeaterBook Search
In the location field, enter the center of the area to be searched. You can use a city and state, a city and country, a landmark, or a zip code. The program will use the Google Geocoding API to determine the coordinates for your queried location.
Enter the radius to search
Select the desired bands
Click OK

The search results will open in a new tab. You can edit the list as you desire before writing the data to your radio. You can even use the copy commands to place some entries into another tab and create a more customized list or to add channels to an existing list. Please refer to the RT Systems documentation available with the software for more information.

Exporting from Repeaterbook

Repeaterbook.com offers many more search options than what is currently offered within the RT Systems software. If you don't mind a little more work an effort, you may be able to produce a more customized list of channels to write to your radio.

To produce an export file, you must first conduct a search for repeaters on Repeaterbook.com. The following searches currently offer the option to export the results in an RT Systems file format:

Quick Search
Advanced State Search (multi-state with filtering)
County Search (multi-county with filtering)
Travel Search
Proximity Search
Free Text Search
Call Sign Search

Once you save the file to your computer, open the RT Systems Radio Programming software and follow these steps:

Click File » Import
Choose the file on your computer and click Open

The repeater channels will display in a new tab within the RT Systems software.

Google Earth Export

Garrett Dow - Site Admin/Owner (KD6KPC)

#94

We have just added the Google Earth format (KML) export from the Feature Search page.

Garrett, KD6KPC

New to Group

DrZ1953

#93

Hello, I am new to the group.

Albert Zodun

Re: Google Maps API

KG4Y - Mike Wolff Virginia Admin

#92

I'm not sure how easy or difficult it is to integrate open street maps, or how well it fits what we are trying to achieve, but I know other sites use it - aprs.fi comes to mind... I wish I could be more help than simply suggesting an alternative, because I know that using something else likely means code changes at some level or another.

73,

Mike - KG4Y

Re: Google Maps API

Clayton Lowther <clowther@...>

#91

Garrett,

Not sure how it would work out but give open street maps a go!

Show quoted text

On May 3, 2018, at 4:07 PM, Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...> wrote:

Google has sent me a notification that they now intend to charge steep fees for using their mapping API on the website. It is estimated that the mapping fees alone on the Repeaterbook website could exceed $500 per month. To combat this, I have removed the automatic display of a Google Map from the Repeater Detail page, but have added a link to the menu bar to allow you to still view the location, coverage circle, and any propagation reports as needed. I will watch the usage meters to see if this measure alone gets us to an acceptable level.

I am looking at open source maps as another alternative and will likely be deploying this in some other areas of the site to further reduce the Google calls.

Thank you for your understanding as we continue to seek to make Repeaterbook the best free online source of ham radio repeater data.

73,

Garrett, KD6KPC

Re: Google Maps API

Eric H. Christensen

#90

You might take a look at Mapbox for a quick, easy way to deploy a mapping solution.

Eric

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Show quoted text

On May 3, 2018 6:07 PM, Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...> wrote:

Google has sent me a notification that they now intend to charge steep fees for using their mapping API on the website. It is estimated that the mapping fees alone on the Repeaterbook website could exceed $500 per month. To combat this, I have removed the automatic display of a Google Map from the Repeater Detail page, but have added a link to the menu bar to allow you to still view the location, coverage circle, and any propagation reports as needed. I will watch the usage meters to see if this measure alone gets us to an acceptable level.

I am looking at open source maps as another alternative and will likely be deploying this in some other areas of the site to further reduce the Google calls.

Thank you for your understanding as we continue to seek to make Repeaterbook the best free online source of ham radio repeater data.

73,

Garrett, KD6KPC

Re: Google Maps API

SRG

#89

Hi Garrett,

Nice thoughts. I just use ACME mapper for any of my needs so either way is good for me.

Regards,

Karl Shoemaker

Show quoted text

On Thu, May 3, 2018 at 2:07 PM, Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...> wrote:

Google has sent me a notification that they now intend to charge steep fees for using their mapping API on the website. It is estimated that the mapping fees alone on the Repeaterbook website could exceed $500 per month. To combat this, I have removed the automatic display of a Google Map from the Repeater Detail page, but have added a link to the menu bar to allow you to still view the location, coverage circle, and any propagation reports as needed. I will watch the usage meters to see if this measure alone gets us to an acceptable level.

I am looking at open source maps as another alternative and will likely be deploying this in some other areas of the site to further reduce the Google calls.

Thank you for your understanding as we continue to seek to make Repeaterbook the best free online source of ham radio repeater data.

73,

Garrett, KD6KPC

--

For current information please visit:
http://www.srgclub.org

Google Maps API

Garrett Dow - Site Admin/Owner (KD6KPC)

#88

Google has sent me a notification that they now intend to charge steep fees for using their mapping API on the website. It is estimated that the mapping fees alone on the Repeaterbook website could exceed $500 per month. To combat this, I have removed the automatic display of a Google Map from the Repeater Detail page, but have added a link to the menu bar to allow you to still view the location, coverage circle, and any propagation reports as needed. I will watch the usage meters to see if this measure alone gets us to an acceptable level.

I am looking at open source maps as another alternative and will likely be deploying this in some other areas of the site to further reduce the Google calls.

Thank you for your understanding as we continue to seek to make Repeaterbook the best free online source of ham radio repeater data.

73,

Garrett, KD6KPC

Re: # P25 Talkgroups for MMDVM/Pi-Star #

Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...>

#87

Hi all
I have been working on a full Talk group list for MMDVM/Pi-Star users. Please take a look and let me know if anything need fixing or adding.

https://docs.google.com/spreadsheets/d/1qFERnf8zwU4VXdwgR4xNKehHHp9MBCdLMq6o1kGKDbI/edit?usp=sharing

P25 Talkgroups for MMDVM

docs.google.com

P25 TalkGroup Alias, TalkGroup ID#, Reflector IP, Port, Dashboard, NOTE Local Repeater, 1, Not in pi-star VK4P25, 4, http:// p25. duckdns. org/ p25. html, Not in pi-star Canada, 302, http:// p25canada. hopto. org/ p25canada/ index. html, Not in pi-star San Diego USA, 858, http:// nz6d. dx40...

Thanks

Michael W. Andrescavage Sr

N2ICV

n2icv@...

Show quoted text

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Tuesday, May 1, 2018 10:36 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] #NXDN

Sure. Where can I get the list and I can update right away.

Regards,

-Garrett

On May 1, 2018, at 05:41, Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...> wrote:

Can we please get a updated list? Pi-Star was updated with 13 tg's and most dont have "NAMES" just ip's.

Re: #NXDN #nxdn

Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...>

#86

I was asking ve3wzw.

Michael W. Andrescavage Sr

N2ICV

n2icv@...

Show quoted text

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Tuesday, May 1, 2018 10:36 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] #NXDN

Sure. Where can I get the list and I can update right away.

Regards,

-Garrett

On May 1, 2018, at 05:41, Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...> wrote:

Can we please get a updated list? Pi-Star was updated with 13 tg's and most dont have "NAMES" just ip's.

Re: #NXDN #nxdn

Garrett Dow - Site Admin/Owner (KD6KPC)

#85

Sure. Where can I get the list and I can update right away.

Regards,

-Garrett

Show quoted text

On May 1, 2018, at 05:41, Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...> wrote:

Can we please get a updated list? Pi-Star was updated with 13 tg's and most dont have "NAMES" just ip's.

Re: #NXDN #nxdn

Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...>

#84

Can we please get a updated list? Pi-Star was updated with 13 tg's and most dont have "NAMES" just ip's.

Re: P25 subgroup created

Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...>

#83

what????

*31672*	*31672 Pi-Star Chat*	*<--- Kill this line.*
31672	Pi-Star chat	*P25 only, not linked to BM - DMR TG 31672. (YET)

Michael W. Andrescavage Sr

N2ICV

n2icv@...

Show quoted text

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Tuesday, April 17, 2018 12:01 PM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

https://www.repeaterbook.com/p25_info/all_talk_groups.php

Regards,

-Garrett

On Apr 17, 2018, at 08:27, Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...> wrote:

Welcome to the Area

Find specialized searches and information for -equipped repeaters.

Fatal error: Call to a member function fetch() on null in /home/nwham123/public_html/repeaters/niche/index.php on line 400

Newest 25 Repeaters
Click a row to view the repeater

Michael W. Andrescavage Sr

N2ICV

n2icv@...

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Tuesday, April 17, 2018 11:10 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

Sorry, I had to change the URL:

https://www.repeaterbook.com/p25_info/all_talk_groups.php

Garrett

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> On Behalf Of Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager
Sent: Tuesday, April 17, 2018 4:17 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

Fatal error: Call to a member function fetch() on null in /home/nwham123/public_html/repeaters/niche/index.php on line 400

Michael W. Andrescavage Sr

N2ICV

n2icv@...

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Sunday, April 15, 2018 7:28 PM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

I added a web page so the current list of talk groups can be seen.
https://www.repeaterbook.com/p25/all_talk_groups.php

I have not added any functionality to repeaters to add these talk groups, yet. Do we have any repeaters in the system with talk groups assignments that would justify the coding time, yet?

Re: P25 subgroup created

Garrett Dow - Site Admin/Owner (KD6KPC)

#82

https://www.repeaterbook.com/p25_info/all_talk_groups.php

Regards,

-Garrett

Show quoted text

On Apr 17, 2018, at 08:27, Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager <n2icv@...> wrote:

Welcome to the Area

Find specialized searches and information for -equipped repeaters.

Fatal error: Call to a member function fetch() on null in /home/nwham123/public_html/repeaters/niche/index.php on line 400

Newest 25 Repeaters
Click a row to view the repeater

Michael W. Andrescavage Sr

N2ICV

n2icv@...

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Tuesday, April 17, 2018 11:10 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

Sorry, I had to change the URL:

https://www.repeaterbook.com/p25_info/all_talk_groups.php

Garrett

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> On Behalf Of Mike A N2ICV ADMIN NJ, Pa, and De. North American DMR Manager
Sent: Tuesday, April 17, 2018 4:17 AM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

Fatal error: Call to a member function fetch() on null in /home/nwham123/public_html/repeaters/niche/index.php on line 400

Michael W. Andrescavage Sr

N2ICV

n2icv@...

From: repeaterbook@repeaterbook.groups.io <repeaterbook@repeaterbook.groups.io> on behalf of Garrett Dow - Site Admin/Owner (KD6KPC) <garrettdow@...>
Sent: Sunday, April 15, 2018 7:28 PM
To: repeaterbook@repeaterbook.groups.io
Subject: Re: [repeaterbook] P25 subgroup created

I added a web page so the current list of talk groups can be seen.
https://www.repeaterbook.com/p25/all_talk_groups.php

I have not added any functionality to repeaters to add these talk groups, yet. Do we have any repeaters in the system with talk groups assignments that would justify the coding time, yet?