This page can't be edited.

VHF Tag Registration

From $1

    Table of contents
    You are currently comparing two old versions - only when you are comparing against the latest version can you revert. Return to version archive.

    Combined revision comparison

    Comparing version 20:37, 4 Dec 2017 by stuart with version 16:20, 11 May 2018 by stuart.

    ...

    1. Download the sample metadata file tagreg.txt (which is attached to this page below) and edit it to match your project information:
      • motusProjID: XXX (numeric project ID)
         
      • tagModel: NTQB-??? (as given on the Lotek invoice)
         
      • nomFreq: 166.38 (nominal tag frequency, in MHz)
         
      • species: XXXXX (optional 4-letter code or motus numeric species ID) 
        Please pick one species here, or omit this line.  You can change species later for individual tags.
         
      • deployDate: YYYY-MM-DD (earliest likely deployment date for any tags)

         
    2. NOTE: each tagreg.txt file should only correspond to groups of tags with the same model, nominal frequency, and intended time frame.  If applicable, create a new tagreg.txt file for each group of tags - ensure you know which tags correspond to which tagreg.txt file.
       
    3. create a .ZIP, .7z or .rar archive for each group of WAV files and its corresponding tagreg.txt file and store them somewhere safe. Eg. if all your tags are intended for the same project, with the same tag model, and the same intended deployment time, you will have one .ZIP file containing all WAV files and the tagreg.txt file.  If you have a group of tags with model NTQB-1, and a group of tags that are NTQB-2, you will have have two .ZIP files; one with all the NTQB-1 WAV files and corresponding tagreg.txt file, and a second of all NTQB-2 WAV files and corresponding tagreg.txt file.
       
    4. upload the .ZIP file(s) to https://sgdata.motussensorgnome.org/upload/index.php
      This requires sensorgnome.org login credentials (email jbrzusto AT fastmail DOT fm to obtain them).

    ...

    Other changes:

    1. /body/ul[2]/li/p/a/@href: "mks://localhost/upload""https://sgdata.motus.org/upload/index.php"
    2. /body/ul[2]/li/p/a/@title: "https://sensorgnome.org/upload""https://sgdata.motus.org/upload/index.php"
    3. /body/ul[2]/li/p/a/@class: nothing ⇒ " external"
    4. /body/ol[4]/li[4]/a/@href: "mks://localhost/Sending_Data_for_Automatic_Processing""https://sgdata.motus.org/upload/index.php"
    5. /body/ol[4]/li[4]/a/@title: "https://sensorgnome.org/Sending_Data_for_Automatic_Processing""https://sgdata.motus.org/upload/index.php"
    6. /body/ol[4]/li[4]/a/@class: nothing ⇒ " external"

    Version from 20:37, 4 Dec 2017

    This revision modified by stuart (Ban)

    ...

    1. Download the sample metadata file tagreg.txt (which is attached to this page below) and edit it to match your project information:
      • motusProjID: XXX (numeric project ID)
         
      • tagModel: NTQB-??? (as given on the Lotek invoice)
         
      • nomFreq: 166.38 (nominal tag frequency, in MHz)
         
      • species: XXXXX (optional 4-letter code or motus numeric species ID) 
        Please pick one species here, or omit this line.  You can change species later for individual tags.
         
      • deployDate: YYYY-MM-DD (earliest likely deployment date for any tags)

         
    2. NOTE: each tagreg.txt file should only correspond to groups of tags with the same model, nominal frequency, and intended time frame.  If applicable, create a new tagreg.txt file for each group of tags - ensure you know which tags correspond to which tagreg.txt file.
       
    3. create a .ZIP, .7z or .rar archive for each group of WAV files and its corresponding tagreg.txt file and store them somewhere safe. Eg. if all your tags are intended for the same project, with the same tag model, and the same intended deployment time, you will have one .ZIP file containing all WAV files and the tagreg.txt file.  If you have a group of tags with model NTQB-1, and a group of tags that are NTQB-2, you will have have two .ZIP files; one with all the NTQB-1 WAV files and corresponding tagreg.txt file, and a second of all NTQB-2 WAV files and corresponding tagreg.txt file.
       
    4. upload the .ZIP file(s) to https://sensorgnome.org/upload
      This requires sensorgnome.org login credentials (email jbrzusto AT fastmail DOT fm to obtain them).

    ...

    Version as of 16:20, 11 May 2018

    This revision modified by stuart (Ban)

    ...

    1. Download the sample metadata file tagreg.txt (which is attached to this page below) and edit it to match your project information:
      • motusProjID: XXX (numeric project ID)
         
      • tagModel: NTQB-??? (as given on the Lotek invoice)
         
      • nomFreq: 166.38 (nominal tag frequency, in MHz)
         
      • species: XXXXX (optional 4-letter code or motus numeric species ID) 
        Please pick one species here, or omit this line.  You can change species later for individual tags.
         
      • deployDate: YYYY-MM-DD (earliest likely deployment date for any tags)

         
    2. NOTE: each tagreg.txt file should only correspond to groups of tags with the same model, nominal frequency, and intended time frame.  If applicable, create a new tagreg.txt file for each group of tags - ensure you know which tags correspond to which tagreg.txt file.
       
    3. create a .ZIP, .7z or .rar archive for each group of WAV files and its corresponding tagreg.txt file and store them somewhere safe. Eg. if all your tags are intended for the same project, with the same tag model, and the same intended deployment time, you will have one .ZIP file containing all WAV files and the tagreg.txt file.  If you have a group of tags with model NTQB-1, and a group of tags that are NTQB-2, you will have have two .ZIP files; one with all the NTQB-1 WAV files and corresponding tagreg.txt file, and a second of all NTQB-2 WAV files and corresponding tagreg.txt file.
       
    4. upload the .ZIP file(s) to https://sgdata.motus.org/upload/index.php
      This requires sensorgnome.org login credentials (email jbrzusto AT fastmail DOT fm to obtain them).

    ...


     
    Powered by MindTouch Core