I have been working on the PY-ARM in the last few weeks, as noted in the Apr. SOTA News.
In this message, I ramble about the rules setting process. One thing that bothers me is that I am working alone. I do not like to take the rule making kind of decisions alone. So, in a sort, I am asking fellow SOTA hams for their opinions. So, this is to warn that this a long message.
I have compiled a list of a bit more than 140 summits. That list is some sort of official in nature, since it was published by IBGE, the national mapping agency. Altough that list is height based, I have few doubts that they’ll all qualify for the 150m rule.
I also defined 19 regions. I defined them by mountain range. As is usual, several ranges are used to define state borders. Since no summit can belong to more than one region, I found the range-based regions to be a good solution. Also, I was striving to keep the number of regions small. I first thought that it might lend itself to easier administration. I wanted to have far fewer regions than we have states (currently 27)
I was having issues with the seasonal bonus. At first I asked the MT to allow seasonal bonus per region, but now I think we can go per General Rules and have a seasonal bonus for each subdivision. I have not found my map of call prefixes, so I can work on the subdivisions.
I am not sure if the criteria I had established for the seasonal bonus do really apply.
Mountain season here is considered to run from mid-autumn to mid-spring, with winter being the driest month. Temperatures in mountains falls below freezing only during the nights. Summer is most problematic, with thunderstorms and heavy rain. Perhaps, summer should be the bonus season, instead of winter.
Regarding subdivisions, regions and seasonal bonus, there is another issue I just happened to notice. Several mountain ranges cross several subdivision boundaries. I am not sure if that is a desirable situation either.