How do we document zero neighbors in a NL?

[west-pac]

How do we document zero neighbors, or a site that has no neighbors? The default label for the NL (and every field) is "N/A"... and that should mean zero, or none, but in our case, in the RRDB, that just means that that field hasn't been populated or documented yet. So, if "N/A" means it has not been determined yet, once we determine its zero, or none, how do we document that without using "N/A"?

 

[GTR8000]

If there are no neighboring sites/peers, then why is it necessary to put anything in that field? I suppose if you feel that strongly about it, you could make a submission asking the dbadmin to put "None" in that field. Seems simple enough.

 

[west-pac]

If there are no neighboring sites/peers, then why is it necessary to put anything in that field?

There are situations where you can use a NL/Peers to your advantage,...if the NL/Peers are documented.

1) If you're experiencing simulcast distortion (by using an non-SDS scanner) you can listen to a non-simulcast neighboring/peer site and likely still hear some of your local radio traffic.

2) By knowing the Peers to 'your' local Site, you know which surrounding counties may potentially be broadcasted from 'your' local site. (There are likely many people who think if they want to listen to an adjacent county, they need to listen to a Site in that adjacent county.)

3) When traveling around your geographic region, by knowing which Sites are Peers of your Site, you know which Sites will potentially broadcast your local TGs.

 

[GTR8000]

Yes, I'm well aware of why adjacent sites should be documented, however it seems that you're overcomplicating the documenting of a lack of adjacent sites. Just leave it N/A or, as I said, ask the dbadmin to put None in the field.

 

[west-pac]

I'm not overcomplicating anything. I just want "unknown" and "none" to be 2 different labels.....and for that to be standardized across the DB.

 

[GTR8000]

Okay.