tids and their effects on hf direction finding 1st techtide user...

TIDs and their effects on HF direction finding

1st TechTIDE User Workshop

Neustrelitz, 15. May 2019

Overview

• TIDs and HF direction finding

• The direction finder

• Measurements

• Processing of measurement results

• Results

2

TID = Travelling Ionospheric Disturbances

(The quality of) HF communication is influenced by thecommunication channel

The communication channel is influenced by the condition of theionosphere

Disturbances of the iononsphere affect the communicationchannel

3

TIDs and HF direction finding

TIDs are influencing the communication channel

Not only the quality of the radio transmission is affected, but direction finding as well!

4

Influence on HF communication

TID TIDIonosphere

Example:

5

Influence on HF direction findingA

zim

uth

Measurement

The German Federal Police operates an HF direction finder closeto Swisttal-Heimerzheim

• Equipped with Plath antennas

• Technology Update by Hensoldt

• Azimuth only, no elevation

The direction finder

6

GFP direction finder – location

Quelle: openstreetmap.org

7

GFP direction finder – location

Map source: openstreetmap.org, Image source: Bundespolizei

8

GFP direction finder – a closer look

Source: maps.google.de9

Source: GFP

GFP direction finder – setup

Source: GFP

Implementation of processing chain:

monitored automatic azimuthfrequencies monitoring values

Measurement details

joblist

azimuthvalues …

11

database query filtered visualizationresults

Measurement details

filteredazimuthvalues

…

12

• Joblist based on HFBC broadcast database

Measurement details – job list

Frequency|Start UTC|Stop UTC|CIRAF - click here to see map|Broadcaster|FMO|Language|Transmitter|Latitude|Longitude|Beam|Power (kW);Days of operation (Sun=1);From date|To date|Notes|

|7295|0000|0130|38NE,39NE,39SW|Abu Dhabi Media Company|ADM|Ara|Dhabayya|24N11|5,40E+15|300|500|1234567|29-Oct-2017|25-Mar-2018|UAE|…|7305|0600|0629|47S,52N,52SE|BBC Worldservice|BAB|Fra|Ascension|07S54|014W23|70|250|1234567|29-Oct-2017|25-Mar-2018|FRENA_CENTRAL|…|5950|0300|1500|39|Yemen Radio & Television|YEM|Und|Sanaa|15N22|4,40E+12 |0|300|1234567|29-Oct-2017|24-Mar-2018||

13

• Generation of task list for direction finder

Measurement details – job list

Id|frequency|start time|stop time|name|location|direction|kW

63761|9405|0000|0030|Far East Broadcasting Company|Bocaue|345|100|53249|9510|0000|0030|Adventist World Radio|Trincomalee (Pe|75|125|54536|9560|0000|0030|BBC Worldservice|Kranji (Merlin)|330|250|

14

• Output from direction finder database

Measurement details – azimuth values

1|3185,000|374|374|stationary|0|264|2909|23|-1029|0|1|0|14.12.2017 08:24:22|14.12.2017 08:24:23|1

1|3185,000|624|624|stationary|0|300|2873|27|-947|0|1|0|10.12.2017 06:24:05| |0

1|3185,000|893|893|stationary|0|271|2906|34|-1017|0|1|0|14.12.2017 08:07:46|14.12.2017 08:08:11|1

15

Simple visualization

• Azimuth values

Measurement details – visualization

0

90

180

270

360

11

72

34

35

14

68

58

56

10

27

11

98

13

69

15

40

17

11

18

82

20

53

22

24

23

95

25

66

27

37

29

08

30

79

32

50

34

21

35

92

37

63

39

34

41

05

42

76

44

47

46

18

47

89

Kaliningrad – all measurements

0

90

180

270

360

12

73

54

58

17

10

89

13

61

16

33

19

05

21

77

24

49

27

21

29

93

32

65

35

37

38

09

40

81

43

53

46

25

48

97

51

69

54

41

57

13

59

85

62

57

65

29

68

01

70

73

73

45

76

17

Goehren – all measuremetns

16

Azi

mu

th

Azi

mu

tNumber of measurement

Number of Measurement

Simple visualization of results shows challenges…:

Visualization

0

90

180

270

360

11

39

27

74

15

55

36

91

82

99

67

11

05

12

43

13

81

15

19

16

57

17

95

19

33

20

71

22

09

23

47

24

85

26

23

27

61

28

99

30

37

31

75

33

13

34

51

35

89

37

27

38

65

Tashkent - all

Transmitter 1

Transmitter 2Transmitter 3

17

Azi

mu

th

Number of measurement

Expected Value: 77,35°

Simple Solution:

• Filtering; discarding divergent direction finding results

• Decision based on known position (known azimuth) of transmitter

Data processing

18

Data processing

19

Azi

mu

thA

zim

uth


… now we know measured azimuth values at given times

as well as

expected azimuth values…

Now we need information about TIDs.

Intermediate results

20

We have:

TID history

date/time

date/time

We need:

TID

azim

uth

21

Source 1: website http://tid.space.noa.gr/data/text_obl_0.txt

TID information sources

TID characteristics

Ref. Time: 2017-11-02T12:53:15.000Z

Ref. Loc(N,E,km): 12.2300 39.9700 445.000

Amp (%): 11.3000

Period (min): 180.000

Prop. Azim (CW): 130.500

Wavelength (km): 1410.00

Phase velocity (m/s): 130.556

Confidence (%): 100.000

Uncertainty (%): 0.00000

Link information

Tx/Rx: AT138-->EB040

Distance (km): 1994.00

Bearing (CW): 91.5000

Ray Path (km): 2298.00

OEL Cutoff (km): 2228.00

An. win (min): 180.000

22

Result of research project NetTIDE

Source 2: website https://lgdc.uml.edu/rix/track-info?tid=$i

TID information sources

# Global Ionosphere Radio Observatory

# Traveling Ionospheric Disturbance Subsystem

# TID Detection Database : Signal Tracking Module

# Generated by Track-Info-Servlet version 0.2 on 2018-05-18T20:18:12.755Z

#

# Requested TID ident: 197749

#

# Reference time (UT) 2017.07.28 21:53:15.000

# Receiver EB040 at 40.80N 0.50E

# Transmitter AT138 at 38.00N 23.50E

# Ground distance 1994 km

# Operating Frequency: 4725.0 kHz

# Polarization: O

#

## Date Time path_km dopp_Hz zen_deg azim_deg SNR_dB Err_deg Amp_dB

01,2017.07.28,21:18:15, 2469.0, -1.660, 61.91, 264.96, 24.3, 1.54, 21.3

02,2017.07.28,21:23:15, 2474.0, -1.489, 51.89, 254.90, 22.7, 1.32, 15.7

03,2017.07.28,21:28:15, 2467.3, -0.993, 64.58, 268.23, 22.2, 4.71, 15.9

04,2017.07.28,21:33:15, 2389.0, -0.684, 66.39, 265.71, 24.2, 2.01, 16.2

05,2017.07.28,21:38:15, 2365.6, -0.439, 63.09, 268.34, 23.8, 4.66, 1

06,2017.07.28,21:43:15, 2464.0, -0.342, 52.21, 268.12, 21.6, 2.

07,2017.07.28,21:48:15, 2474.0, -0.562, 47.29, 271.49,

08,2017.07.28,21:53:15, 2464. 23

Source 2 data processing (1/4)





#


#






# Polarization: O

#


01,2017.07.28,21:18:15, 2469.0, -1.660, 61.91, 264.96, 24.3, 1.54, 21.3

02,2017.07.28,21:23:15, 2474.0, -1.489, 51.89, 254.90, 22.7, 1.32, 15.7

03,2017.07.28,21:28:15, 2467.3, -0.993, 64.58, 268.23, 22.2, 4.71, 15.9

04,2017.07.28,21:33:15, 2389.0, -0.684, 66.39, 265.71, 24.2, 2.01, 16.2

05,2017.07.28,21:38:15, 2365.6, -0.439, 63.09, 268.34, 23.8, 4.66, 1

06,2017.07.28,21:43:15, 2464.0, -0.342, 52.21, 268.12, 21.6, 2.

07,2017.07.28,21:48:15, 2474.0, -0.562, 47.29, 271.49,

08,2017.07.28,21:53:15, 2464.





#


#






# Polarization: O

#


01,2017.07.28,21:18:15, 2469.0, -1.660, 61.91, 264.96, 24.3, 1.54, 21.3

02,2017.07.28,21:23:15, 2474.0, -1.489, 51.89, 254.90, 22.7, 1.32, 15.7

03,2017.07.28,21:28:15, 2467.3, -0.993, 64.58, 268.23, 22.2, 4.71, 15.9

04,2017.07.28,21:33:15, 2389.0, -0.684, 66.39, 265.71, 24.2, 2.01, 16.2

05,2017.07.28,21:38:15, 2365.6, -0.439, 63.09, 268.34, 23.8, 4.66, 1

06,2017.07.28,21:43:15, 2464.0, -0.342, 52.21, 268.12, 21.6, 2.

07,2017.07.28,21:48:15, 2474.0, -0.562, 47.29, 271.49,

08,2017.07.28,21:53:15, 2464.





#


#






# Polarization: O

#


01,2017.07.28,21:18:15, 2469.0, -1.660, 61.91, 264.96, 24.3, 1.54, 21.3

02,2017.07.28,21:23:15, 2474.0, -1.489, 51.89, 254.90, 22.7, 1.32, 15.7

03,2017.07.28,21:28:15, 2467.3, -0.993, 64.58, 268.23, 22.2, 4.71, 15.9

04,2017.07.28,21:33:15, 2389.0, -0.684, 66.39, 265.71, 24.2, 2.01, 16.2

05,2017.07.28,21:38:15, 2365.6, -0.439, 63.09, 268.34, 23.8, 4.66, 1

06,2017.07.28,21:43:15, 2464.0, -0.342, 52.21, 268.12, 21.6, 2.

07,2017.07.28,21:48:15, 2474.0, -0.562, 47.29, 271.49,

08,2017.07.28,21:53:15, 2464.

Filtering: Transmitter, receiver

AT138 -> EB040

DB049 -> EB040

PQ052 -> JR055

DB049 -> JR055

MHJ45 -> MHJ45

…

…

24

Test data

PQ052

JR055

DB049

AT138

EB040

25


…

date/time

AT

138

->

EB

040

date/time

AT

138 -

> E

B040

concatenate, sort

uniq

…

26


tidfile = open("X:/TechTIDE/DBDaten/JR_PQ_uniq.txt","r")for tidline in tidfile:

tidsplit = tidline.split(",")if len(tidsplit)>2:

lasttime = currenttimecurrenttime = datetime.datetime(int(tidsplit[0][0:4]), int(tidsplit[0][5:7]), int(tidsplit[0][8:10]), int(tidsplit[1][0:2]),

int(tidsplit[1][3:5]), int(tidsplit[1][6:8]))# Setzen der Anfangs- und Endzeit einer TIDif starttime is None:

starttime=lasttimeendtime=lasttime

# Erst mit dem zweiten Eintrag beginnen zu prüfen, da es sonst# keinen letzten Zeitstempel gibt.if not(lasttime is None):

timediff=currenttime-lasttime

# Wenn zwischen zwei Zeitstempeln mehr als 6 min vergangen# sind, dann wird dies als Lücke zwischen TIDs und somit# Beginn einer neuen TID gewertet

if (timediff.seconds>360 or timediff.days>0):#print ("Old TID ends at ",lasttime,# "\nand new TID starts at ", currenttime)#print ("TID found:",starttime,"~~~",endtime)tidlist.append((starttime,endtime))starttime=currenttimeendtime=currenttime

[...]

date/time

AT

138

->

EB

040

clustering

Script:

…

TID1 TID3TID2

2018-xx-xx yy:yy-zz:zz – TID12018-xx-xx yy:yy-zz:zz – no TID2018-xx-xx yy:yy-zz:zz – TID2

2018-xx-xx yy:yy-zz:zz – no TID2018-xx-xx yy:yy-zz:zz – TID3

2018-xx-xx yy:yy-zz:zz – no TID

27

Azimuth list TID list


2018-xx-xx yy:yy-zz:zz – TID1


2018-xx-xx yy:yy-zz:zz – TID2


2018-xx-xx yy:yy-zz:zz – 61°2018-xx-xx yy:yy-zz:zz – 62°2018-xx-xx yy:yy-zz:zz – 61°2018-xx-xx yy:yy-zz:zz – 73°2018-xx-xx yy:yy-zz:zz – 61°2018-xx-xx yy:yy-zz:zz – 62°2018-xx-xx yy:yy-zz:zz – 62°2018-xx-xx yy:yy-zz:zz – 70°2018-xx-xx yy:yy-zz:zz – 61°2018-xx-xx yy:yy-zz:zz – 62°2018-xx-xx yy:yy-zz:zz – 60°

…

…

#

#

#

azimuth

azimuth

azimuthTID1:

TID2:

no TID:

28

Data source 2: Overview

29

Receiver Transmitter #lines of data #unique lines of data

JR055 PQ052 4.131.045 254.346

JR055 DB049 64.190 6.515

EB040 DB049 3.249.681 238.303

EB040 AT138 247.413 49.629

MHJ45 MHJ45 2.016 142

(Error) / /

Sum 7.694.345 548.935

(2.4 Gigabytes of data)

Data source 2 – Statistics

30

Test data – PQ052-JR055

PQ052

JR055

DB049

AT138

EB040

31

PQ052-JR055 – a closer look

PQ052

JR055

TID

32

Measurements from Swisttal

PQ052

JR055Göhren Moscow

Kaliningrad

Nauen

…Taschkent

Weenermoor

33

PQ052-JR055 – a closer look

PQ052

JR055 Kaliningrad

TID

34

Kaliningrad

Freq.: 5461,5820, 6125, 6465, 6470, 6495, 8191, 8939, 9625, 9650 kHzAzimuth: 58.882°, distance = 1021.05 km

35

Azi

mu

t


0

90

180

270

360

11

73

34

55

17

68

98

61

10

33

12

05

13

77

15

49

17

21

18

93

20

65

22

37

24

09

25

81

27

53

29

25

30

97

32

69

34

41

36

13

37

85

39

57

41

29

43

01

44

73

46

45

48

17

Kaliningrad all

0

500

1000

1500

2000

2500

3000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37

Histogram azimuth values

occurence in 10° areas

Kaliningrad


36

Azi

mu

th


0

90

180

270

360

11

73

34

55

17

68

98

61

10

33

12

05

13

77

15

49

17

21

18

93

20

65

22

37

24

09

25

81

27

53

29

25

30

97

32

69

34

41

36

13

37

85

39

57

41

29

43

01

44

73

46

45

48

17

Peilung – Kaliningrad komplett

0

500

1000

1500

2000

2500

3000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37

Histogramm Peilwerte

occurence in 10° areas

Kaliningrad


37

Azi

mu

th


0

90

180

270

360

11

73

34

55

17

68

98

61

10

33

12

05

13

77

15

49

17

21

18

93

20

65

22

37

24

09

25

81

27

53

29

25

30

97

32

69

34

41

36

13

37

85

39

57

41

29

43

01

44

73

46

45

48

17

Kaliningrad all

0

500

1000

1500

2000

2500

3000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37

Histogramm Peilwerte

Occurrence in 10° areas

Kaliningrad


0

90

180

270

360

11

10

21

93

28

43

75

46

65

57

64

87

39

82

10

91

12

00

13

09

14

18

15

27

16

36

17

45

18

54

19

63

20

72

21

81

22

90

23

99

25

08

26

17

27

26

28

35

29

44

30

53

Kaliningrad, filtered

38

Azi

mu

th

Azi

mu

thNumber of Measurement


0

90

180

270

360

11

73

34

55

17

68

98

61

10

33

12

05

13

77

15

49

17

21

18

93

20

65

22

37

24

09

25

81

27

53

29

25

30

97

32

69

34

41

36

13

37

85

39

57

41

29

43

01

44

73

46

45

48

17

Kaliningrad all

Kaliningrad

39

mea

n s

qu

ared

err

or

TID number

No

TID

Mean squared error: average squared differences between measured azimuths and true value 0

100

200

300

400

500

600

700

800

900

1000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71 73 75 77 79 81 83 85 87 89 91

Kaliningrad – filtered, TIDs

The data sets allow analysis of the following aspects:

• Day/night/dawn

• Frequencies (MUF, FOT, LUF)

• Movement (velocity and direction) of TIDs

• Summer/winter

• Multi hop connections

• Local geomagnetic anomalies

• (Local influences close to direction finder)

• (Technology of direction finder)40

Further questions

Thank you very much for your attention.

Questions?

The end…

??41

tids and their effects on hf direction finding 1st techtide user...

Documents