You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Download event function has a small ease of access problem.
Because of the way files are automatically named, when a number of calls from 2 or more talkgroups are downloaded from the same event they will appear in the folder out of order.
This is due to the names assigned to the files. when downloaded the files will appear like such:
ex. mocomdps-4005-1676726457
'mocomdps' being the radio system '4005' being the assigned talkgroup number and I don't know what the third number is.
if you download an event with calls from mult. talkgroups (say TG 4000, 4005, and 4010) the 4000 talkgroups will appear in the file first due to alphabetization order then the 4005, then 4010.
So a proper sequence of calls say transmissions on 4000, 4010, 4005, 4010, 4010, and 4000 again will download as
4000, 4005, 4010, 4010, 4005, even thought this is now out of order
The text was updated successfully, but these errors were encountered:
Ah! great point - my long term plan is to include a small, local website that you could open in your browser and go through the files and also see if the metadata for each call. In the meantime, I will see how hard it would be to add a number for the spot in the list for each file.
The Download event function has a small ease of access problem.
Because of the way files are automatically named, when a number of calls from 2 or more talkgroups are downloaded from the same event they will appear in the folder out of order.
This is due to the names assigned to the files. when downloaded the files will appear like such:
ex. mocomdps-4005-1676726457
'mocomdps' being the radio system '4005' being the assigned talkgroup number and I don't know what the third number is.
if you download an event with calls from mult. talkgroups (say TG 4000, 4005, and 4010) the 4000 talkgroups will appear in the file first due to alphabetization order then the 4005, then 4010.
So a proper sequence of calls say transmissions on 4000, 4010, 4005, 4010, 4010, and 4000 again will download as
4000, 4005, 4010, 4010, 4005, even thought this is now out of order
The text was updated successfully, but these errors were encountered: