Tactical Reconnaissance Analysis
Data downloads
The following data are available:
Spreadsheet with CNB and RES information
1032 kB | 1008 kiB
3310-11-21 10h
3 minutes ago
3 minutes ago
Populated systems with Shop and Arena information
962 kB | 939 kiB
3310-11-21 10h
3 minutes ago
3 minutes ago
Thargoid activity spreadsheet (Elite 4.0 only)
68 kB | 66 kiB
3310-11-21 10h
3 minutes ago
3 minutes ago
Thargoid activity data (Elite 4.0 only)
66 kB | 64 kiB
3310-11-21 10h
3 minutes ago
3 minutes ago
Thargoid war progress scan results (Elite 4.0 only)
7459 B
3310-11-21 06h
3 hours ago
3 hours ago
Schema
Arena list
CSV rows with header line.
Each row contains comma-separated CNB and RES data for each populated system. The tabulation is designed for browsing manually via spreadsheet program.
System row
System
The full system name.
CNB 3.8
Navigation beacon status reported from Elite 3.8.
Values: Yes, No, ?.
Values: Yes, No, ?.
CNB 4.0
Navigation beacon status reported from Elite 4.0.
Values: Yes, No, ?.
Values: Yes, No, ?.
Hazardous RES
Hazardous RES distance and body if known, otherwise its RES report status.
Values: Present, None, ?.
Values: Present, None, ?.
High RES
High RES position if known, otherwise its RES report status.
Values: Present, None, ?.
Values: Present, None, ?.
Medium RES
Medium RES position if known, otherwise its RES report status.
Values: Present, None, ?.
Values: Present, None, ?.
Low RES
Low RES position if known, otherwise its RES report status.
Values: Present, None, ?.
Values: Present, None, ?.
RES status
Combined RES report status for the system.
Values: Confirmed, Declared, Reported, Unknown.
Values: Confirmed, Declared, Reported, Unknown.
System data supplement
JSON lines with Gzip compression.
Each line contains a JSON object with station, CNB and RES data for each populated system. Various different keys for joining that to existing data are also provided.
System object
name
String
The full system name.
addr
Integer
The SystemAddress ID value as reported by Elite.
edsm
Integer
If known, the system ID used by EDSM.
Sentinel: -1 if no EDSM ID is stored.
Sentinel: -1 if no EDSM ID is stored.
eddb
Integer
If known, the system ID used by EDDB.
Sentinel: -1 if no EDDB ID is stored.
Sentinel: -1 if no EDDB ID is stored.
port_d
Number
If present, the distance in light-seconds to the closest starport.
Sentinel: -1 if the system contains no starports.
Sentinel: -1 if the system contains no starports.
post_d
Number
If present, the distance in light-seconds to the closest outpost.
Sentinel: -1 if the system contains no outposts.
Sentinel: -1 if the system contains no outposts.
cnb3
Integer
Navigation beacon status reported from Elite 3.8.
Values: 1 for CNB, 0 for NB, -1 if no report exists.
Values: 1 for CNB, 0 for NB, -1 if no report exists.
cnb3_t
Integer
Timestamp of the most recent beacon status report from Elite 3.8.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
cnb4
Integer
Navigation beacon status reported from Elite 4.0.
Values: 1 for CNB, 0 for NB, -1 if no report exists.
Values: 1 for CNB, 0 for NB, -1 if no report exists.
cnb4_t
Integer
Timestamp of the most recent beacon status report from Elite 4.0.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
ring_d
Number
If present, the distance in light-seconds to the closest planetary ring.
If a RES is reported, this could be used to estimate its distance.
Sentinel: -1 if the system contains no rings.
If a RES is reported, this could be used to estimate its distance.
Sentinel: -1 if the system contains no rings.
ring_b
String
If present, the name of the closest body in-system with a planetary ring.
Names starting with «+» are expressed as a system name suffix.
Names starting with «+» are expressed as a system name suffix.
visit
Integer
The number of times this system has received Arena data.
Missing RESs can be considered probably absent if the visit counter is high.
Missing RESs can be considered probably absent if the visit counter is high.
haz
Object
Hazardous RES status.
hi
Object
High RES status.
med
Object
Medium RES status.
low
Object
Low RES status.
RES object
r
Integer
RES presence status reported via INTRA.
Use the visit counter to decide whether an unreported RES may be present.
Values: 1 if a RES has been reported, otherwise 0.
Use the visit counter to decide whether an unreported RES may be present.
Values: 1 if a RES has been reported, otherwise 0.
c
Integer
RES status confirmed manually.
Values: 1 if confirmed present, 0 if confirmed absent, otherwise -1.
Values: 1 if confirmed present, 0 if confirmed absent, otherwise -1.
d
Number
The distance in light-seconds to the closest body with this RES type in its planetary rings.
Sentinel: -1 if no RES is reported or confirmed to be present, or if a RES is reported but has no body specified.
Sentinel: -1 if no RES is reported or confirmed to be present, or if a RES is reported but has no body specified.
b
String
The name of the closest body in-system with this RES type in its planetary rings.
Names starting with «+» are expressed as a system name suffix.
Sentinel: Empty string if no RES is reported or confirmed to be present, or if a RES is reported but has no body specified.
Names starting with «+» are expressed as a system name suffix.
Sentinel: Empty string if no RES is reported or confirmed to be present, or if a RES is reported but has no body specified.
Thargoid alert list
CSV rows with header line.
One row per system which has Thargoid presence in Elite 4.0, due to a Maelstrom or otherwise. The specific indications are listed, plus which Maelstrom is present or nearby (if any). The tabulation is designed for browsing manually via spreadsheet program.
System row
System
The full system name.
Allegiance
The system allegiance, if any, otherwise blank.
Station
If available, whether a station was reported as being under attack, otherwise blank.
Values: OK, Attack.
Values: OK, Attack.
Conflict
Whether any Low (L), Medium (M), High (H), or Very High (V) conflicts with Thargoids are present.
Maelstrom
Maelstrom title if present, otherwise the name and distance of a Maelstrom if nearby, otherwise blank.
Thargoid alert data
JSON lines with Gzip compression.
JSON objects with all indications used by INTRA to determine a Thargoid alert warning. The list contains all systems with reported Thargoid presence in Elite 4.0, due to a Maelstrom or otherwise.
Different indications have different times at which they were reported. It is reasonable to consider a system safe again if it has non-Thargoid allegiance and all other indications become stale.
System object
updated
Integer
Aggregated timestamp of the most recent activity report of any type.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
addr
Integer
The SystemAddress ID value as reported by Elite.
name
String
The full system name.
ally
String
The system allegiance, or empty if none.
sys_t
Integer
Timestamp of the most recent system report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
visit
Integer
The number of times this system entry has received a system report.
st_attack
Integer
Station attack status.
Values: 1 if attacked, 0 if no attack, -1 if no report exists.
Values: 1 if attacked, 0 if no attack, -1 if no report exists.
st_attack_t
Integer
Timestamp of the most recent station attack report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
cz_l
Integer
Timestamp of the most recent Low conflict report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
cz_m
Integer
Timestamp of the most recent Medium conflict report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
cz_h
Integer
Timestamp of the most recent High conflict report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
cz_v
Integer
Timestamp of the most recent Very High conflict report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
mael
String
The name of a Maelstrom if present, or empty if none.
mael_t
Integer
Timestamp of the most recent Maelstrom report.
Sentinel: -1 if no report exists.
Sentinel: -1 if no report exists.
War cycle progress
JSON lines.
Each JSON object represents a war-state system for which the war cycle progress is relevant and non-zero. Relevant states are Alert, Invasion and Control.
War activity object
cycle
Integer
The weekly cycle number, where cycle 1 started at 0700 on 1st December 3308.
name
String
The full system name.
addr
Integer
The SystemAddress ID value as reported by Elite.
state
String
The system war state initial; either Alert, Invasion or Control.
Values: A, I, C.
Values: A, I, C.
prog
Integer
The war state progress this cycle as a percentage.
src
String
ID code of organisation which supplied this activity entry.
updated
Integer
Timestamp of the most recent activity report from the given source.