D
DaveNF2G
Guest
Frequency 1 Slot 1 = LCN 1
Frequency 1 Slot 2 = LCN 2
Frequency 2 Slot 1 = LCN 3
...etc.
Frequency 1 Slot 2 = LCN 2
Frequency 2 Slot 1 = LCN 3
...etc.
Frequency 1 Slot 1 = LCN 1
Frequency 1 Slot 2 = LCN 2
Frequency 2 Slot 1 = LCN 3
...etc.
Frequency 1 Slot 1 = LCN 1
Frequency 1 Slot 2 = LCN 2
Frequency 2 Slot 1 = LCN 3
...etc.
There are hundreds of thousands of entries in the database when you include every trunked site and talkgroup, in addition to the conventional listings. It would take countless hours for the relatively small team of admins to go through the entire database just once, much less "periodically". So no, we don't because it's completely impractical. What you will get are admins who will keep an eye on the most popular counties, agencies, and trunked systems simply because they are frequent topics of discussion or change. I'm sure some admins from time to time try to do a 'sweep' through their state's systems or listings, but practically speaking it would be nearly impossible to spot every issue or inconsistency. Remember, we are volunteers who often cover entire states or more, which is why we rely on locals like you making submissions to get stuff fixed.Do the admins periodically go through the whole database and do cleanups of obvious inconsistencies?
The Change History is not tied to the submissions in any way, shape, or form. You as an end-user of the database would have absolutely no way to know what changes came from a user submission, vs changes that the dbadmin made on their own accord, or from other sources such as posts in the forums.I suspect so, because of certain changes I've seen at times that don't look like they came from actual user submissions (although there's evidently no way to tell exactly what was changed in the Change History).
As long as the dbadmins and users understand the difference between LCN and LSN as used in the RRDB, I see no issue with them being displayed. Keep in mind that the LSN values are only displayed on the Site Details page, not on the main page of the trunked system itself. In other words, you have to look for them to find them; most people simply look at the main system page and see the LCNs and frequencies, and work from there. Frankly, I think it helps having the LSN listed on the Site Details page, as it allows for a direct comparison with what someone is seeing in the DSD+ Channel Activity window. You may not have noticed the issue with the systems near you if you hadn't seen the incorrect LSN values in the RRDB.Does there even need to be an LSN column?
If they have a premium subscription, the chances are good that they're downloading the system via software, in which case the software will grab the correct LCN, not the LSN. So that's not an issue. If they're creating a system manually either in software or directly in the scanner, then it's up to them to understand the difference between LCN and LSN. Again, as stated above, the LCN and frequency relationship is pretty clear when looking at the main system page.I would be concerned that a lot of scanners out there could unknowingly be getting programmed wrong (mainly Unidens), especially by those with premium subscriptions. You could have a lot of users out there wondering why their Uniden scanners aren't working right (although I've always had reservations about Uniden scanners supposedly doing proper trunk following versus Whistlers).
Note to self: Remember to triple check all DMR trunked system submissions in NY made by @DaveNF2GFrequency 1 Slot 1 = LCN 1
Frequency 1 Slot 2 = LCN 2
Frequency 2 Slot 1 = LCN 3
...etc.
That is exactly how the systems are reported and tracked by DSDPlus.