SPECIFICATION FOR RINGING-DATA EXCHANGE FILE FORMAT Specification 3.40 The BTO Ringing Unit encourages the submission of ringing data (relating to newly-ringed birds, retraps and recoveries, including controls) in the form of computer data files via email to [email protected]or on floppy disks. To enable smooth operation of this system, and minimise the risk of incorrect data being incorporated into the BTO’s computerised archives, there are two essential requirements: ALL data files and disks MUST conform to the format expected by the system; and ALL data to be submitted MUST have passed a preliminary verification, performed by a program supplied by the BTO, before despatch to BTO HQ. This document sets out the technical specification for the content and format of computer data files (and disks) containing ringing data for verification and subsequent submission to the BTO Ringing Unit. This format applies to ALL such files and not just to those produced using the IPMR (and B-RING) programs. This document is primarily intended for users who wish to prepare appropriate submission files using their own systems and programs; most of the information it contains will be embodied in the relevant parts of the IPMR program, so users of this program do not need to study it unless they wish to do so. Ringers writing their own software should follow this specification carefully. Please note that all data will still have to be verified (in IPMR) before submission to BTO HQ. Queries about the procedure for sending emails or submitting disks and the data on them should be directed to BTO HQ (Tel: 01842 750050, Email: [email protected]) ; for programming and other technical queries: IPMR Mark Cubitt (Email: [email protected]). /home/website/convert/temp/convert_html/5aee77687f8b9a585f91b9e4/document.doc 06/03/2022 06:11 1
81
Embed
Ringing data on disc - Welcome to the BTO | BTO - British ... · Web viewSpecification 3.40 The BTO Ringing Unit encourages the submission of ringing data (relating to newly-ringed
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SPECIFICATION FOR RINGING-DATA EXCHANGE FILE FORMATSpecification 3.40
The BTO Ringing Unit encourages the submission of ringing data (relating to newly-ringed birds, retraps and recoveries, including controls) in the form of computer data files via email to [email protected] or on floppy disks. To enable smooth operation of this system, and minimise the risk of incorrect data being incorporated into the BTO’s computerised archives, there are two essential requirements:
ALL data files and disks MUST conform to the format expected by the system; and ALL data to be submitted MUST have passed a preliminary verification,performed by a program supplied by the BTO, before despatch to BTO HQ.
This document sets out the technical specification for the content and format of computer data files (and disks) containing ringing data for verification and subsequent submission to the BTO Ringing Unit. This format applies to ALL such files and not just to those produced using the IPMR (and B-RING) programs.
This document is primarily intended for users who wish to prepare appropriate submission files using their own systems and programs; most of the information it contains will be embodied in the relevant parts of the IPMR program, so users of this program do not need to study it unless they wish to do so. Ringers writing their own software should follow this specification carefully. Please note that all data will still have to be verified (in IPMR) before submission to BTO HQ.
Queries about the procedure for sending emails or submitting disks and the data on them should be directed to BTO HQ (Tel: 01842 750050, Email: [email protected]); for programming and other technical queries:IPMR Mark Cubitt (Email: [email protected]).B-RING David Coker ( Tel: 0118-901-6339, Email: [email protected]).
Submission of Ringing Data Files
A ringing data submission file should be prepared and submitted to the Ringing Unit:
a) when 3 months have elapsed since the last file was submitted AND there are at least 200 newly-ringed birds to be reported;
ORb) when 6 months have elapsed since ringing of a bird which has not yet been reported
to the Ringing Unit;OR
c) when the number of newly-ringed birds not yet reported reaches 1,000 (irrespective of the time elapsed since the last file was submitted);
d) by the end of February at the very latest in each year if any bird ringed in the previous year has not yet been reported to the Ringing Unit;
ORe) if there is a specific need to submit a submission file at a particular time (eg to report
a newly-controlled bird).
A ringing data submission file should include details of all birds ringed but not yet reported to the Ringing Unit at the time the file is prepared; so a file submitted under d) above may include details of birds ringed in January or February of the current year in addition to those ringed in the previous year.
Each file should be emailed to [email protected] or on put a clearly labelled disk, which should be mailed to BTO HQ using a disk mailer obtainable from the Ringing Unit.
EmailThe email must contain the following information: Name(s) and Permit number(s) of ringer(s), partnership(s) and/or group(s) whose data are
in the file(s) Name(s) of data file(s) which are attached (see below) One or more attached submission files Explanatory remarks eg if file(s) contains corrections to data already submitted
Disk FormatThe following disk format is also acceptable:
PC: 3½” high (1.44MB) density disks
Disk LabelThe disk must have affixed a label containing the following information:
Name(s) and permit number(s) of ringer(s), partnership(s) and/or group(s) whose data are on the diskName(s) of data file(s), which are on the disk (see below)
Pre-printed labels with space for this information are available from the Ringing Unit.
Disk Volume Label (ie 'volume label' or 'name' stored magnetically on the disk itself).This label has no significance to the Ringing Unit system; accordingly it may have any value or be left blank.
Email or Disk ContentsAn email will have attached, or disk will carry, one or more data files each conforming to the data file naming scheme and format specified below. An email or single disk may carry files for more than one ringer/partnership/group. However ALL records (whether for newly-ringed birds, retraps or recoveries, including controls) in an individual file must include the same permit number (ie the permit number to which the newly-used rings were issued or transferred); for controlled birds reported in a submission file the Ringing Unit will send the original ringing details to the address on record for the permit number specified in that file, or member of the public (MOP) finder if the details are included in the finder field (94).
Data for birds ringed outside UK and Ireland using BTO scheme rings can (from 2005) be submitted electronically using a separate foreign version of IPMR, available directly from Mark Cubitt.
No files other than verified ringing data files should be present on the disk.
Data File NamesA ringing data file name must have the general form
NNNNN.YYS
where:NNNNN (permit number) is the single number to which the new rings reported in the file were issued or transferred. The permit number should be expressed as two to five digits, with no leading zeroes; the permit type (eg A) and any endorsement (eg M or P) should not be included. This number is followed by a full stop.
YY (year of preparation) is the calendar year in which the data file was prepared for submission to the Ringing Unit. A data file may contain data for handlings in years prior to the year of preparation (eg the first file prepared in each year may contain data for remaining unreported rings used at the end of the previous year). The year should be expressed as two digits (decades and units), with a leading zero if necessary (eg 96 for 1996, 02 for 2002).
S (sequence indicator) is one plus the total number of files already prepared and submitted to the Ringing Unit in relation to the permit number NNNNN during the current calendar year. This sequence number should start at 1, and increment by 1 for each successive file submitted; if more than nine files are submitted in one calendar year, the sequence indicator should step through the letters of the alphabet, starting with A (=10).
Thus the fifth file in 2001 containing data on rings issued to permit number 3242 would be named 3242.015, the twelfth file would be named 3242.01C, and the eighth file in 2002 would be named 3242.028.
ZIP file submissionsOne (and only one) data file can be included within a zip file. The name of the included file must conform to the specification above. The ZIP file name must be of the format NNNNN_YYS.zip where these are defined as above. Files produced in v2.2 of IPMR (2005 onwards) will be automatically zipped as part of the submission creation process.
Data File FormatA ringing data file must consist of one or more records (lines), each record giving the details for a single bird in accordance with the data record format specified below, followed by a total count record as specified below. The contents of a file must be in plain text form, ie as a sequence of ASCII codes representing the sequence of alphanumeric characters forming the data items and their separators. Data should not be stored in any further-encoded form (such as the encoding of numeric values). Decimal points should be included explicitly where relevant.
A ringing data file may contain records for rings of one or more sizes, and records may be in any order.
Header Record FormatThe first record should be a comment line containing a structured set of values. Each value is separated by a comma and must not contain a comma. The format is:
Field Meaning Valid valuesSOFTWARE Software that created file *IPMR, *B-RING or
*MACRINGVALIDATION Type of validation: Internal
or ExternalI or E
CREATION DATE/TIME Date and time that submission file created
dd/mm/yyyy hh:mm
APPVERSION Version of Application that produced file
Application determined eg 2.1.75 or 2.20
SPECIFICATION Submission specification version
3.30 or 3.40
OS Operating system running software
DOS or Windows version eg 3.95
Optionally a second comment line can be present which allows the submitter to specify an email address. The EMAILADDRESS must contain no spaces and one @ character. The format is:
Further comment lines (which must start with an asterisk), for example containing warnings about not altering the content of the file may be added as required.
Data Record FormatA data record consists of a series of fields. The content and required sequence of these fields are specified in Appendix A.
Successive fields are separated by a comma character (ASCII code 44). Any field, which may include a comma character (including PLACE NAME – field 20 and EXTRA TEXT - field 63) must be enclosed in double quote marks (ASCII code 34); double quote marks are not permitted within any field. Any field for which there is no value is left empty but the comma characters separating it from adjacent fields must still be present (ie two commas immediately following one another signify a null field); thus each record must have a full complement of comma separators (one fewer than the total number of fields). There must not be any leading or trailing spaces in any field. Where code fields contain alphabetic characters these must be in upper case.
Every record (line) in a data file must be self-contained, with all relevant values indicated explicitly. No ditto marks should be used, even if the value of a field is repeated in successive records.
The end of a record is marked by a new line character sequence, the exact form of which varies from system to system; for MS-DOS files it is a CRLF pair (ASCII 13,10); for Macintosh files it is a CR alone (ASCII 13).
Total Count Record FormatAfter the last record in a file the total count of data records in the file should be indicated on a separate line, as a sequence of ASCII codes representing the digits making up the count, followed by an end of record marker. This count is exclusive of comment lines and the total record count itself; thus a file containing fifty data records, for a complete string of rings, would end with a total record count containing the value 50 (and not 51).
Note: The data file format specified above is different from that of the BTO Micro-Computer Coding Scheme for Bird Ringing Data (used by B-RING for data files): in particular the identity and sequence of data fields are fixed, so there is no header.
Data VerificationIn order to minimise the risk of incorrect or suspect data entering the BTO's computer archives, all ringing data files to be supplied to the Ringing Unit must pass a preliminary verification before despatch to the BTO HQ. This verification can be carried out using IPMR, which can be downloaded from the BTO website (www.bto.org). The program is also available (on CD only) free of charge from the Ringing Unit.
IPMR Captures> Validate externally produced submission files menu option reads data files conforming to the format defined above and performs various checks (eg validity of species, habitat and region codes, appropriate ring size - as indicated by the ring number - for the species, consistency between codes used in different fields, and consistency of any biometrics with expected ranges for the species). Any discrepancy is reported to the user, alternatively original data files can be amended, a new file for the Ringing Unit prepared and the verification program re-run. If no discrepancy is found a verification code derived from the contents of the data file is appended to the file to indicate to the BTO computer system that the verification has been completed successfully.
The data fields specified in Appendix A include some that are mandatory and some that are optional (eg for biometrics, though ringers are strongly encouraged to submit these). Sometimes a computer program for preparing ringing data according to this format may not have all the mandatory data available to it (eg a user's data files may not contain details of the original ring carried by a re-ringed bird). In this case a preliminary data file must be edited manually (eg to insert the original ring number) prior to verification.
Other Notes
1 Handlings (new birds, retraps or recoveries, including controls) should be reported to the Ringing Unit once only in a ringing submission file; such a file should not normally contain details of rings reported in a previous submission file. However, repetition of a record is permissible to correct any inaccuracy in the record as originally submitted. Note: for any duplicate records that are received by the Ringing Unit the latest version is generally assumed to be correct (unless it is obvious that it was sent in error).
Likewise, details of a controlled bird, which are reported in a submission file should not be reported on a paper recovery form as well. (If it is desired to report a controlled bird without delay, a submission file may be submitted with a file containing a single record relating to that bird.). If the original ringing details have not been received from the Ringing Unit for the control, DO NOT resubmit the control in a subsequent data file, contact the Ringing Unit to check the reason for the delay.
Note that, if the ringing details for a bird are specifically requested by the Ringing Unit (ie on a 'Blue Card'), the requested information should be supplied immediately by sending in a data submission file.
2 Ringers ringing species on Schedule 1 of the Wildlife and Countryside Act at sites they wish to be confidential should submit the open details. Confidential details should be sent in on paper schedules – see Ringers’ Manual for details.
3 It is suggested that programs for preparing ringing data submission files should produce a report summarising the contents of a file by species and record type, species and place, and species and date. This report is not required by the Ringing Unit but may assist the user to make a manual cross-check of the records contained in the file.
4 A comma-delimited file as required by this specification is available as an output option in a variety of commercial application programs, such as spreadsheet and database programs.
5 When a submission file is received at BTO HQ it is scanned for viruses. Email submissions receive an immediate, automated reply. Attached email files and disk files are checked for record counts and validation codes and then the data files are copied over to the BTO's main computer where additional checks are performed (eg for new rings, were the rings issued or transferred to the relevant permit number). Once the data have been transferred, a reply email is sent or the disk is returned confirming data have been loaded. If any problems have been encountered it may not be possible to transfer part or all of a file, in this case a note of the problem is returned with the email or disk and the ringer is asked to resubmit the data
6 Examples of the format specified above are given in Appendix B2
Content and Sequence of Fields comprising a Ringing Data Record
Fields marked *** must always contain a value; fields marked ** must normally contain a value; fields marked * must have a value for certain categories of record, as indicated.
This record format is independent of the BTO coding scheme for ringing data held on computers. However, to assist users of that scheme the fields in that scheme which correspond to fields specified in this record format are indicated where appropriate.
1 ***
Record type (RTYPE$)
Character = 1.One code only, from the following list:
N New bird (or ring lost/missing/destroyed)R Retrap1 Retrap, ring replaced2 Retrap, ring added3 Retrap, already with two ringsC Control4 Control, ring replaced5 Control, ring added6 Control, already with two ringsS Control (field record/Observation)1 8 Control (field record/Observation) already with two (metal) ringsO Retrap (field recordObservation)– usually ringer’s Own bird A Anything Else2 X Dead (except pulli which die before fledging)9 Dead, already with two ringsP Pullus which died before fledging (must be the sole record for a bird ie
should be used instead of N where a bird is ringed and subsequently dies before fledging) Keep date the same = date of ringing
E New bird, excluded from ringing totals(eg captive-bred birds, birds in poor condition, birds captive for more than 24 hours)
M Measurement only (Metal ring number not known)
For type E, an appropriate Condition code (H, P, C or R) must also appear in the
1 Sightings/Observations are reports of metal or colour rings read in the field, or records from satellite, RFID tag or radio tag without the bird being caught. They may be either controls or retraps.2 ie alive but not a new bird, control, retrap or sighting, or not known if alive. Eg ringed bird, which came down neighbours chimney and was handed to ringer, note put through ringers letterbox with note of a ring number but no indication if bird alive or dead and no contact name and address.
condition of the bird field (field 10). For types R, C, S, O, 1 to 6 and 8, the time (typically of capture) must appear in
the time field (field 16), to enable multiple records of a bird on one day to be distinguished.
For types R, C and 1 to 6, the appropriate code (8, or 7 if the bird was caught and released by a member of the public) must also appear in the Finding Condition field (field 31).
For types X and 9, the appropriate code (1, 2, 3 21 or 22) must also appear in the Finding Condition field (field 31), and a brief description of finding circumstances must also appear in the Submission Extra Text field (field 63).
For types O, S and 8, the appropriate code (89, or 79 if the sighting was by a member of the public) must also appear in the Finding Condition field. and the type of ring read selected from the list in the Finding Circumstances field (field 70).
For type A the appropriate code (0, 4 5, 6, 7 or 9) must also appear in the Finding Condition field (field 31) and a brief description of the bird’s condition (eg found sick, released), and the circumstances in which it was found must appear in the Submission Extra Text field (field 63).For types N, E and P no code should appear in the finding condition field.
2 ***
Permit number (RPN)Numeric max 5.For new birds: the permit number to which the ring identified at field 4 was issued or transferred.For retraps and controls: the permit number of the group, partnership or individual ‘A’ ringer responsible (ie to whom rings used at the site were issued).Two to five digits, with no leading zeroes; permit type (eg A) and any endorsement (eg M, P) should be omitted (eg 579, 3079).
3 ***
Ringing scheme (SCHEME$).
Character = 3.The code for the ringing scheme which issued the ring identified at field 4 - Ring Number (see Appendix C); for all newly-ringed birds (record types N, P and E or 1, 2, 4, 5) this is GBT
4 ***
Ring number (RING$)Character max 12.Record typeN,E,P
R,C,S,X,P,O,A1,2,4,5
3,6,8,9
Contents of this fieldThe number of the ring placed on the bird, must be a valid and existing ring number The number of the ring already on the birdThe number of the new ring placed on the bird, must be a valid and existing ring numberThe number of one of the two rings on the bird
Missing or unreadable characters should be entered as _ (underscore), not valid for newly ringed birds (record types N, P, E or 1, 2, 4, 5) 12 characters maximum
Character = 5. Species code from the approved Ringing Unit list (see Appendix D). Note that names which contain fewer than five letters are padded with trailing periods (eg JAY.., KNOT., WREN.). The following codes are also allowed:*LOST ring lost*MISS ring missing*DEST ring destroyedHYBRI hybrid species; when used then the names of the species must appear in the Extra Text field*UNKN ring used but ringing data lostIf code ****1 is used for a rarity then the name of the species must appear in the Submission Extra Text field (field 63).
6** Age (AGE$)Character max 2. EURING age code. 1J, 2J, 3J, 5J, 4I, 6I and 8I should be entered where appropriate. Note that the code for pullus is 1, not P. Required value except for rings lost / missing / destroyed/unknown. Maximum value 16.
7 Sex (SEX$).Character = 1. Sex. M or F; leave empty if not known
8* Pulli ringed (BFRACT1%)Numeric max 2. Total number of birds ringed in this brood. Leading zeroes are not necessary. Required for pulli (age code 1) including record type (field 4) P (ie pullus which died before fledging). Where number from a brood that have been ringed is not known because of creching then enter 1. Where some pulli are removed for ringing,translocation & release (eg Red Kite) then record the number ringed at the time (ie not including the ones removed to be ringed at another location) but the pulli alive should be recorded as the total number of pulli (ie include the ones removed for release elsewhere). A supplementary note in the submission text field (field 63) noting ‘X pulli removed for translocation & release’ should be inlcuded).Optional for local young (age code 1J) and young (age code 3) Mute Swans. Not allowed for other age codes.
9* Pulli alive (BFRACT2%).Numeric max 2. Total number of birds alive in this brood at the time of ringing, including runts and any others not ringed (including those that are removed for translocation & release eg Red Kites). Must be a figure not less than Pulli Ringed. Must not be present if Pulli Ringed value not present. For species with precocial young as given in Appendix G if the brood size is not known (eg Lapwings), leave empty. If number of pulli alive is not known and species is not listed in Appendix G then this field can be left blank if an explanatory comment is added to Extra Text (field 63). Leading zeroes are not necessary. Required for pulli (age code 1) if known unless record type (field 5) is P (ie pullus which died before fledging). Optional for local young (age code 1J) and
10* Condition of bird (COND$)Character = 1.One code only, from the following list:H captive-bred (ie with Human involvement)P Poor conditionC Captive more than 24 hoursM Manipulated on ringing (eg radio transmitter added)R in poor condition because captured (Ringing accident)N held over NightT transported To place specified at fields 19 to 30K Fledging provoKed If code T is specified here, the place specified at fields 19 to 30 must be the place
where the bird is released. If multiple codes are applicable the one which occurs first in the list should be
selected: for example, if a radio transmitter is fitted to a bird which is held overnight, the correct code is M.
Required (with value H, P, C or R) if the record type (field 6) is E. H only allowed with record type E
Record type N not permitted for P, C and H
11* Ring information (RINFO$)Character = 1.One code only, from the following list:U individual (Unique) colour mark, eg Wing tagI Individual colour ring combinationM colour Mark (not ring), not individually identifiable, eg leg flag or dyeR conventional colour Ring(s), not individually IdentifiableA any metal ring Above tarsusW Wing tag (not a ring or colour mark), ie this bird is wing-tagged instead of
being ringed; normally only used for penguins, not for coloured wing tags (which are codes U or M)
O On tarsus (indicates re-ringed at finding)S Metal ring already present X Metal ring removedN No metal ring
If multiple codes are applicable the one which occurs first in the list should be selected: for example, if a wader is dye-marked and has a metal ring above the tarsus, the correct code is M.Required only for records where a colour mark has been added or changed, where the colour mark codes are detailed in the appropriate field (83-90) otherwise leave blank (see fields 83-90).
12* Sexing method (SXMTD$)Character = 1.Required if birds sexed by using method other than plumage. In order to provide information on breeding seasons ringers are asked to collect this information even when birds have been sexed using plumage.
One code only, from the following list: D DNA T DissecTed L Laproscopy E internal cloacal ExaminationC Cloacal protuberance (males only)B Brood patch (females only)S Size difference (ie a measurement such as wing length is the only criterion of
sexing) A Activity If multiple codes are applicable, the one that occurs first in the list should be
selected: for example, B for sexed on brood patch and measurement. Code C may only be used if sex is M Code B may only be used if sex is F
13* Activity code 1 (ACT$)Character = 1.Required if bird is carrying out any of these activities when caught. One code only, from the following list:A Artificial bait – provided intentionally or
UnintentionallyT Tape luredL at LighthouseS at SeaN Nesting/breeding adultC at Colony (must not be used for pulli)M Moult of wings or tailR at RoostP on PassageW WinteringIf multiple codes are applicable, the one that occurs first in the list should be selected; a second code may be entered in the following field only if this field is completed. If active moult is indicated among the biometrics (ie fields 42, 43 or 44), code M should be entered here or in the next field if higher priority codes are not already in these fields. Conversely, code M should not be present if any of fields 42, 43 or 44 contain a value but, of those that are present, none indicate active moult (NB Active moult is defined as a bird which is currently growing some wing or tail feathers). It is acceptable for all of fields 42, 43 and 44 to be blank and Activity code to be M.
14* Activity code 2 (ACT2$)Character = 1.One code only, as for Activity code 1. May only be completed if Activity code 1 is present.
15 **
Date of capture (DAY%,MONTH%,YEAR%)
Numeric = 8.In sequence day month year, all as numbers with leading zeroes.The year should have four digits.Examples: 1 January 1996 = 01011996, 29 September 2002 = 29092002.Required except for rings lost/missing/destroyed/Unknown. If date is not known exactly, the beginning and end of the range of possible dates should be put in the
Submission Extra Text field (field 67), and the appropriate date accuracy in days in the Date Accuracy field ( field 69).
16 * Time of capture (and possibly of weighing) (TIMC% or TIM%)Numeric = 4. Local time (eg BST in summer, GMT in winter): 24-hour clock, hours and minutes, IPMR (and B-RING) allow four digits to be input.
Required if the record type (field 8) is R, C, S, 1 to 6 or 8 (retrap, control, etc.), or if there is an interval between capture and weighing (eg cannon-net catches of waders, and roost catches). If time of capture is the same as time of weighing, duplicate time of weighing here.
17 **
Habitat code 1 (HAB1$)
Character = 2.One two-character habitat code, using the appropriate letter and Column A code from the BTO Habitat Coding Scheme (see Appendix E; note that code G10 becomes GA for electronic ringing data files). Required except for rings lost/missing/destroyed/unknown or when Finding Condition = 8 or 89 and (in IPMR) where Place code is not an Owner Place. In this case the user should be requested to enter the habitat code if it is known.
18 Habitat code 2 (HAB2$)Character = 2.One optional additional habitat code, as for Habitat code 1. May only be completed if Habitat code 1 is present. Should not be the same as Habitat code 1.
19 **
Registered site code (REGCODE$)
Character = 3.(Applicable only to birds ringed within the British Isles) 3-letter site code, Alphabetic characters only. if any, registered with the Ringing Unit under the permit number at field 9 in respect of the place of ringing or of release if transported - Condition code T (field 10). From summer 2005 new sites are no longer registered, but existing registered site codes will be maintained and submitted in electronic data files.
20 **
Place name (PLNAME$)
Character max 40, enclosed in (and not including) double quote marks Name of place of ringing or of release if transported – Condition code T (field 10). Omit if the ring is lost/missing/destroyed/unknown; otherwise must be included.In the case of confidential ringing sites, this field should contain the text “Site Confidential” (including the double-quote marks) it may also contain a vague name (see Other Notes - 2 above) or its registered site code.For ERH Sitename1 & Sitename2 on the ORACLE Sites table are concatenated, separated by a comma, to a maximum of 80 Characters.
Character max 5 (field length of 4 for 3.40 spec or lower for foreign places).EURING region (county) code (see Appendix F). Required except for rings lost/missing/destroyed/unknown.
22 **
Grid reference (GRID$)
Character max 6. (Applicable only to birds ringed in Britain and Ireland). Character Grid reference of ringing place, to 1 km accuracy. Two letters (or I and one letter for Ireland) followed by four digits. Required except for rings lost/missing/destroyed/unknown.
23 Grid reference Accuracy (GRIDACC$)Numeric max 2. (Applicable only to birds ringed in Britain and Ireland). Grid reference accuracy: distance in km (0,1 or 2) of maximum extent of site from central location identified at field 22 or deliberate inaccuracy in km (5 to 25 or 99) of grid reference for a confidential ringing record.
24 * Latitude – degrees (IRLA$)Numeric max 2. (Applicable only to, and required for, birds ringed outside Britain and Ireland) Degrees part of latitude of ringing place (0 to 90).
25 * Latitude – minutes (IRLA$)Numeric max 2. (Applicable only to, and required for, birds ringed outside Britain and Ireland). Minutes part of latitude of ringing place (0 to 59).
26 * Latitude – hemisphere (IRLA$)Character = 1. (Applicable only to, and required for, birds ringed outside Britain and Ireland). Hemisphere containing latitude of ringing place: N for North or S for South.
27 * Longitude – degrees (IRLO$)Numeric max 3 . (Applicable only to, and required for, birds ringed outside Britain and Ireland) Degrees part of longitude of ringing place (0 to 180).
28 * Longitude – minutes (IRLO$)Numeric max 2. (Applicable only to, and required for, birds ringed outside Britain and Ireland). Minutes part of longitude of ringing place (0 to 59).
29 * Longitude – hemisphere (IRLO$)Character = 1. (Applicable only to, and required for, birds ringed outside Britain and Ireland). Hemisphere containing longitude of ringing place: E for East or W for West.
30 Co-ordinate accuracy (IRLACC$)Character max 3. (Applicable only to birds ringed outside Britain and Ireland).
As a numeric value alone if in minutes; as a numeric value followed by the letter D if in degrees.
31 * Finding condition (FIND$)Numeric max 2.One code only, from the following list:0 Unknown1 Dead - no information on how recently2 Freshly dead (died less than one week ago)21 Destroyed22 Dying3 Dead: Not fresh (died more than one week ago)4 Sick or injured: now released5 Sick or injured: not released or not known if released6 Alive and probably healthy and taken into captivity7 Alive and probably healthy and released by non- ringer79 Field record by non-ringer8 Controlled (by a ringer)89 Field record by a ringer9 Alive and probably healthy, fate unknownThe normal code for a bird controlled or retrapped and released after examination of the ring is 8. Required if the record type (field 10) is R, C, 1 to 6, S, 8, O, X, 9 or A.
32 * Other ringing scheme (SCHEM2$)Character = 3. The code for the ringing scheme that issued the ring identified at field 33 (see Appendix C); GBT for the BTO ringing scheme. Required if there is a second ring at field 33.
33 Other ring number (RING2$)Character max 12.Record type Contents of this field1,2,4,5 The number of the old ring already on the bird3,6,8,9 The number of the other of the two rings on the birdMissing or unreadable characters should be entered as _ (underscore). 12 characters maximum. This field should be empty for all other record types.
34 ***
Biometrics flag This is an indicator to help ORACLE processing at BTO HQ.
Numeric = 1.Fields 1-34, 60,63-82,94,95-101, 104-111 and 130-131 are ignored for the biometrics flag.Fields 35-59, 61,62, 91-93, 102-103 and 112-129 are defined as group A (Biometrics). Fields 83-90 are defined as group B (colour marks).
Biometrics flag values:0 if no values in group a or b1 if values in group a
35 Weight (WT%)Numeric(real) max 7. Weight in grams, to a maximum precision of 0.1 g, with explicit decimal point (up to five digits plus, if appropriate, decimal point and fraction digit).
36 * Date of weighing (WTDTE$)Numeric = 8. In sequence day month year, all as numbers with leading zeroes.
The year should have four digits.Examples: 1 January 1996 = 01011996, 29 September 2002 = 29092002. Required if a weight is given at field 35; if date of weighing is the same as the date of capture (field 15), repeat date of capture here. Must be equal to, or after, date of capture.Not required if Capture Date/Time are not recorded, or a weight is not recorded.
37 * Time of weighing (WTTIME%)Numeric = 4. Local time (eg BST in summer, GMT in winter): 24-hour clock, hours and minutes, . IPMR and B-RING allow four digits to be input. Required if a weight is given at field 35. Must be equal to, or later than, time of capture if date of weighing is same as date of capture. IF weight is given but no time is recorded, defaults to time of capture but IPMR issues a warning to record the time of weighing.Not required if Capture Date/Time are not recorded, or a weight is not recorded.
38 Wing measurer's initials (WINGINIT$)Character max 3. Initials of the person making the wing measurement recorded at field 39. Uppercase character.
39 Wing length (WING%)Numeric(real) max 5. Wing length in millimetres, to a maximum precision of 0.5 mm, with explicit decimal point (up to three digits plus decimal point plus fraction digit); flattened and straightened (Svensson method 3). It is recommended that wing length normally be measured to the nearest millimetre; however, a higher precision is permitted here to accommodate occasional circumstances in which it is justified.
40 State of wing point (POINT$)Character = 1.One code only, from the following list:A AbradedV Very abradedB Broken G GrowingM feather MissingThere should be no wing measurement recorded in WING% if codes V, B, G or M are recorded, except for pullus for which G is permitted.
41 Length of primary feather (PRIML%)Numeric(real) max 5. Length of primary feather (usually the eighth, numbered descendently) in millimetres, to nearest 0.5 mm, with explicit decimal point (up to three digits plus decimal point plus fraction digit).
42 Moult code (MOULT$)Character = 1.One code only, from the following list:J wholly Juvenile plumageP undergoing Post-juvenile body moult (see codes M, A if in full post- juvenile moult)B undergoing active Body moult - not a post-juvenile moult and not part of a Full moult of wings and tailO Old plumage, no body or main moult (includes birds that have completed
partial post-juvenile moult, and also birds of unknown age in Autumn before 31/12
S Starting body moult: main moult yet to start – wings and tail oldE Ending body moult: main moult finished - wings and tail newN New plumage following main moult, no body or main moult (used for birds
that have recently completed moult. Not used after 31 December)M* active Moult of wings and tail (main moult)A Arrested wing moult (primaries or secondaries)T Post-juvenile moult involving Tail or Tertials*if Moult Code = M then ACT$ or ACT2$ (fields 12 or 13) should be set to M if not already in use for other higher priority activity codes.
43 Primary moult score (PPSC%)Numeric max 2. Sum of moult scores (see next field) for primary feathers (0 to 50). If Primary Moult (field 44) is completed then this field must equal the sum of the
first ten numeric values in field 44. A code of V in primary moult (field 44) should be scored as 0. If a code of U appears in primary moult (field 44), then this field should not be completed.
If the Primary Moult Score is 1-49 (inclusive) then ACT$ or ACT2$ (fields 12 or 13) should be set to M if not already in use for other higher priority activity codes, unless score is because of arrested moult.
If there is a value in Moult code and the Primary Moult Score is not 0 or 50 then Moult code must be M or A.
If Moult code is A then Primary Moult Score must end in 0 or 5 as individual codes must all be 0, 5 or V.
44 Primary moult (PPMLT$)Character max 20. Between ten and twenty moult scores for individual primary feathers, in sequence from the body outwards (descendently): 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new. If any of the 10 Primary Moult Scores is 1-4 then ACT$ or ACT2$ (fields 12 or
13) should be set to “M” if not already in use of other higher priority activity
codes. If Moult code is A then individual moult scores must not be in the range 1-4. If
there is a value in Moult code and the sum of the individual moult scores is not 0 or 50 then the Moult code must be M or A.
45 Old greater coverts (OGC%)
Numeric =2. Progress of post-juvenile moult through the greater coverts – number of old greater coverts (0 to 10).
46 Alula (ALULA%)Numeric = 1. Progress of post-juvenile moult through the two largest feathers of the alula; one code only, from the following list:0 both old1 largest old, other new2 largest new, other old3 both new
47 * Bill length method (BLMTD$)Character = 1.One code only, from the following list:S to SkullF to FeathersC to CereN to NostrilRequired if a bill length measurement is given at field 48.
48 Bill length (BILL%)Numeric(real) max 5. Length of bill in millimetres, to a precision of 0.1 mm if less than 100 mm; normally to a precision of 1 mm if 100 mm or more (maximum precision of 0.1 mm), with explicit decimal point (up to three digits plus, if appropriate, decimal point and fraction digit).
49 THL (head+bill length) (THL%)Numeric(real) max 5. Total head length (length of head plus bill) in millimetres, to a precision of 0.1 mm if less than 100 mm; normally to a precision of 1 mm if 100 mm or more (maximum precision of 0.1 mm), with explicit decimal point (up to three digits plus, if appropriate, decimal point and fraction digit).
50 * Bill depth method (BDMTD$)Character = 1.One code only, from the following list:N at distal edge of NostrilT at TipD at Deepest point along billG at proximal end of GonysF at Feathers
B at BoneM at MidpointO at any Other pointRequired if a bill depth measurement is given at field 51
51 Bill depth (BILLD%)Numeric(real) max 4. Depth of bill in millimetres, definitely to a precision of 0.1 mm, with explicit decimal point (up to two digits plus, if appropriate, decimal point and fraction digit).
52 * Tarsus method (TSMTD$)Character = 1.One code only, from the following list:S Minimum tarsus (Svensson) – length of tarso-metatarsal boneT Tarsus and Toe: length to end of longest toe, foot flattened on ruleM Maximum tarsus (folded foot to extreme end of tarsal joint)Required if a tarsus measurement is given at field 53.
53 Tarsus length (TARSUS%)Numeric(real) max 5. Length of tarsus in millimetres, to a precision of 0.1 mm for methods S and M (field 52) and to a precision of 0.5 mm for method T, with explicit decimal point (up to three digits plus, if appropriate, decimal point and fraction digit).
54 Tail length (TAIL%)Numeric(real) max 5. Length of tail recorded to 0.5 mm, but more usually to nearest mm. (up to 3 digits plus, if appropriate, decimal point and fracton digit). Decimal point and fraction digit are optional and if missing does not imply reduced accuracy.
55 Claw length (CLAW%)Numeric(real) max 4.Length of hind claw in millimetres, ideally to a precision of 0.1 mm, with explicit decimal point (up to two digits plus, if appropriate, decimal point and fraction digit).
56 Plumage (PLUM$)Numeric = 1.One code only, from the following list:1 full winter plumage2 trace of summer plumage3 ¼ summer plumage4 ½ summer plumage5 ¾ summer plumage6 trace of winter plumage7 full summer plumage
Note: codes J and I, if applicable, should appear in AGE (field 11).
One code only, from the following list:0 absent1 starting2 well defined3 veined and red4 wrinkled5 feathering overP present
58 Fat score (FAT$)Numeric max 2.See Fat Score Method (Field 94)For Fat Score Method ‘E’ one code only, from the following list based on codes described by A. Kaiser (1993, J. Field Ornithol. 64: 246-255) (F=Furcular region; A=Abdomen; B=Breast muscles; see diagrams below):00 No fat, or trace05 F: small strip. A: fat not delimited10 F: wedge of fat. A: trace of fat.15 F: almost completely covered. A: trace.20 F: filled but concave. A: slips of fat.25 F: filled but concave. A: very small pad.30 F: moderate covering of clavicles. A: flat or slightly bulging pad.35 F: still concave. A: slightly bulging.40 F: completely filled up to far end of clavicles. A: covered by clearly
bulging pad of fat.45 F: filled to far end of clavicles. A: abdominal structures covered50 F: convex bulge, perhaps overlapping breast muscles. A: extreme convex
bulge.55 F and A: flight muscle border covered by a few mm60 F and A: fat covering breast muscles by several mm.65 Fat reaches flight muscle from side of wings70 F and A: ¾ of breast muscles covered.75 Small rounded fat free area80 F and A: breast muscles not visible.
For Fat Score Method ‘B’ one code only, from the following list based on codes described by BTO Biometrics Working Party0 No visible Fat. Dark Red1 F: trace of fat (~E05). Light red/pink2 F: base of trachael pit obscured by fat to about one third full (~E10). Yellow-
pink3 F: Trach pit about two-thirds full. Muscle within trachael pit visible between
fat and clavicles (~E15). Yellow-pink.4 F: completely filled up to far end of clavicles but still concave (not bulging)
(~E30)5 F: convex bulge, perhaps overlapping breast muscles. A: extreme
convex bulge (~E50).6 F and A: fat covering breast muscles by several mm (~E60).7 F and A: ¾ of breast muscles covered (~E70).8 F and A: breast muscles not visible (~E80).
59 Pectoral muscle score (PEC%)Numeric = 1. Size of pectoral muscle. One code only, from the following list: Prominence of sternum Pectoral muscle shape0 Sternum sharp Muscle depressed1 Sternum easy to distinguish Muscle neither depressed, sharp nor rounded
but not sharp2 Sternum still distinguishable Muscle slightly rounded3 Sternum difficult to distinguish Muscle rounded (full)
60 Capture method (MTHOD$)Character = 1.One code only, from the following list:A Actively-triggered trap (by ringer)B trap automatically triggered by BirdC Cannon net or rocket netD DazzlingF caught in Flight by anything other than a static mist net (eg flicked,
Fleyged)G nets put under water’s surface and liftedH by Hand (with or without hook, noose etc.)L cLap netM Mist netN on Nest (any method)O any Other systemP Pneumatic/Phut netR Round up whilst flightlessS Bal-chatri or other Snare deviceT Helgoland Trap or duck decoyU dutch net for plUvialis apricariaV roosting in caVityW passive Walk-in/maze trap
Field not applicable to pulli
61 Pullus Stage code (PULCODE$)Character = 2.Pullus stage code (not age in days). One code only, from the following list:DO DownyIP primary feathers In PinFS primary Feathers Short: < 1/3 emerged from sheathFM primary Feathers Medium: 1/3 to 2/3 emerged from sheathFL primary Feathers Large: > 2/3 emerged from sheath
62 Race (RACE$)
Numeric max 2.If there is no race code this field should be null.See Appendix I for details of Race Codes (new for 3.40)
63 * Submission Extra text (TEXT)Character max 40 enclosed in (and not including) double quote marks.Required with brief description of finding circumstances if the record type (field 12) is X or 9;Required with brief description of finding conditions and circumstances if the record type (field 1) is A;Required with the beginning and end of range of possible dates if an exact date cannot be given in field 15:Required with brief explanation of circumstances if the non-standard ring size used;Required if number of Age is 1 and pulli alive is not known and species is not listed in Appendix G. Required if record is being resubmitted – ie to correct a previous error.
64 Validation codesNot loaded into ORACLE from submission files.Codes used internally by B-RING’s BTOCHK program to avoid multiple prompts for user to confirm record content.
65 Capture TypeCharacter = 1.Not loaded into ORACLE from submission files.Always blank for ringing capture records with a ring number in submission files sent to BTO HQ. Only used for Electronic Recovery History files and Observation reports where metal ring not known (these are submitted to BTO HQ and currently printed out to send to colour mark co-ordinators).
O
F
R
Observation records where bird has no unique metal ring number specifed in Ring Number (field 4), but has other means of identification – currently colour marks. There should be no Ring Information value for these records.First Ringing details; used for importing these Capture Type records into IPMRSubsequent encounter of bird; which has been made by someone other than the original ringer. Used for importing these Capture Type records into IPMR
66 Place code (PLACE)Character max 6.Place code (up to 6 alphanumeric characters in uppercase plus _-/ and space); (B-RING only supports 3 characters)
67 Subsite (SITE)Character max 6.Subsite code (up to 6 alphanumeric characters in uppercase plus _-/ and space)
68 Processor’s Initials (INIT)Character max 3.Processor’s initials (uppercase)
69 Date Accuracy (DTEACC)Character max 4. Either a positive integer from 1 through 9999 indicating a range in days either side of
the date in field 15 OR one code from the following list. The record type must be one of those listed for each code.ILRU
Date of ring issue NEP123456Long dead X9Date of report RC123456AS8X9Unknown date NEPRC123456AX9S8O
70 Finding Circumstance (CIRCUMSTANCE)Numeric = 2.Not loaded into ORACLE from submission files.One code from Euring list of finding circumstance codes. When a submission file is created only the finding circumstance codes relating to field sightings and controls are included and imported into ORACLE (see Submission Finding Circumstance Code field 141):
71 Own data (OWN)Character max 10.User’s own data (up to 10 characters); enclosed in, and not containing, double quotation marks.
72 Own data 2 (OWN2)Character max 20.User’s own data (up to 20 characters); enclosed in, and not containing, double quotation marks.
73 Userc1Character max 1.User field (up to 1 character); enclosed in, and not containing, double quotation marks.
74 Userc2Character max 2.User field (up to 2 characters); enclosed in, and not containing, double quotation marks.
75 Userc3Character max 4.User field (up to 4 characters); enclosed in, and not containing, double quotation marks.
76 Userc4Character max 8.User field (up to 8 characters); enclosed in, and not containing, double quotation marks.
77 Userc5Character max10.User field (up to 10 characters); enclosed in, and not containing, double quotation marks.
Character max 255.User field (Variable length, up to 255 characters); enclosed in, and not containing, double quotation marks.
79 Userv2Character max 255.User field (Variable length, up to 255 characters); enclosed in, and not containing, double quotation marks.
80 Userv3Character max 255.User field (Variable length, up to 255 characters); enclosed in, and not containing, double quotation marks.
81 Userv4Character max 255.User field (Variable length, up to 255 characters); enclosed in, and not containing, double quotation marks.
82 Userv5Character max 255.User field (Variable length, up to 255 characters); enclosed in, and not containing, double quotation marks.
83 Left leg below tarsus colour mark (LB)Character max 12 enclosed in, and not containing, double quotation marks. Colour-mark (ring or flag) codes for left leg below tarsus. See Appendix H for field content. Leg flags are unconventional marks and require special permission for use.
84 Right leg below tarsus colour mark (RB)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark (ring or flag) codes for right leg below tarsus. See Appendix H for field content. Leg flags are unconventional marks and require special permission for use.
85 Left leg above tarsus colour mark (LA)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark (ring or flag) codes for left leg above tarsus. See Appendix H for field content. Leg flags are unconventional marks and require special permission for use.
86 Right leg above tarsus colour mark (RA)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark (ring or flag) codes for right leg above tarsus. See Appendix H for field content. Leg flags are unconventional marks and require special permission for use.
87 Neck collar colour mark (NC)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark codes for neck collar. See Appendix H for field content. Neck Collars are unconventional marks and require special permission for use.
88 Left wing colour mark (LW)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark codes for left wing. See Appendix H for field content. Wing tags are unconventional marks and require special permission for use.
89 Right wing colour mark (RW)Character max 12, enclosed in, and not containing, double quotation marks. Colour-mark codes for right wing. See Appendix H for field content. Wing tags are unconventional marks and require special permission for use.
90 Nasal colour mark (NA)Character max 12, enclosed in, and not containing, double quotation marks. Not in use currently – reserved for future. Colour-mark codes for nasal tag or saddle. See Appendix H for field content. Nasal tags and saddles are unconventional marks and require special permission for use.
91 Sample (SAMPLE$)Character = 1Used to indicate the sample of birds processed. ERAJCO
Everything Random sampleAdults onlyJuveniles onlyReCaptures only (controls and retraps),Other non-random sample
92 Time of nearest high tide (HTTIME%)Numeric max 4. Time of the nearest high tide being the nearest one within six hours of the current time (catch).24-hour clock, hours and minutes, eg2026.
93 Fat score method (FATMTD$)Character = 1.Code to indicate method used for FAT SCORE (Field 58)B Biometrics Working GroupE ESFRequired if a Fat Score is given at field 58.
94 Finder (FINDER$)Character max 100, enclosed in (and not including) double quote marks.Finders’ name, address and postcode if not same as submitting ringer. Commas to be used to delimit lines in the name, address and postcode with a maximum of 30 characters between commas. Between three and seven commas to be present ie between four and eight lines in a name/address/postcode. No spaces after commas. Only normal display characters. Must not be more than 100 characters in length.
Only to be used for Record types X, 9, O, S, 8, A, P
95 IPMR Observation Bird Identifier (OBSERVATIONBIRDID)Character max 18.
A unique code for the submitting permit number identifying the individual bird. Up to 18 Characters in length composed of Character, numeric or the forward slash (/) character.Only to be used for CAPTURETYPE O and F. It will be used on an F record when providing first ringing details of a submitted Observation. Stored on BTO ORACLE database as separate field to ORACLE Bird Identifier.
96 Project Code 1 (PROJECTTYPE)Character max 3.A code to identify the BTO/Euring project of which this capture forms part. The value must be one of those in the list of valid project codes listed below together with the species codes valid for the project:SRP Swallow Roost Project SWALL
97 Project Registration 1 (PROJECTREGISTRATION)Numeric max 8.A registration number or code unique to the ringer or group for the project identified in the Project Code 1 field (96). The format of the registration number or code are given in the example below (where 9 is a mandatory numeric; 0 is optional numeric:
eg 0009 Note: if it is max 8, why 4 digits here??98 Project Code 2 (PROJECTTYPE)
Character max 3.A code to identify the BTO/Euring project of which this capture forms part. The value must be one of those in the list of valid project codes listed under Project Code 1 field 96.
99 Project Registration 2 (PROJECTREGISTRATION)Numeric max 8.A registration number or code unique to the ringer or group for the project identified in the Project Code 1 field (96). The valid formats for this field are given under Project Registration field 97.
100 Project Code 3 (PROJECTTYPE)Character max 3.A code to identify the BTO/Euring project of which this capture forms part. The value must be one of those in the list of valid project codes listed under Project Code 1 field 96.
101 Project Registration 3 (PROJECTREGISTRATION)Numeric max 8.A registration number or code unique to the ringer or group for the project identified in the Project Code 1 field (96). The valid formats for this field are given under Project Registration field 97.
102 Body moult code (BODYMOULT)Numeric = 1.A code to record the degree of body moult present in a bird. Single code from following list:01
No body feathers growing.A few body feathers growing: up to about 20 growing feathers.
2 Many body feathers growing (more than about 20). This includes feathers growing due to the completion of the juvenile plumage in birds just after fledging.
103 Tail Fork length (TAILFORK)Numeric(real)max 4.The distance between the tip of the shortest innermost and the longest outermost tail-feather to 0.5 mm. (up to 2 digits in length, plus, if appropriate, decimal point and fraction digit). Decimal point and fraction digit are optional and if missing does not imply reduced accuracy. A zero (0) need not be present before the decimal point if the figure is less than 10 mm. A hyphen (-) charatcer may be present immediately preceding the left most number to indicate a negative tail fork (i.e rounded tail shape).
104 Extractor Initials (EXTRACTINIT)Character max 3.Extractors initials in uppercase.
105 Ringer Initials (RINGINIT)Character max 3.Ringers's initials in uppercase.
106 Checker Initials (CHECKINIT)Character max 3.Checker's initials in uppercase.
107 Nest Recorder Observer Code (NRNO)Character min 2 max 4.Codes must be 2, 3 or 4 digits long, can be any alphabetic or numeric character or the / or & characters.
108 Nest Record number (NRCNO)Numeric max 6.Nest record number, optionally with leading zeroes.
109 Euring Species CodeNumeric max 5.Not loaded into ORACLE from submission files.Euring Species Code from list in Species table of IPMR. Not used by BTO.
110 Sibley-Monroe Species Code Numeric max 6.Not loaded into ORACLE from submission files.Sibley-Monroe Species Code. Not used by BTO.
111 CES subsite type Character = 1.Code to identify status of subsite for CES use.SAX
112 Secondaries moult scores (SSMLT)Character max 40.Between nine and forty moult scores for individual secondary and tertial feathers, in sequence from the middle of wing inwards, towards body: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new.
113 Tail Moult scores (TAILMLT)Character max 20. Between five and twenty moult scores for individual tail feathers, in sequence from the centre of tail outwards: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new.
114 Primary covert moult scores (PCMLT)Character max 20. Between ten and twenty moult scores for individual primary covert feathers, in sequence from the middle of wing outwards, away from body: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new. Final value can be X for outer diminutive feather.
115 Greater covert moult scores (GCMLT)Character max 40. Between nine and forty moult scores for individual greater covert feathers, in sequence from the middle of wing inwards, towards body: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new.
116 Carpal covert moult scores (CCMLT)Character = 1.Moult score for carpal covert feather: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for feather. Use code U for feathers where unknown if old or new.
117 Alula moult scores (ALULAMLT)Character = 3.Three alphanumeric moult scores for individual alula feathers, in sequence from the inner wing outwards, away from body: 0 (zero, not letter O) for old to 5 (not letter N) for full grown new, V for very old, for each feather. Use code U for feathers where unknown if old or new.
118 Left wing primary moult scores (LPPMLT)Character= 20As 44 for left wing.
119 Left wing Secondaries moult scores (LSSMLT)Character = 40As 112 for left wing.
Code for representative state of upperpart moult.02345U
All oldBeginningMiddleEndingAll newUncertain
129 Underparts moult (UNPMLT)Character = 1.Code for representative state of underpart moult.02345U
All oldBeginningMiddleEndingAll newUncertain
130 BTO Record Identifier (RECORD_ID)Character max32.Not populated for submission files to BTO.This field is set in the BTO ORACLE Database and will not be changed even if a correction is made to the record. It is present in the Electronic Recovery History (ERH) downloads, which are imported back into IPMR from the BTO ORACLE Database.
131 Edit_Flag (EDIT_FLAG)Numeric = 1.Not populated for submission files to BTO.This field is set to zero in the BTO ORACLE Database when a new record is added. If a correction is made to a record then this value will be incremented by one for each change. The value is used during import back into IPMR to decide whether the record is new, needs to overwrite an existing record or should just be skipped.
132 Moved by (MOV)Character = 2.Not populated for submission files to BTO.One code from the following list:WA Moved by waterMI Moved intentionally by manUI Moved unintentionally by manMO Moved by other agency-- Not moved or not recorded
Only valid for Record Types A, X and 9.
133 Finding Circumstances Presumed (FCP)Character = 1. Not populated for submission files to BTO.One code from the following list:P presumedNull
134 BTO Extra Text (BTOEXTRATEXT)Character max 80, enclosed in but not containing double quotation marks.Not populated for submission files to BTO.Text describing additional ringing or finding information entered by BTO staff (normally during recovery processing). Valid for all record types. For ERH finding information is generated by concatenating FXT1 and FXT2 (each max 40 characters) with a space to separate each field of text. For ringing information it uses RXT (max 40 characters).
135 Ring Number Verified (RNV)Character = 1.Not populated for submission files to BTO.Single code ‘V’ added by BTO during processing of record types X & 9 only, where the ring number has been sent in and verified.
136 Identification Verified (IDV)Character = 3Not populated for submission files to BTO.One code from following list added by BTO during recovery processing to indicate whether the finder verified identification of the species or not:SPV - Species VerifiedGPV - Group Verified (e.g finder says bird was a Raptor or Gull)SSV - Subspecies VerifiedSPX - Species changed (e.g ringing in mixed Gull colony, where bird is
subsequently recovered as for example a Herring Gull rather than L B B Gull)
SSX - Subspecies changedGPX - Group changed.--- - Unknown
137 BTO Finder (BTOFINDER)Character = 100Not populated for submission files to BTO.Populated during ERH download to provide details of the finder. If a ringer then format is:Name (permit), Email Addresse.g Bridget Griffin (4711), [email protected] a MOP finder then the name and address (if recorded) separated by commas is sent back (Intermediate ringers do not receive the address).
138 Reporter (REPORTER)Character = 45Not populated for submission files to BTO.This name is added by BTO during recovery processing if the bird has been reported by a MOP or another ringer via the ringer submitting the report.
139 Submission Flag (SUBM)Character = 3Populated as part of IPMR data submission process, one code from following list:
NOT – i.e ‘not yet submitted’ (so the first submission of this record to BTO).RES - used if data is being resubmitted to BTO.YYN - Where YY is the two digit year code (eg 05 for 2005) and N is the file sequence number (eg 1 for first file for that year). This flag will come in where a submission file has had to be re-created.
140 Captures Key (CAPTURESKEY)Numeric =7This is the unique reference within an IPMR database to a bird capture. The key starts at 1 and is added sequentially. This field will be picked up by ORACLE during data loading and along with the submission flag field (139), will assist with identifying if a correction is being submitted by the ringer.
141 Submission Finding Circumstance Code (CIRCUMSTANCE)Character = 2Loaded into ORACLE from submission files created from 3.40 Spec or later, only for following ‘Trusted’ finding circumstances:
20 Intentionally Taken27 At Nest Box/Artificial Site28 Metal Ring Read in Field29 Colour Mark Record81 Identified from Leg Ring(s)82 Identified from Neck Ring(s)83 Identified from Wingtags84 Identified with Radio Tracking85 Identified with Satellite Tracking86 Identified from Transponder
Record Types R,1,2,3,C,4,5,6 – Circumstance Codes 20 or 27Record Types O,S,8 – Circumstance Codes 28,29,81,82,83,84,85 or 86
Otherwise the correct Circumstance code is entered by BTO based on the text in Submission Extra Text field (63).
Spain Madrid (SEO) ESMSan Sebastian ESA+ Seville (Biol. Donana) ESEMadrid (Icona) ESI
Sweden Stockholm Museum SVS
Switzerland Sempach HES
UK & Ireland London (Brit. Museum/Thetford) GBT
Ukraine Kiev UKK
Yugoslavia Beograd YUB
NON-EUROPEAN SCHEMES
Angola Luanda ALLAustralia Canberra AACBrazil Brasilia BABCanada Washington NAWChina Bejing CPBEgypt Cairo EGCGhana Legon GHLHong Kong Hong Kong CGH +India Bombay INBIraq Bagdad Univ. IQBIran Teheran IPTIsrael Tel-Aviv Univ. ILTJapan Yamashina Inst. O.Z. JHYJordan Jordanie JO.Kazakstan Almaty KZAKenya Nairobi GPNMalaysia Kuala Lumpur FVKNew Zealand Wellington AJWNigeria Jos NVJ +Pakistan Lahore PNL +Philippines … OE +USA Washington NAWSaudi Arabia Rhyiad ARRSouth Africa Pretoria/Cape Town FPPSouth Korea Korea TXSTaiwan Taipei CXTTunisia Tunis TOT +Turkey Ankara University TUA
1237 RIVWA River Warbler 26 SOPPE Soft-plumaged Petrel1099 ROBIN Robin 552 SOLSA Solitary Sandpiper1860 ROCBU Rock Bunting 1835 SONSP Song Sparrow665 ROCDO Rock Dove 1200 SONTH Song Thrush
1014 ROCPI Rock Pipit 43 SOOSH Sooty Shearwater1604 ROCSP Rock Sparrow 623 SOOTE Sooty Tern1162 ROCTH Rock Thrush 409 SORA. Sora841 ROLLE Roller 1520/3 SOGSH Southern Grey Shrike
*DEST RING DESTROYED*LOST RING LOST*MISS RING MISSING*UNKN RINGING DATA LOST****1 Rarity code unknown (comment must be added in extra text)HYBRI Hybrid species
NB + indicates code derived in non-standard manner
grasslandA6 Mixed broadleaved & coniferous water-logged E3 Mixed grass/tilled land
E4 Tilled landB SCRUBLAND (or very young woodland less than 5m tall)
E5 Orchard
E6 Other farmingB1 Regenerating natural or semi-natural woodlandB2 Downland (chalk) F HUMAN SITESB3 Heath scrubB4 Young coppice F1 UrbanB5 New plantation F2 SuburbanB6 Clear-felled woodland, with or without new
saplingsF3 Rural
B7 OtherG WATER BODIES (freshwater)
C SEMI-NATURAL GRASSLAND & MARSHG1 Pond (less than 50m2)
C1 Chalk downland G2 Small water-body (50-450m2)C2 Grass moor (unenclosed) G3 Lake/unlined reservoirC3 Grass moor mixed with heather (unenclosed) G4 Lined reservoirC4 Machair G5 Gravel pit, sand pit, etc.C5 Other dry grassland G6 Stream (less than 3m wide)C6 Water-meadow/grazing marsh G7 River (more than 3m wide)C7 Reed swamp G8 Ditch with water (less than 2m
wide)C8 Other open marsh G9 Small canal (2-5m wide)C9 Saltmarsh GA* Large canal (more than 5m
wide)
D HEATHLAND & BOGS H COASTAL
D1 Dry heath H1 Marine - open shoreD2 Wet heath H2 Marine shore - inlet/cove/lochD3 Mixed wet/dry heath H3 EstuarineD4 Bog H4 Brackish lagoonH5 Open sea I6 Mine/spoil/slag heap
J MISCELLANEOUSI1 Cliff J1 OtherI2 Scree/boulder slopeI3 Limestone pavement * Note: code GA differs from theI4 Other rock outcrop Nest Record Scheme code (G10) I5 Quarry for this habitat.
ENGLANDBath and N. E. SomersetBedfordshireBlackburn with DarwenBlackpoolBournemouthBracknell ForestBrighton & HoveBristolBuckinghamshireCambridgeshireCheshireCornwallCumbriaDarlingtonDerbyDerbyshireDevonDorsetDurhamEast Riding of YorkshireEast SussexEssexGloucestershireGreater LondonGreater ManchesterHaltonHampshireHartlepoolHerefordshireHertfordshireIsle of ManIsle of WightIsles of ScillyKentKingston upon HullLancashireLeicesterLeicestershireLincolnshireLutonMedwayMerseysideMiddlesbroughMilton KeynesNorfolkNorth East LincolnshireNorth LincolnshireNorth SomersetNorth YorkshireNorthamptonshire
REGION South WestEast of EnglandNorth WestNorth WestSouth WestSouth EastSouth EastSouth WestSouth EastEast of EnglandNorth WestSouth WestNorth WestNorth EastEast MidlandsEast MidlandsSouth WestSouth WestNorth EastYorkshire and The HumberSouth EastEast of EnglandSouth WestLondonNorth WestNorth WestSouth EastNorth EastWest MidlandsEast of EnglandIsle of ManSouth EastSouth WestSouth EastYorkshire and The HumberNorth WestEast MidlandsEast MidlandsEast MidlandsEast of EnglandSouth EastNorth WestNorth EastSouth EastEast of EnglandEast MidlandsYorkshire and The HumberSouth WestYorkshire and The HumberEast MidlandsNorth East
NorthumberlandNottinghamNottinghamshireOxfordshirePeterboroughPlymouthPoolePortsmouthReadingRedcar & ClevelandRutlandShropshireSloughSomersetSouth GloucestershireSouth YorkshireSouthamptonSouthendStaffordshireStockton-on-TeesStoke-on-TrentSuffolkSurreySwindonTelford and WrekinThurrockTorbayTyne and WearWarringtonWarwickshireWest BerkshireWest MidlandsWest SussexWest YorkshireWiltshireWindsor and MaidenheadWokinghamWorcestershireYork
East MidlandsEast MidlandsSouth EastEast of EnglandSouth WestSouth WestSouth EastSouth EastNorth EastEast MidlandsWest MidlandsSouth EastSouth WestSouth WestYorkshire and The HumberSouth EastEast of EnglandWest MidlandsNorth EastWest MidlandsEast of EnglandSouth EastSouth WestWest MidlandsEast of EnglandSouth WestNorth EastNorth WestWest MidlandsSouth EastWest MidlandsSouth EastYorkshire and The HumberSouth WestSouth EastSouth EastWest MidlandsYorkshire and The Humber
PositionEach leg bone can have up to four colour marks attached. Wing and neck up to two. Each of these body parts are known as positions. Marks are always recorded from the top down. The reading of any digits eg BIN should be from left to right as if they were the letters from a word. The orientation of the writing on the ring whether it goes round, up or down should not affect the code. In the Submission file the position codes mentioned below are not included as the position is indicated by the field in the submission record. The colour mark codes are also enclosed in double quotation marks.
KK3BTO
The first two characters denote the position LB: left below the inter-tarsal joint ("knee"), LA: left above, RB: right below, RA: right above, NC: Neck collar, RW: right wing tag, LW: left wing tag. NS: Nasal tags and saddles. Note that special permission is required to use unconventional marks (ie anything other than conventional colour rings), please contact the Ringing Unit for details.
The colour marks at each position are listed from top down separated by commas (,). So for yellow over BTO ring on the right leg on the tarsus (below the tarsal joint) we have RBY,M.
BTO437
If colour marks are on multiple positions each position code is separated by a semicolon eg LAG,Y;RAP,M .
Inscriptions (including digits, bands and wasp rings)
recorded after the mark's colour code in parentheses. The colour of the digits is required this is recorded as the second colour of a two colour code eg a Green darvic with Black digits on a Gull's left tarsus with code XSL would be LBGN(XSL);RBN,M when the black over BTO position is added. If there are bars around the ring then these are recorded using the forward slash (/) symbol. Example 1: letter R separated from letter B by a bar (all black) round a white ring (on the left tarsus) would be LBWN(R/B); Example 2: as example 1 except that the bar is replaced by a bar at each end of the ring would be LBWN(/RB/).
If a two-colour mark is used with different colour digits on each it should be recorded as two marks; if they are the same colour then see below under two colour marks.
To record a tall ring a suffix code of T is used.
For ‘Wasp’ rings with positional bands on a (tall) ring a suffix of a hash (#) is used; the wasp bands are recorded as for inscriptions except that the only characters allowed are 0 for ‘no band’, 1 for thin band and 2 for ‘thick band’. For a yellow wasp ring with black bands on the left tarsus with a thin band over a thick band over ‘no band’ is coded LBY#N(120).
Leg Flags Note: Special permission is required to use leg flags as they are an unconventional mark, please contact the Ringing Unit for details.To record leg flags a suffix code of F is used. eg LBRF is a red flag on the left tarsus.
Nasal tags and saddles Note: This field is not currently in use. Special permission is required to use nasal tags or saddles as they are unconventional marks, please contact the Ringing Unit for details.Nasal tags and saddles are both recorded using the NS position code. Nasal saddles follow the standard convention eg NSRB(QQ) for a Red Nasal Saddle with a Blue "QQ" inscription. Nasal tags always come in pairs and are treated as two marks on the same position with the tag on the bird’s right side being recorded first. Tags also have a shape which is recorded after the colour code within square parentheses. Tag shape codes are: square [Q], rectangle [R], triangle [T], circle [C], hexagon [H], octagon [O], star [S]. For a bird with a red, square tag on the right and green circular tag on the left the coding is NSR[Q],G[C].
Marks with two colours (on one ring, tag or flag).For two-colour marks a number after the colour indicates the type. Blank is the default for a single colour, 2 for narrow (multiple stripes of each colour) stripes and 3 for thick (one stripe of each colour) stripes. eg RAPC2,M for a Pale Blue/Dark Pink narrow striped ring over BTO metal. The top colour, if applicable, should be the first letter of the code. If a striped colour mark has digits inscribed that are all the same colour then the colour code of the digits follows the colour codes for the ring. eg a white and green thick striped neck collar with dark blue digits XYZ would be recorded as NCWG3B(XYZ).
NCY(RTY)
RTY
Colour codes for colour marks
R Red P Pale BlueW White O OrangeG Green (dark) C Dark Pink (Carmine)L Light Green (Lime) K Light PinkN Black (Niger) B Blue (dark)M BTO Metal Ring V Violet/Mauve/PurpleY Yellow S Silver/GreyU Brown (Umber) A Any other metal ring