Power maps preview

With system connectivity becoming more important in Powerplay 2, I've been trying to put some visualisations together.

Here's the current Powerplay 1 territories (minus a few systems the previewers have confirmed as going to Kaine) under the Powerplay 2 rules, with the Strongholds as previewers have found. Data from EDDN around the start of the week for current Control/Exploited so a few systems might not match in-game.
AislingDuval.png
ALavigny-Duval.png
ArchonDelaine.png
DentonPatreus.png
EdmundMahon.png
FeliciaWinters.png
LiYong-Rui.png
(Not enough data yet to do a preview for Nakato Kaine's expected territory)
PranavAntal.png
YuriGrom.png
ZacharyHudson.png
ZeminaTorval.png

At the moment I'm using a hierarchical map heading outwards from the HQ to show connectivity and distance, since it seems like "inside/outside" might well be affecting system thresholds.
Another alternative would be a less hierarchical and less distance-sensitive format as used in my Thargoid war maps - this gives scope to show more connections between Fortified/Stronghold at the same layer without it getting too messy, but has the disadvantage of not being able to show roughly how far away a system is from the HQ in any meaningful sense.

I did also consider showing links which would be created if a Fortified was promoted to a Stronghold ... but it turns out that there are a lot of them and again it makes the graph very messy.

Any thoughts? I'm going to try to put these together weekly (and once things get going, with some extra automation!) just for my own curiosity, but if people would find them useful or have suggestions for extra information which would make them useful then provided it's readable via EDDN I can look at adding it.
 
With system connectivity becoming more important in Powerplay 2, I've been trying to put some visualisations together.

Here's the current Powerplay 1 territories (minus a few systems the previewers have confirmed as going to Kaine) under the Powerplay 2 rules, with the Strongholds as previewers have found. Data from EDDN around the start of the week for current Control/Exploited so a few systems might not match in-game.
AislingDuval.png
ALavigny-Duval.png
ArchonDelaine.png
DentonPatreus.png
EdmundMahon.png
FeliciaWinters.png
LiYong-Rui.png
(Not enough data yet to do a preview for Nakato Kaine's expected territory)
PranavAntal.png
YuriGrom.png
ZacharyHudson.png
ZeminaTorval.png

At the moment I'm using a hierarchical map heading outwards from the HQ to show connectivity and distance, since it seems like "inside/outside" might well be affecting system thresholds.
Another alternative would be a less hierarchical and less distance-sensitive format as used in my Thargoid war maps - this gives scope to show more connections between Fortified/Stronghold at the same layer without it getting too messy, but has the disadvantage of not being able to show roughly how far away a system is from the HQ in any meaningful sense.

I did also consider showing links which would be created if a Fortified was promoted to a Stronghold ... but it turns out that there are a lot of them and again it makes the graph very messy.

Any thoughts? I'm going to try to put these together weekly (and once things get going, with some extra automation!) just for my own curiosity, but if people would find them useful or have suggestions for extra information which would make them useful then provided it's readable via EDDN I can look at adding it.
Thank you for this
 
With system connectivity becoming more important in Powerplay 2, I've been trying to put some visualisations together.

Here's the current Powerplay 1 territories (minus a few systems the previewers have confirmed as going to Kaine) under the Powerplay 2 rules, with the Strongholds as previewers have found. Data from EDDN around the start of the week for current Control/Exploited so a few systems might not match in-game.
AislingDuval.png
ALavigny-Duval.png
ArchonDelaine.png
DentonPatreus.png
EdmundMahon.png
FeliciaWinters.png
LiYong-Rui.png
(Not enough data yet to do a preview for Nakato Kaine's expected territory)
PranavAntal.png
YuriGrom.png
ZacharyHudson.png
ZeminaTorval.png

At the moment I'm using a hierarchical map heading outwards from the HQ to show connectivity and distance, since it seems like "inside/outside" might well be affecting system thresholds.
Another alternative would be a less hierarchical and less distance-sensitive format as used in my Thargoid war maps - this gives scope to show more connections between Fortified/Stronghold at the same layer without it getting too messy, but has the disadvantage of not being able to show roughly how far away a system is from the HQ in any meaningful sense.

I did also consider showing links which would be created if a Fortified was promoted to a Stronghold ... but it turns out that there are a lot of them and again it makes the graph very messy.

Any thoughts? I'm going to try to put these together weekly (and once things get going, with some extra automation!) just for my own curiosity, but if people would find them useful or have suggestions for extra information which would make them useful then provided it's readable via EDDN I can look at adding it.
Showing dependent systems is good to see where vulnerabilities lie in an easy way.

Could you do a sort of Venn diagram where (say) in the top left you have the capital, then have overlaps across the page (so you can then visually see fortified systems and strongholds by bigger / smaller circles?

1730193522907.png
 
Last edited:
Could you do a sort of Venn diagram where (say) in the top left you have the capital, then have overlaps across the page (so you can then visually see fortified systems and strongholds by bigger / smaller circles?
The tricky thing there is compressing a 3-D space onto a 2-D map, and distinguishing between "these circles overlap because they share the same space" and "these circles overlap because of the projection".

Using lines for connections like the Thargoid maps, that gives something like this
LiYong-Rui.neato.png
(Just a quick draft, I'd make the arrow pairs just be double-headed arrows if I was doing it properly)

Arguably more informative for a strongly-connected power like LYR, but for a weakly-connected power like AD
AislingDuval.neato.png
the layout algorithm just puts all the loose systems on without any way to really indicate their positioning. On the other hand, it is still perhaps clearer for showing the Cubeo, Cari and LTT 1289 clusters as distinct from the others.

I might tune this version up and do both sorts - as the loose systems get either cross-linked or destroyed the "big cloud of targets" effect should decrease anyway.
 
The tricky thing there is compressing a 3-D space onto a 2-D map, and distinguishing between "these circles overlap because they share the same space" and "these circles overlap because of the projection".

Using lines for connections like the Thargoid maps, that gives something like this
(Just a quick draft, I'd make the arrow pairs just be double-headed arrows if I was doing it properly)

Arguably more informative for a strongly-connected power like LYR, but for a weakly-connected power like AD
the layout algorithm just puts all the loose systems on without any way to really indicate their positioning. On the other hand, it is still perhaps clearer for showing the Cubeo, Cari and LTT 1289 clusters as distinct from the others.

I might tune this version up and do both sorts - as the loose systems get either cross-linked or destroyed the "big cloud of targets" effect should decrease anyway.
I think the most important useful information to highlight visually (where possible) is what exploited systems are the most vulnerable and what system to attack.

Defenders will want this to see where is exposed, attackers will use this for maximum damage.

Maybe have colour- deep reds for exposed exploited systems that have low support (so in essence working backwards- seeing everything from the exploited systems POV first, since they'll be lost the fastest).
 
So connectivity here defines a fortified/stronghold system that is within range of another fortified/stronghold system? It would also be useful to know, if a fortified system has exploits also supported by another fortified system, which system that is. Not sure if that's honestly practical to display, however. Particularly on the same display.
 
So connectivity here defines a fortified/stronghold system that is within range of another fortified/stronghold system?
Yes, that's right.

It would also be useful to know, if a fortified system has exploits also supported by another fortified system, which system that is. Not sure if that's honestly practical to display, however. Particularly on the same display.
Not sure - it'd certainly increase the number of links on the graph, but maybe not to the point of being unreadable on the non-hierarchical display style. I'll give it a try and see what happens.

It'd be easy enough to build a query interface where you gave it a Fortified system and it gave you a table of Exploited | Other Supporters. On the other hand, that seems like the sort of question which the in-game map would do pretty well at answering, without risking EDDN-inevitable lag in updating system states!
 
Okay, I quite like this at the moment for bringing a little more geographic sense to the maps which were previously mainly a collection of loose blobs.
ZacharyHudson.connections.png
If Powers get to the stage of heavily cross-reinforcing everything I'll probably need to turn it off again, but at that point it's likely less relevant anyway.
 
I really appreciate these flowchart/Venn illustrations identifying the specific features of specific systems affiliated with a Power.

What I do not understand is the Galaxy Powerplay bubble map. Many of the systems within a "bubble" are not listed as directly controlled by or affiliated with a specific Power.

Is this representation just about the approximate boundaries of that Power's space, or is there a hidden tag for unaffiliated systems that actually attaches them to the Power?
 
Okay, I quite like this at the moment for bringing a little more geographic sense to the maps which were previously mainly a collection of loose blobs.
If Powers get to the stage of heavily cross-reinforcing everything I'll probably need to turn it off again, but at that point it's likely less relevant anyway.
Yep. It's busy, but adds something. I was sort of thinking of a toggleable overlay I suppose. Or two versions of the map. One with each kind of connection shown.
 
It'd be easy enough to build a query interface where you gave it a Fortified system and it gave you a table of Exploited | Other Supporters. On the other hand, that seems like the sort of question which the in-game map would do pretty well at answering, without risking EDDN-inevitable lag in updating system states!
That would be nice. Not sure how clear it is from the in-game map.
 
That would be nice. Not sure how clear it is from the in-game map.
Okay, yes, this is possible. Output would look something like this (but with more spaces in system names - copy-paste into the forum got messed up somehow)

I'll put it up somewhere once I start getting actual EDDN data through.

LTT 9795​

Fortified for Denton Patreus

Exploited SystemOther Supporters (Strongholds bold)
AninohanuPicaurukan; TsimBinba; Zelano;
ArngiPicaurukan; TsimBinba;
AryaminOmicronGruis; Vaka; Zelano;
BPM45047
CPO24Picaurukan; TsimBinba; Zelano;
CoelatuveanTsimBinba;
Dalia
GamiMusuTsimBinba; Vaka; Zelano;
HR9046Buricasses; Vaka;
Isis
KappaPhoenicisTsimBinba; Zelano;
KigandanTsimBinba;
LFT1834Vaka;
LFT37
LHS1020Vaka; Zelano;
LHS1122TsimBinba; Zelano;
LTT198TsimBinba;
LTT377TsimBinba;
Nemet
NgauninginVaka; Zelano;
Pachamama
Qarato
ReddotPicaurukan; TsimBinba; Zelano;
Segovit
TavgiTsimBinba;
ThetaSculptorisTsimBinba;
UdihikojaVaka; Zelano;
 
Hi Ian,

Once the final release comes out, will you be making these maps available to us with the final strongholds and fortified systems?

thanks,
Andrew
 
Once the final release comes out, will you be making these maps available to us with the final strongholds and fortified systems?
That's the idea - it'll probably be a few days post-release as I'll need to make sure the EDDN feed is working properly with the new properties and give it a couple of days to at least get most of the systems recorded.
 
Back
Top Bottom