The RadioReference.com Forums

The RadioReference.com Forums (https://forums.radioreference.com/)
-   Database Discussion Forum (https://forums.radioreference.com/database-discussion-forum/)
-   -   Alpha tags too long (https://forums.radioreference.com/database-discussion-forum/359282-alpha-tags-too-long.html)

n2pqq 09-20-2017 1:45 PM

Alpha tags too long
 
Hello :

I notice the description fields on a lot of the talk groups
are very long . Some being as long as 45 characters .

This results in the description line being cut short
or not displaying properly.

For example please look at NJICS system and the
New York city NYPD ect .

I know the database is not geared toward any particular scanner model.

That being said I don't believe there is a scanner on the market that
supports alpha tags that long.

I use a BCD536HP , Uniden HP2 and Whistler 1098 and
experience the problem on all radios.

Is there something that can be done to correct this.

ChrisABQ 09-20-2017 2:01 PM

If the tags are too long or look unreadable, I will alter them on my scanner PC programs before uploading to the scanner.

n2pqq 09-21-2017 8:16 PM

Thank you for your suggestion,
however I don't feel that is a
viable solution.

There should be a maximum amount of
characters entered in the description field
that will not cause the overflow effect.

This should be done when items are being
inputted to database.

I bring this up so that the database will be
more enjoyable for all ,when using there scanners.

Southernsky 09-21-2017 8:18 PM

1 Attachment(s)
I just wish they were in all Capital letters both for regular people and vision impaired people in the database,some are oddly.
Mine are all caps!.:)
Look how nice that is.
Aside from my crappy focus on the camera,who cant read that?Clear as day.
TRX1 Whistler

PLEASE UPLOAD EM IN ALL CAPS FOR US BLIND PEOPLE .REMEMBER WE ALL GET OLD ONE DAY!

W8RMH 09-21-2017 9:07 PM

I have always used uppercase tags on my scanners for ease of reading. And yes the RRDB tags are way, way too long. I use FLs for local scanning but use the DB when traveling. On my HP-2 the tag runs off the screen and I can't tell which channel it is because of the description. It should only include the short tag and not the long description. However, these admins are going to do things their own way and they take offense to any suggestions as they feel we are acting like admins or telling them how to do their jobs and they will give you an infraction in a heartbeat.

GTR8000 09-21-2017 9:24 PM

Please do not confuse the Alpha Tag field with the Description field. They are completely separate from each other.

The Alpha Tag field has a maximum length of 16 characters. Nearly all modern scanners with the exception of the Uniden HP and x36HP series use that field when importing with software (including preloaded database on the GRE/RS/Whistler scanners).

The Description field has a maximum length of 128 characters. The HP-1, HP-2, BCD436HP, and BCD536HP use this field instead of the Alpha Tag field.

In any event, while there are a certain percentage of entries in the database that could probably use some trimming down of the Description field, it's not as if we have an epidemic on our hands. Most descriptions are relatively short and sweet.

Keep in mind also that this is the whole reason why the Description field should not contain duplicate text from the Category and Subcategory that the listing is in, as that would surely result in excessively long descriptions.

As far as your gripe with the database admins, W8RMH, maybe your gripe should be with Uniden for using the Description field instead of the Alpha Tag field for the HP based scanners. Oh and database admins cannot give infractions, only moderators can, so quit whining. :roll:

n2pqq 09-22-2017 12:16 AM

Quote:

Originally Posted by GTR8000 (Post 2821391)
Please do not confuse the Alpha Tag field with the Description field. They are completely separate from each other.

The Alpha Tag field has a maximum length of 16 characters. Nearly all modern scanners with the exception of the Uniden HP and x36HP series use that field when importing with software (including preloaded database on the GRE/RS/Whistler scanners).

The Description field has a maximum length of 128 characters. The HP-1, HP-2, BCD436HP, and BCD536HP use this field instead of the Alpha Tag field.

In any event, while there are a certain percentage of entries in the database that could probably use some trimming down of the Description field, it's not as if we have an epidemic on our hands. Most descriptions are relatively short and sweet.

Keep in mind also that this is the whole reason why the Description field should not contain duplicate text from the Category and Subcategory that the listing is in, as that would surely result in excessively long descriptions.

As far as your gripe with the database admins, W8RMH, maybe your gripe should be with Uniden for using the Description field instead of the Alpha Tag field for the HP based scanners. Oh and database admins cannot give infractions, only moderators can, so quit whining. :roll:

The maximum amount of characters that will display on One Line of text without
being cut off or wrapping around is 30.

That should be kept in mind when entering in database.

What I am offering here are ideas to make things better not criticism.

GTR8000 09-22-2017 1:43 AM

Actually, it's exactly 35 characters that fit on a 536HP before the ... appears.

I'm not sure if that also applies to the 436HP, or the HomePatrol models. I believe you can change the font size on the HomePatrol, so you might fit more or less depending on the setting.


Regardless, the current and official policy is as follows:

Quote:

6.1.4.2 FREQUENCY AND TALKGROUP DESCRIPTIONS

Talkgroup and frequency descriptions shall be kept short and informative (50 characters or less) while avoiding exact duplication with other fields where possible. Channel numbers should be included when known. For example:
  • Where an alpha tag states "PD DISPATCH 1" use “Police Dispatch 1” in the Description.
  • Common operating channels shall be shown as "Countywide Common 1" or "Law Interop 1" rather than just "Countywide Common" or "Law Interop" in the Description field.
  • Category or Subcategory headings or names will not be shown or duplicated in the Description field.


W8RMH 09-22-2017 4:04 AM

Quote:

Originally Posted by GTR8000 (Post 2821391)
Please do not confuse the Alpha Tag field with the Description field. They are completely separate from each other.

The Alpha Tag field has a maximum length of 16 characters. Nearly all modern scanners with the exception of the Uniden HP and x36HP series use that field when importing with software (including preloaded database on the GRE/RS/Whistler scanners).

The Description field has a maximum length of 128 characters. The HP-1, HP-2, BCD436HP, and BCD536HP use this field instead of the Alpha Tag field.

In any event, while there are a certain percentage of entries in the database that could probably use some trimming down of the Description field, it's not as if we have an epidemic on our hands. Most descriptions are relatively short and sweet.

Keep in mind also that this is the whole reason why the Description field should not contain duplicate text from the Category and Subcategory that the listing is in, as that would surely result in excessively long descriptions.

As far as your gripe with the database admins, W8RMH, maybe your gripe should be with Uniden for using the Description field instead of the Alpha Tag field for the HP based scanners. Oh and database admins cannot give infractions, only moderators can, so quit whining. :roll:

I wasn't whining just making a point, which you just proved.

dave3825 09-22-2017 11:15 AM

1 Attachment(s)
Quote:

Originally Posted by W8RMH (Post 2821383)
However, these admins are going to do things their own way and they take offense to any suggestions as they feel we are acting like admins or telling them how to do their jobs and they will give you an infraction in a heartbeat.

Its not the admins, it's the software authors. The rr staff are not the ones who decide how and what is downloaded to the scanners.

Quote:

Originally Posted by GTR8000 (Post 2821391)
Please do not confuse the Alpha Tag field with the Description field. They are completely separate from each other.



On the x36 series it seems it's specific to the software. Freescan and Proscan use the "Alpha Tag" while Sentinel uses the "Description Tag" So it's uniden making that choice to download description rather than alpha tags that take less display..

The screenshot shows what each looks like with all 3 using NYS DEC "Statewide" as the example.

jonwienke 09-22-2017 11:39 AM

Proscan actually gives you the choice of using Description or Alpha Tag--the checkbox labeled "Channels-Use Description Name instead of the Display Name".

n2pqq 09-22-2017 1:13 PM

Thank you for the reply:

I would compare that to the following hypothetical situation

Sign on pier says pier length 35 feet
do not proceed beyond 50 feet.

Of course if you do you will fall off the pier.

Looks like the same thing is occurring here.
only 35 characters will display on one line
however 50 may be written thus falling off or
not displaying.

Would you concur that is a fair assessment ?



Quote:

Originally Posted by GTR8000 (Post 2821474)
Actually, it's exactly 35 characters that fit on a 536HP before the ... appears.

I'm not sure if that also applies to the 436HP, or the HomePatrol models. I believe you can change the font size on the HomePatrol, so you might fit more or less depending on the setting.


Regardless, the current and official policy is as follows:

6.1.4.2 FREQUENCY AND TALKGROUP DESCRIPTIONS

Talkgroup and frequency descriptions shall be kept short and informative (50 characters or less) while avoiding exact duplication with other fields where possible. Channel numbers should be included when known. For example:
Where an alpha tag states "PD DISPATCH 1" use “Police Dispatch 1” in the Description.
Common operating channels shall be shown as "Countywide Common 1" or "Law Interop 1" rather than just "Countywide Common" or "Law Interop" in the Description field.
Category or Subcategory headings or names will not be shown or duplicated in the Description field.

marksmith 09-22-2017 2:43 PM

The world is in pretty good shape when this is a concern.
Learn the software and fix it however you want.
That's what its for.

Sent from my LG-V410 using Tapatalk

Spitfire8520 09-22-2017 5:58 PM

Quote:

Originally Posted by n2pqq (Post 2821647)
I would compare that to the following hypothetical situation

Sign on pier says pier length 35 feet
do not proceed beyond 50 feet.

Of course if you do you will fall off the pier.

Looks like the same thing is occurring here.
only 35 characters will display on one line
however 50 may be written thus falling off or
not displaying.

Would you concur that is a fair assessment ?

A more correct hypothetical situation:
  1. 50 feet long pier was built first.
  2. A few years later, someone else (not the builders) comes by and puts down a sign saying you can only use the first 35 feet of the pier.

The pier has always been 50 feet, but someone else won't let you use anything past 35 feet. The description field in the database was around before scanners/software tried to use it.

GTR8000 09-22-2017 7:44 PM

Quote:

Originally Posted by Spitfire8520 (Post 2821819)
The description field in the database was around before scanners/software tried to use it.

Exactly.

The RRDB was first and foremost designed as a means to catalog this information on a website interface, not for means of programming. That came along later as software writers and manufacturers took advantage of the ability to download the data for use with scanners.

As a reminder, the RRDB does not cater to any particular scanner brand or model, nor should it.

KevinC 09-22-2017 7:54 PM

Let's keep in mind any complaints toward moderation activity should follow the guidelines in the below post and not be hashed out in public forums...

https://forums.radioreference.com/fo...-activity.html

Have a GREAT weekend!

marcotor 09-22-2017 11:43 PM

Quote:

Originally Posted by n2pqq (Post 2821445)
That should be kept in mind when entering in database.

But ONLY for users who have 436/536/HP1&2 scanners.
Why should others suffer the flexibility of the description field to make things nicer for YOU?

And yes, I happen to have several models of those scanners, and it puzzles me why Uniden would use that as the "tag", when every other scanner uses the "Tag" field as the "Tag" (which is a completely different annoyance in the inconsistent way they are listed).

mancow 09-23-2017 12:00 AM

I started a huge thread on this a couple years ago.

If it were up to me an additional descriptor field would be added, something that the Uniden software doesn't pick up. It would be a lot of work but the admins would then constrain the current field to something usable and reasonable.

As it is now a good portion of the Kansas KSICS system displays only Kanas State Interoperable Comm......... or something similar.

It's useless.

Oh well...

mancow 09-23-2017 12:01 AM

Quote:

Originally Posted by GTR8000 (Post 2821848)
Exactly.

The RRDB was first and foremost designed as a means to catalog this information on a website interface, not for means of programming. That came along later as software writers and manufacturers took advantage of the ability to download the data for use with scanners.

As a reminder, the RRDB does not cater to any particular scanner brand or model, nor should it.

Why shouldn't it? There are really only two brands in existence. It's not like there are hundreds of manufacturers we have to cater to.


If Uniden won't compromise with the descriptor tag use then just standardize it to a point that there is a reasonable compromise.

W9BU 09-23-2017 7:55 AM

Quote:

Originally Posted by mancow (Post 2821941)
As it is now a good portion of the Kansas KSICS system displays only Kanas State Interoperable Comm......... or something similar.

I just looked at the KSICS system. None of the Description fields say "Kansas State Interoperable Comm....". You sure the problem isn't with your scanner or how you are programming it?


All times are GMT -5. The time now is 6:36 PM.

Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2018, vBulletin Solutions, Inc.
All information here is Copyright 2012 by RadioReference.com LLC and Lindsay C. Blanton III.Ad Management by RedTyger