Database issue

Status
Not open for further replies.

PaulyWog

Member
Premium Subscriber
Joined
Jan 2, 2021
Messages
15
Reaction score
5
Location
Tennessee
The sds series out puts comma delimited data with STS command so if you look at the database header for "TN - State Highway Patrol, District 3: Nashville"
there is a comma in the header.. Is there a way to edit this? IF not then why would the database use chars that is use in the output data from the radio?
 

Attachments

  • database.png
    database.png
    8.1 KB · Views: 31

hiegtx

Mentor
Premium Subscriber
Joined
May 8, 2004
Messages
12,173
Reaction score
4,557
Location
Dallas, TX
The sds series out puts comma delimited data with STS command so if you look at the database header for "TN - State Highway Patrol, District 3: Nashville"
there is a comma in the header.. Is there a way to edit this? IF not then why would the database use chars that is use in the output data from the radio?
You cannot edit it in the main database itself. (I presume you are just using the main database & location.) That heading for the department is derived from how it appears in the RR database online.

But if, instead, you've appended the system to a Favorites list, then you can edit the field however you want.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
The sds series out puts comma delimited data with STS command so if you look at the database header for "TN - State Highway Patrol, District 3: Nashville"
there is a comma in the header.. Is there a way to edit this? IF not then why would the database use chars that is use in the output data from the radio?
That's more of a scanner issue because the STS fields are separated with commas. Software using the output from the scanner could parse the STS data. It's a little tricky but doable or use the xml data from the scanner.
 

PaulyWog

Member
Premium Subscriber
Joined
Jan 2, 2021
Messages
15
Reaction score
5
Location
Tennessee
I don't really like the xml data.. I was hoping for a easier way I guess.. Just doesn't make sense that they'd use comma's in the database in the first place.. So what came first the database or the radio? ..lol
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
I don't really like the xml data.. I was hoping for a easier way I guess.. Just doesn't make sense that they'd use comma's in the database in the first place.. So what came first the database or the radio? ..lol
No problems here parsing the STS data in ProScan. It can be done, just requires a little bit of work.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
Just doesn't make sense that they'd use comma's in the database in the first place.. So what came first the database or the radio? ..lol
It makes sense to me. The RRDB text tags should not disallow comma's due to a particular scanner characteristics. This is an interfacing issue that can be overcome in software.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
Also the RRDB is at the top level of the hierarchy so it really doesn't matter which came first.
 

JoeBearcat

Inactive member
Uniden Representative
Joined
Jun 30, 2020
Messages
2,019
Reaction score
2,586
The sds series out puts comma delimited data with STS command so if you look at the database header for "TN - State Highway Patrol, District 3: Nashville"
there is a comma in the header.. Is there a way to edit this? IF not then why would the database use chars that is use in the output data from the radio?

That's a known issue which will hopefully make the cut to address. It's technically not a bug, but I'm going to treat it as such.

(unless RR wants to make the change on their end since this isn't a Uniden-only issue - it's an issue with any CSV export even if Uniden happens to be the only ones currently offering that.) An argument could be made that commas in text fields is technically inappropriate unless they are surrounded by quotes.

That said, how about some input of what it could be changed to - just mask commas in text fields (change to a space)? Change them to some other character like a ; or a | or a /? What would be the best RR-current-policy solution?

I would suggest changing CSV to |SV, but that might break a lot of software.

Or should any text fields be surrounded by quotes? Would that fix the issue? Or would that break software?
 
Last edited:

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
Are we talking just about the scanner protocol STS command? Asking because that seems to be where the problem is when the text tags contain commas. Importing from the RRDB to programs such as mine with commas in the text tags is not an issue due to the SOAP protocol. Sentinel database format is tab delimited, as you know, so that's not a problem either. It doesn't really matter to me but if I had preference, I would choose the STS output data to be tab delimited. I would stay away from using double or single quotes as those are characters that can also create problems as they can also be in the scanner text tags(names).

{Edit} Also on the older scanners before the HP & SDS such as the DMA types, Those don't accept the comma character in the text tags(sys, group, or channel names) so I believe what I'm doing with ProScan is converting the commas in to spaces so the STS data is not an issue.
 
Last edited:

PaulyWog

Member
Premium Subscriber
Joined
Jan 2, 2021
Messages
15
Reaction score
5
Location
Tennessee
I would agree with Proscan.. Tab delimited or just change the comma to a space in the output.
Other options would be escape the special characters.
 

JoeBearcat

Inactive member
Uniden Representative
Joined
Jun 30, 2020
Messages
2,019
Reaction score
2,586
Are we talking just about the scanner protocol STS command? Asking because that seems to be where the problem is when the text tags contain commas. Importing from the RRDB to programs such as mine with commas in the text tags is not an issue due to the SOAP protocol. Sentinel database format is tab delimited, as you know, so that's not a problem either. It doesn't really matter to me but if I had preference, I would choose the STS output data to be tab delimited. I would stay away from using double or single quotes as those are characters that can also create problems as they can also be in the scanner text tags(names).

{Edit} Also on the older scanners before the HP & SDS such as the DMA types, Those don't accept the comma character in the text tags(sys, group, or channel names) so I believe what I'm doing with ProScan is converting the commas in to spaces so the STS data is not an issue.

I was hoping you would chime in, Bob. Thank you.

Back on the original issue, what is the SW that is causing issues with the STS command? Are we proposing a solution looking for a problem?
 

mancow

Member
Database Admin
Joined
Feb 19, 2003
Messages
6,943
Reaction score
1,136
Location
N.E. Kansas
It's in the latest firmware for both the SDS100 and SDS200. No it's not a solution looking for a problem, it's a nightmare for people trying to parse the STS output data. Also, please check the end of the volume pop up bar in the SDS100. When the knob is pushed and the popup volume bar is presented the progess bar icon glyphs presented as hex 1, 17, 18 and 19 which comprise the bar are not comma delimited at the end. Another control character that I think might represent squelch open or closed is appended to the end next to the hex 19 closing bracket ] glyph so you end up with something that looks like [__________]0 It's actually something like hex 190 or 191 and it throws an exception in python if an extended charcter set is not used since it's trying to reference something way out of the normal ASCII set range.

If I were working on it I think I might have chosen to output the reverse text and text color in the form of color tuples or hex codes in the blank control fields that follow each comma delimted line. That way the program could read in the text display format and color on the fly and apply the color data directly and immediately and not have to rely on reading the text color file to map it. So instead of outputting something like:

,POLICE DISPATCH,******************************,

It might read out decimal:

,POLICE DISPATCH,*050205050 ,

or hex:

,POLICE DISPATCH,*0320CD032

or even the color name

,POLICE DISPATCH,*LimeGreen ,

That way you can read in the odd numbered control line, check for * set reverse, read the color code, set the font color and move on immediately. The radio doesn't allow for PER CHARACTER color control only PER DATA FIELD so no real need for a full matching line of ***** or blanks that comprise the exact matching text data field length. Just indicate reverse or not and color.

My SDS200 here is indicating Main: Version 1.10.00 Sub Version 1.02.01
 
Last edited:

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
8,629
Reaction score
5,231
Location
Ontario, Calif.
It's actually something like hex 190 or 191 and it throws an exception in python if an extended charcter set is not used since it's trying to reference something way out of the normal ASCII set range.
The STS display data contains many codes above dec 127 as you know. I believe that's by design. Is there any way your python scripts can use a different character encoding such as Text.Encoding.GetEncoding(28591)?
That's what I use in ProScan and it's never been an issue.

28591 iso-8859-1 ISO 8859-1 Latin 1; Western European (ISO)

{edit} I don't know python but if it doesn't have any character encoding mechanism then perhaps intercept the incoming data before it gets converted to the ascii conversion.
 
Last edited:
Status
Not open for further replies.
Top