Tag prefix

[peterdesmet]

Tags seem to have the prefix A69-1601-. What does this stand for and will all tags have that exact prefix?

[PieterjanVerhelst]

This is the code space for a transmitter. The "A69" indicates the acoustic tag is operating at a frequency of 69kHz. The “1601” is a unique number that is understood by the receiver firmware to determine how to detect and decode the tags. It is possible to have 2 tags with the same ID, but different code space, for example A69-1601-13631 and A69-3001-13631. These are 2 different tags and will be identified accordingly. As such, transmitters will not have the same prefix.

[peterdesmet]

In that case, we need the prefix information in the tag metadata! I would suggest to have tag_id contain the whole string (A69-1601-31855) instead of just the suffix number (31855). It will make matching easier too, as the data downloaded from the receiver contains the full codes as well (if I understand correctly).

[PieterjanVerhelst]

By default, code_space and tag_id (in Vemco called "ID") are in separate columns. Is there a possibility to link column code_space with tag_id?

[peterdesmet]

Tag IDs are used in 3 places:

1. Metadata
2. Raw CSV download file from receiver
3. Export file from VEMCO software

Could you send me an example of 2? Depending on the format there, we can decide.

[PieterjanVerhelst]

I forgot something. When reading a receiver, you get a VRL file and a CSV file (and a RLD file, but irrelevant here). The CSV file does not contain the full ID (space_code+transmitter_ID) in 1 column, but in separated columns as mentionned before. However, when exporting a VRL file from the Vemco program (VUE), you get a column named 'transmitter' with the full transmitter ID. I'll send you the two different csv files as an example. Because the VRL file is the most raw form of data, I would prefer to make exports from VRL to CSV and use these for metadata (in case VRL can't be used as metadata).

[peterdesmet]

Conclusion: CSV file retrieved directly from receiver has the following useful columns:

• Date/Time → date_time
• Code Space (A69-1601) → transmitter_id_prefix
• ID (28297) → transmitter_id_suffix
• Receiver name (VR2W-122322) → receiver_id

We definitely need to add the code space info to the metadata, either as a separate column or (my preference) concatenated in the transmitter_id as A69-1601-28297.

[PieterjanVerhelst]

I agree to put it in 1 column (also to reduce the number of columns and keep a good overview). This has to be done manually?

[peterdesmet]

Do we currently have more than one code_space value, or is it A69-1601 for all?

[peterdesmet]

Added for all transmitters