Difference between revisions of "RADAR"
(→SUBWINDOW_RESULT) |
(→Introduction) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | === Description of tables in RADAR schema in | + | === Description of tables in RADAR schema in e-Ecology database === |
Data model for Motion Analyses images collected with ROBIN-system for the Medium Power Radar | Data model for Motion Analyses images collected with ROBIN-system for the Medium Power Radar | ||
| Line 6: | Line 6: | ||
=Introduction= | =Introduction= | ||
| − | Radar data are one of the most important measurements in Bird Avoidance System (BAS) and | + | Radar data are one of the most important measurements in Bird Avoidance System (BAS) and FlySafe project. Until now data are archived in structured files instead of in a database. In this document data model for Motion Analysis images of the ROBIN4 system is designed, based on file structure of ROBIN4-MA images as defined in High Level Design Document of ROBIN4 (HLDD, TNO 2006). |
MA (Motion Analysis) images are summated images of ten radar antenna rotations and are recorded twice per hour, two radar beams per radar, 3 radars in total (equalling 12 images per hour). | MA (Motion Analysis) images are summated images of ten radar antenna rotations and are recorded twice per hour, two radar beams per radar, 3 radars in total (equalling 12 images per hour). | ||
| − | The data comprise all recorded radar echoes with summated intensities, plus rain clutter masks, land clutter masks and all separate objects of all recognised tracks. The huge amount of data per image (360°, 150km range, 10Mb) require a flexible database. Numbers of tracks can be as high as 15.000 tracks per image, with a mean about 1000 tracks. Per day we collect 48 images * 2 beams * 10Mb * 3 radars equipped with Robin | + | The data comprise all recorded radar echoes with summated intensities, plus rain clutter masks, land clutter masks and all separate objects of all recognised tracks. The huge amount of data per image (360°, 150km range, 10Mb) require a flexible database. Numbers of tracks can be as high as 15.000 tracks per image, with a mean about 1000 tracks. Per day we collect 48 images * 2 beams * 10Mb * 3 radars equipped with Robin 3Gb data. |
| − | Because the database must be readily and speedily accessible, only aggregated data can be recorded in the database. Original data will have to be recorded in a file system. The level of aggregation is still under debate, as the database should also allow a certain level of reanalysis. It is not desirable to store all original recorded echoes and raw radar data, which are the bulk of the data, in the database. Because the number of tracks is rather low ( | + | Because the database must be readily and speedily accessible, only aggregated data can be recorded in the database. Original data will have to be recorded in a file system. The level of aggregation is still under debate, as the database should also allow a certain level of reanalysis. It is not desirable to store all original recorded echoes and raw radar data, which are the bulk of the data, in the database. Because the number of tracks is rather low (1000) for most of the images, it may be sufficient to store summaries of each track. This will lead to an estimated data reduction of 90%. |
In the near future, already during precursor phase of FlySafe project, bird echo tracks will be recorded continuously. This means that if we want to store individual tracks, also positions of each antenna rotation is stored and database could be increasing much faster than it does now. | In the near future, already during precursor phase of FlySafe project, bird echo tracks will be recorded continuously. This means that if we want to store individual tracks, also positions of each antenna rotation is stored and database could be increasing much faster than it does now. | ||
| − | |||
| − | |||
| − | |||
=Data model for MA images collected by ROBIN4 system .= | =Data model for MA images collected by ROBIN4 system .= | ||
| Line 319: | Line 316: | ||
|OBJECT_PHI||Array of phi coordinate of object | |OBJECT_PHI||Array of phi coordinate of object | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[ Image : Radar_datamodel.png ]] | [[ Image : Radar_datamodel.png ]] | ||
Latest revision as of 10:23, 22 February 2018
Contents
Description of tables in RADAR schema in e-Ecology database
Data model for Motion Analyses images collected with ROBIN-system for the Medium Power Radar
Originally Hans van Gasteren, May 2007
Introduction
Radar data are one of the most important measurements in Bird Avoidance System (BAS) and FlySafe project. Until now data are archived in structured files instead of in a database. In this document data model for Motion Analysis images of the ROBIN4 system is designed, based on file structure of ROBIN4-MA images as defined in High Level Design Document of ROBIN4 (HLDD, TNO 2006). MA (Motion Analysis) images are summated images of ten radar antenna rotations and are recorded twice per hour, two radar beams per radar, 3 radars in total (equalling 12 images per hour). The data comprise all recorded radar echoes with summated intensities, plus rain clutter masks, land clutter masks and all separate objects of all recognised tracks. The huge amount of data per image (360°, 150km range, 10Mb) require a flexible database. Numbers of tracks can be as high as 15.000 tracks per image, with a mean about 1000 tracks. Per day we collect 48 images * 2 beams * 10Mb * 3 radars equipped with Robin 3Gb data. Because the database must be readily and speedily accessible, only aggregated data can be recorded in the database. Original data will have to be recorded in a file system. The level of aggregation is still under debate, as the database should also allow a certain level of reanalysis. It is not desirable to store all original recorded echoes and raw radar data, which are the bulk of the data, in the database. Because the number of tracks is rather low (1000) for most of the images, it may be sufficient to store summaries of each track. This will lead to an estimated data reduction of 90%. In the near future, already during precursor phase of FlySafe project, bird echo tracks will be recorded continuously. This means that if we want to store individual tracks, also positions of each antenna rotation is stored and database could be increasing much faster than it does now.
Data model for MA images collected by ROBIN4 system .
RADAR
The radar table contains details for the different radars.
| RADAR_ID | unique radar id |
| RADAR_NAME | logical name |
| LATITUDE | degrees |
| LONGITUDE | degrees |
| X_POSITION | in meters, rijksdriehoekmeting |
| Y_POSITION | in meters, rijksdriehoekmeting |
| Z_POSITION | In meters, rijksdriehoekmeting |
| ALTITUDE_ANTENNA | In meters with respect to sea level |
| Radar type: | |
| MIN_RANGE | In meters |
| MAX_RANGE | In meters |
| RANGE_RESOLUTION | In meters, normal MPR 30m |
| AZIMUTH_RESOLUTION | In radials azimuth if horizontal radar else elevation |
| REVOLUTION_TIME | In seconds, normal MPR 10s |
| Transmitter: | |
| MEAN_CARRIER_FREQUENCY | In GigaHz |
| PEAK_POWER | In dB |
| PULSE_LENGTH | In μS |
| PULSE_REPETITION_FREQUENCY | In Hz |
| Antenna: | |
| TYPE | circ, rectangular, omni |
| VERTICAL_ILLUMINATION | uniform, parabolic, parabolic², cosec² |
| POLARISATION | (horizontal, vertical, circular) |
| TRANSMITTER_GAIN | In dB |
COVERAGE_DIAGRAM
(for each azimuth horizontal elevation is given).
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| COVDIAG_ID | |
| AZIMUTH | Radians (0-2PI) |
| ELEVATION | Radians |
BEAM
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | |
| BEAM_NAME | |
| BEAM_ELEVATION | Elevation of beam (radians) |
| EL_BEAMWIDTH | Beam width (radians) in elevation |
| AZ_BEAMWIDTH | Beam width (radians) in azimuth |
IMAGE_REQUEST
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | Reference to BEAM_ID of table BEAM |
| IMAGE_REQUEST_ID | |
| WINDOW_MIN_RANGE | Measurement range (m) of window |
| WINDOW_MAX_RANGE | meters |
| WINDOW_MIN_AZIMUTH | radials |
| WINDOW_MAX_AZIMUTH | radials |
| Motion_analysis_parameters | Note: for CMA different |
| RAIN_CLUTTER_MODE | Automatic, off, on |
| LAND_CLUTTER_MODE | Automatic, off, on |
| DETECTION_METHOD | Peak detection, threshold |
| MIN_TRACK_MEMBERS | 2 ..10 |
| ALLOWED_INTERVAL | 0..9 |
| MIN_MEMBER_SIZE | 1..? |
| MIN_SPEED | 5..50 |
| MAX_SPEED | 5..50 |
| ALLOWED_SPEED_DEFLECTION | 5..50 |
| TANGENTIA_SPEED_DEVIATION | … part of score function |
| RADIAL_SPEED_DEVIATION | … part of score function |
| MASS_DEVIATION | … part of score function |
| BONUS_SCORE_PROBABILITY | … part of score function |
| PATH_FRACTION_THRESHOLD | … part of score function |
| RELAXATION_FACTOR | 0.0..1.0 … part of score function |
| RANGE_RESOLUTION | Correction with respect to default range resolution |
| AZIMUTH_RESOLUTION | Correction with respect to default azimuth resolution |
SUBWINDOW
The subwindow table specifies size and location of subwindows
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | Reference to BEAM_ID of table BEAM |
| IMAGE_REQUEST_ID | Reference to IMAGE_REQUEST_ID of table IMAGE_REQUEST |
| SUBWINDOW_ID | |
| SUBWINDOW_MIN_RANGE | meters |
| SUBWINDOW_MAX_RANGE | meters |
| SUBWINDOW_MIN_AZIMUTH | radials |
| SUBWINDOW_MAX_AZIMUTH | radials |
IMAGE_RESULT
The IMAGE_RESULT table contains references to actual images that have been recorded with the radar at different timestamps. For the Medium Power Radar normally every half hour such an image is generated. So for one RADAR/ BEAM we can expect 17520 such images a year.
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | Reference to BEAM_ID of table BEAM |
| IMAGE_REQUEST_ID | Reference to IMAGE_REQUEST_ID of table IMAGE_REQUEST |
| IMAGE_RESULT_ID | |
| ACQUISITION_TIME | Date and time of request |
| ERROR_STATUS | Status given back by Robin-system |
| CORRECTION_LEVEL | False alarm rate, FAR correction factor, important value, should have own graphical representation through out the year and correlate with the weather conditions |
| NR_OF_TRACKS | Number of tracks in image |
| RAIN_MASK | Rain clutter mask. Area were bird detection is switched off |
| LAND_MASK | Land clutter mask. No bird detection has been achieved in this area |
| IMAGE | Jpeg image of data (high resolution ) or georef TIFF |
SUBWINDOW_RESULT
The SUBWINDOW_RESULT table contains values for all the subwindows and for each image_result and contains some computed values where the most notable is the ROBIN_CORRECTED_DENSITY which is a measure of the bird density that can be used for warnings such as the BirdTam
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | Reference to BEAM_ID of table BEAM |
| IMAGE_REQUEST_ID | Reference to IMAGE_REQUEST_ID of table IMAGE_REQUEST |
| IMAGE_RESULT_ID | Reference to IMAGE_RESULT_ID of table IMAGE_RESULT |
| SUBWINDOW_ID | Reference to SUBWINDOW_ID of table SUBWINDOW |
| AREA | (km²) |
| LAND_CL_PERC | % land clutter in image |
| RAIN_CL_PERC | % rain clutter in image |
| CLUTTER_PERC | % land or rain clutter in image |
| TOTAL_MASS_DENSITY | Total mass density per km², before MA |
| LAND_MASS_DENSITY | Mass density per km², after MA in land clutter mask |
| RAIN_MASS_DENSITY | Mass density per km², after MA in rain clutter mask |
| CLUTTER_MASS_DENSITY | Mass density per km², after MA in rain or land clutter mask |
| BIRD_MASS_DENSITY | Mass density per km² of bird tracks |
| BIRD_ECHO_DENSITY | Mean bird echo density per km² |
| BIRD_MEAN_DIRECTION | Mean direction of all bird tracks in sub-window (radians) |
| BIRD_MEAN_SPEED | Mean speed of all bird tracks in sub-window (m/s) |
| MEAN_SPEED_VECTOR_RHO | Mean speed value added as vector |
| MEAN_SPEED_VECTOR_PHI | Mean speed direction added as vector |
| MEAN_BIRD_VECTOR | ( sum(cos(alpha[i]) )^2 + sum(sin(alpha[i]) )^2 ) / n |
| STANDARD_DEVIATION_BIRD_SPEED | standard deviation BIRD_MEAN_SPEED |
| N | Number of echos in subwindow |
| ROBIN_CORRECTED_DENSITY | Corrected density |
| ROBIN_CORRECTED_QUALITY | Quality parameter associated with the ROBIN_CORRECTED_DENSITY |
The BIRD_MEAN_DIRECTION is the directional mean of the direction of all bird tracks in the subwindow. ( atan2(sum(sin(direction)) / N, sum(sin(direction)) / N) )
The BIRD_MEAN_SPEED is just the average speed of the birds in the subwindow. The STANDARD_DEVIATION_BIRD_SPEED is the standard deviation for this BIRD_MEAN_SPEED.
The MEAN_BIRD_VECTOR is a measure of whether the birds fly in the same direction. MEAN_BIRD_VECTOR = SQRT(sum(sin(direction)) /N + sum(cos(direction)) /N)
If this value is 1 they all fly in the same direction. If it is zero they all fly in opposite directions.
In addition the mean speed is also calculated as vector with the results in rho and phi in MEAN_SPEED_VECTOR_RHO and MEAN_SPEED_VECTOR_PHI.
Details for the calculations of the ROBIN_CORRECTED_DENSITY and ROBIN_CORRECTED_QUALITY are in Robin subwindow density/quality_calculations.
TRACK_RESULT
The TRACK_RESULT table contains tracks of birds that have been detected by the ROBIN4 system. It also contains as arrays all the different points in a track data. That data used to be in the TRACK_OBJECT table. The TRACK_RESULT table is a master table and the real data is contained in the inherited tables TRACK_RESULT<YEAR><MONTH>. Otherwise the TRACK_RESULT table would become too big.
| RADAR_ID | Reference to RADAR_ID of table RADAR |
| BEAM_ID | Reference to BEAM_ID of table BEAM |
| IMAGE_REQUEST_ID | Reference to IMAGE_REQUEST_ID of table IMAGE_REQUEST |
| IMAGE_RESULT_ID | Reference to IMAGE_RESULT_ID of table IMAGE_RESULT |
| TRACK_RESULT_ID | |
| DATE_TIME | Starttime (date + time) of track (for MA equal to ACQUISITION TIME, for CMA different) |
| TRACK_RANGE | Start position of track (m) |
| TRACK_AZIMUTH | Start position of track (radians) |
| TRACK_MASS | Mean mass of bird track |
| TRACK_SPEED | Mean speed of bird track (m/s) |
| TRACK_DIRECTION | Mean direction of bird track (radians) |
| TRACK_OBJECTS | Number of objects in track (0 – 10) |
| TRACK_SOURCE | MA / CAM |
| OBJECT_LATITUDE | Array of latitude position of object |
| OBJECT_LONGITUDE | Array of longitude position of object |
| OBJECT_MASS | Array of mass (reflection) of object |
| OBJECT_SIZE | Array of size of object |
| OBJECT_RHO | Array of rho coordinate of object |
| OBJECT_PHI | Array of phi coordinate of object |
