So here is the deal.
The backend of that system was in disarray. None of the talkgroups were deleted, except for duplicate ones that were in there (there may be one or two that needs to be addressed).
Several of them had very vauge descriptions of what/where they actually belonged to.
Our standards for database structure was used to revamp and reorganize USAI.
Prior to it, most talkgroups were centered in Charlotte. This means if you used GPS/DB aware products, you wouldn't be scanning the adjacent counties or agencies - unless you were in metro Charlotte.
We also do not normally separate out (in the case of CMPD) patrol areas for police departments or fire departments, etc. They are in there as an *agency*. We can and do (depending on size) separate out the agency from a city listing to cut down the large volume of data that is under one category - which CMPD is presently setup as. So instead of 8+? categories for CMPD, its all together. If any talkgroups are added by the system in the future, they will be automatically be ranged by that agencies GPS range without any backend work or discrepancies cropping up.
As noted in the database heading:
"The Charlotte UASI (Urban Areas Security Initiative) trunked system covers multiple counties centered around Charlotte. The database is structured for system wide emergency services talkgroups at the top, followed by counties and cities in alphabetical order. Towns located within a county are listed after the county level services/departments "
If you are having issues montoring, you may want to check your range setting, or use county or GPS selection crietera.
Prior to the update, none of the counties were linked to the catagories. This may have you on uniden products scanning "Everything" - which is improper in the backend.
Otherwise, no data was deleted. Typically with Uniden its a range selection issue than a database issue.