The National Archives - link to home page    

Saturday 22 November

 

Main website navigation:

   
 
 NDAD: The National Digital Archive of Datasets
Welcome (home page) About NDAD Users Contributors  
Search Browse News Help (new window)  
 
 

Table details: CRDA/17/DS/1/1/1

Bat Data (BATDATA)

 
 
Quick reference Full details Order copies
Search this table Download as CSV
 
  View in hierarchy
 

Jump to :  Context  |  Summary  |  Identity statement  |  Description  |  Fields  | 

Context

AH/17  Nature Conservation Departments
  CRDA/17  British Bats
  CRDA/17/DS/1  English Nature
  CRDA/17/DS/1/1  1999 snapshot
 
Top of pagetop of page

Summary

Title Bat Data
NDAD reference CRDA/17/DS/1/1/1
Scope & content Main file holding information on bat enquiries, roosts etc
Access conditions

The following fields are closed:

  • SITE_NAME - until 2025
  • GREF - until 2025
  • LOCALITY - until 2025
  • ADDRESS - until 2025
  • VISITORS - until 2025
  • NOTES - until 2025
  • SURNAME - until 2025

This record was closed under the Public Records Act or is exempt under the Freedom of Information Act 2000. It is possible to request a review of the information it contains under the Freedom of Information Act 2000 and this will trigger a review. Request review.

You can use the NDAD Query Builder to view and query data in this and other tables in this dataset.

 
Top of pagetop of page

Identity statement

Table name BATDATA
Number of records 22241
SIZE of file (MB) 6.41
Maximum record size (bytes) 1558
ISAD(G) level of description Item
 
Top of pagetop of page

Description

Field descriptions
 
Top of pagetop of page

Fields

Number of fields 28
 

Go to page: . 1 . 2 . 3 . . next page. final page

1
Field name: BATKEY
Data type: Positive Integer
Original description: Keyfield - sequential number
Further descriptive information:

Unique identifier of the record; the key to the file. The first 2 numbers in the key are the region number ie the region which entered the record (the region number and name are held in the COUNTIES table); the remainder are a unique sequential number.

Records in which the BATKEY starts with the digits '99' were entered by the EN Ecologist who developed/administered the Bats database. When a copy of the BATDATA system is first installed in a region, a maintenance facility is run to set the regional code. The key numbers (BATKEY) assigned to records begin with the number of the region. {Maximum length 6}

Missing value(s): [not permitted for this field]
Attributes:
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
2
Field name: ALTERED
Data type: Date as Fixed Length String (length 10)
Original description: Date record added or edited
Further descriptive information:

This field is updated whenever the record is altered. This allows the selection, in order to transfer records to English Nature HQ, of all records added or updated since the last transfer. In the Batadata system, dates were held internally as the number of days since December 31st 1967 (day 0)

Missing value(s): [not permitted for this field]
Attributes:
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
3
Field name: OPERATOR
Data type: Variable Length String
Original description: User name of most recent editor of the record
Further descriptive information:

Identification of the user who added or last updated the record

For the ordinary user of the system, the user-id is of the form BAT.XX, where XX is the number of the user's region. Other entries in this field identify the user ids of individuals (mainly system administrators?). User names also controlled the user environment within the BATDATA system. {Maximum length 10}

Missing value(s): [not permitted for this field]
Attributes:
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
Field name: SITE_NAME
Data type: Variable Length String
Original description: Site name / 1st line of address
Further descriptive information:

{Maximum length 40}

Missing value(s): One or more spaces
Attributes: Anonymised until 2025
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
Field name: GREF
Data type: Variable Length String
Original description: Grid reference for site. This can be 4, 6 or 8 figures
Further descriptive information:

During data entry, the grid reference is validated against the VCOUNTY table, to check that a record for the 10 km square exists in that table and that the county entered for this BATDATA record contains the 10km square defined by the grid reference. {Maximum length 10}

Missing value(s): [not permitted for this field]
Attributes: Anonymised until 2025
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
6
Field name: COUNTY_CODE
Data type: Variable Length String
Original description: County code - use to lookup in COUNTIES
Further descriptive information:

At data entry, the COUNTY_CODE is validated against the COUNTIES table, which holds the codes and names of the Counties. The region code is used to ensure that only the appropriate counties (ie those within the user's region) are presented to the user {Maximum length 6}

Missing value(s): [not permitted for this field]
Attributes:

This field forms a Many - 1 relationship with the following tables:

From CRDA/17/DS/1/1 to COUNTIES (CRDA/17/DS/1/1/2)

via the field CNUMB

Constraints: [As specified by Encoding]
Encoding: This field may only take one of the 67 pre-defined values listed
Codes Values
1Avon
2Cornwall
3Devon
4Dorset
5Somerset
6Berkshire
7Buckinghamshire
8Hampshire
9Oxfordshire
10Isle of Wight
11Wiltshire
12Kent
13Greater London
14Surrey
15East Sussex
16West Sussex
17Cheshire
18Derbyshire
19Gloucestershire
20Hereford & Worcester
21Shropshire
22Staffordshire
23Warwickshire
24West Midlands
25Bedfordshire
26Cambridgeshire
27Hertfordshire
28Leicestershire
29Lincolnshire
30Northamptonshire
31Nottinghamshire
32Essex
33Norfolk
34Suffolk
35Cumbria
36Greater Manchester
37Lancashire
38Merseyside
39South Yorkshire
40West Yorkshire
41Cleveland
42Durham
43Humberside
44Northumberland
45Tyne & Wear
46North Yorkshire
50Dumfries & Galloway
51Strathclyde
52Borders
53Central
54Fife
55Lothian
56Tayside
57Highland
58Western Isles
59Grampian
60Badenoch & Strathspey
61Orkney
62Shetland
70Clwyd
71Gwynedd
72Dyfed
74Powys
76Gwent
77Mid Glamorgan
78South Glamorgan
79West Glamorgan
 
7
Field name: DISTRICT_CODE
Data type: Fixed Length String (length 3)
Original description: District (Local Authority)
Further descriptive information:

At data entry, the DISTRICT_CODE is validated against the LPAS table, which holds the codes and names of the Districts. {Maximum length 6}

Missing value(s): One or more spaces
Attributes:

This field forms a Many - 1 relationship with the following tables:

From CRDA/17/DS/1/1 to LPAS (CRDA/17/DS/1/1/4)

via the field LPA_KEY

Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
Field name: LOCALITY
Data type: Variable Length String
Original description: Locality of site (from OS map) (converted records used the 2nd line of address)
Further descriptive information:

EN have confirmed that for records converted from an earlier system, whatever was in the 2nd line of the address was copied over. For more recent records, the user consults the relevant OS map to identify the locality. {Maximum length 30}

Missing value(s): One or more spaces
Attributes: Anonymised until 2025
Constraints: This field may take any value appropriate to its datatype.
Encoding: [No encoding used]
 
9
Field name: SITE_TYPE
Data type: Variable Length String
Original description: Type of site
Further descriptive information:

At data entry, the SITE_TYPE is validated against the SITE_TYPES table, which holds the code / text for each type of site. {Multi-valued field. Maximum length 16}

Missing value(s): One or more spaces
Attributes:

This field forms a Many - 1 relationship with the following tables:

From CRDA/17/DS/1/1 to SITE_TYPES (CRDA/17/DS/1/1/7)

via the field TYPE_KEY

Constraints: [As specified by Encoding]
Encoding: This field may only take one of the 14 pre-defined values listed
Codes Values
ABridge
BBuilding
CCave
EChurch
FFortification
HHouse
IIce-house
KKiln
LSite lost
MMine
OOther
RRoad/rail tnl.
TTree
WWaterway tunnel
 
10
Field name: ENQTYPE_CODE
Data type: Positive Integer(Byte)
Original description: Enquiry code. Use to lookup in ENQTYPES
Further descriptive information:

At data entry, the ENQTYPE_CODE is validated against the ENQTYPE table, which holds the codes and description of the types of enquiries. {Maximum length 10}

Missing value(s): One or more spaces
Attributes:

This field forms a Many - 1 relationship with the following tables:

From CRDA/17/DS/1/1 to ENQUIRY_TYPES (CRDA/17/DS/1/1/3)

via the field ENQUIRY_KEY

Constraints: [As specified by Encoding]
Encoding: This field may only take one of the 14 pre-defined values listed
Codes Values
1Domestic: no action/information request
2Domestic: persuaded to leave alone
3Domestic: provided with advice under WCA
4Domestic: premature or illegal action
5Domestic: building repairs /alterations
6Domestic: timber treatment/pest control
7Non-domestic: 'lawful activity' defence
8Non-domestic: church with bat problem
9Non-domestic: bats present
10Bat found: alive
11Bat found: dead
12Bat found: ringed
13Domestic: other enquiry/unknown
14Report of bats - not an enquiry
 
 

Go to page: . 1 . 2 . 3 . . next page. final page

Top of pagetop of page

* maximum list length 500

 
 

NDAD v3.0