ED Astrometrics: Maps and Visualizations

Orvidius

Orvidius
I've added region boundaries as a selection on the interactive map. I'm not sure how precise this is, since I was using screenshots to build it, and I'm surprised that Sagittarius-A* would be that face below the region center. This will take further verification and refinement later.
 

Maolagin

M
Orvidius said:
I've added region boundaries as a selection on the interactive map. I'm not sure how precise this is, since I was using screenshots to build it, and I'm surprised that Sagittarius-A* would be that face below the region center. This will take further verification and refinement later.
Click to expand...

Impossible to verify until next week since the Beta is over, but I'm pretty sure you have an offset. I was starting to make notes about the coordinates of the vertices on the region map last week, so I can say that the Orion/Elysium/Sanguinous triple point that you have a bit west of the Bubble, is actually closer to -2000,-1700. Roughly on the high-traffic diagonal between the Bubble and the Formidine settlements. Shifting everything down by about that much looks like it would center SagA too.

Once 3.3 goes live, the community should really go through and get refined coordinates for all those corners. I think a variety of apps will wind up wanting precise boundaries or vector overlays.
 

Orvidius

Orvidius
Yeah, I made a few attempts to align the regional boundaries, and I centered it more visually at first. But then some of the corners didn't line up with the arm gaps the same way they did in screenshots of the in-game codex map. Some of that might also be due to scaling the whole overlay too, but it's hard to tell.

The good news is that now that I've created the "path" in Photoshop, I can scale and move it around as needed before re-rasterizing.

I didn't see if the journals will record region names as people travel. I hope it does, so that EDSM can build up some region data.
 

Maolagin

M
Orvidius said:
Yeah, I made a few attempts to align the regional boundaries, and I centered it more visually at first. But then some of the corners didn't line up with the arm gaps the same way they did in screenshots of the in-game codex map. Some of that might also be due to scaling the whole overlay too, but it's hard to tell.

The good news is that now that I've created the "path" in Photoshop, I can scale and move it around as needed before re-rasterizing.

I didn't see if the journals will record region names as people travel. I hope it does, so that EDSM can build up some region data.
Click to expand...

It does, but not very usefully. At least in my journal files from the beta, the region name is only emitted when you create a Codex entry by scanning a new type of object. So EDSM could harvest region names from the journals, but each player could only contribute one system per type of object (104 in total, I think?). We might need something similar to the current triangulation interface, allowing players to manually tag systems with the region they are in. Of course, once we have good boundaries, EDSM can do that automatically from the coordinates. Then perhaps it could do something similar to how it puts systems needing more trilateral distances on the front page -- proactively ask commanders to check stars calculated to be close to a region border to verify which region they are in.
 

Orvidius

Orvidius
I've tweaked the positioning of the region boundaries and labels, but I know it's still not quite right. I'll have to make more adjustments later when we can start getting some positioning info in-game on where the region corners are.

I've also added the region-overlaid heatmap as a downloadable image.
 

Orvidius

Orvidius
I'm still tweaking the region boundaries on the interactive map, but it's already a lot better. I've been flying out to some of the boundary intersections, where 3 regions come together, and it's helping to line things up.

Also, I started to get curious about the exploration data rates before and after 3.3. The server downtime on Tuesday is quite apparent in the data, and the weekend had a huge amount of activity:

2 weeks of discovered systems:

Code: 
mysql> select date(edsm_date),count(*) from systems group by date(edsm_date) order by date(edsm_date) desc limit 14;
+-----------------+----------+
| date(edsm_date) | count(*) |
+-----------------+----------+
| 2018-12-16      |    61325 |
| 2018-12-15      |    57712 |
| 2018-12-14      |    43199 |
| 2018-12-13      |    33966 |
| 2018-12-12      |    23235 |
| 2018-12-11      |     4889 |
| 2018-12-10      |    19578 |
| 2018-12-09      |    37325 |
| 2018-12-08      |    29882 |
| 2018-12-07      |    15411 |
| 2018-12-06      |    21377 |
| 2018-12-05      |    23956 |
| 2018-12-04      |    18393 |
| 2018-12-03      |    23380 |
+-----------------+----------+
14 rows in set (9.00 sec)


2 weeks of discovered planets:

Code: 
mysql> select date(updateTime),count(*) from planets group by date(updateTime) order by date(updateTime) desc limit 14;                                   
+------------------+----------+
| date(updateTime) | count(*) |
+------------------+----------+
| 2018-12-16       |   465891 |
| 2018-12-15       |   397207 |
| 2018-12-14       |   309462 |
| 2018-12-13       |   222336 |
| 2018-12-12       |   170213 |
| 2018-12-11       |    13638 |
| 2018-12-10       |    24029 |
| 2018-12-09       |    33260 |
| 2018-12-08       |    27922 |
| 2018-12-07       |    18667 |
| 2018-12-06       |    14887 |
| 2018-12-05       |    16272 |
| 2018-12-04       |    16819 |
| 2018-12-03       |    20934 |
+------------------+----------+


2 weeks of discovered stars:

Code: 
mysql> select date(updateTime),count(*) from stars group by date(updateTime) order by date(updateTime) desc limit 14;       
+------------------+----------+
| date(updateTime) | count(*) |
+------------------+----------+
| 2018-12-16       |   141353 |
| 2018-12-15       |   124212 |
| 2018-12-14       |   100121 |
| 2018-12-13       |    71191 |
| 2018-12-12       |    51368 |
| 2018-12-11       |     4902 |
| 2018-12-10       |    12813 |
| 2018-12-09       |    16127 |
| 2018-12-08       |    14185 |
| 2018-12-07       |     7542 |
| 2018-12-06       |     8396 |
| 2018-12-05       |    11887 |
| 2018-12-04       |     9333 |
| 2018-12-03       |    10280 |
+------------------+----------+
 
Last edited:

Straha Yeagar

S
Holy crap, I figured the number of reports would go up, but those have skyrocketed! No wonder EDSM and EGO have been under such heavy load.

Complete side note, do you have an image of the galaxy regions overlay? I have been trying to track one down without much luck.
 

Orvidius

Orvidius
Straha Yeagar said:
Complete side note, do you have an image of the galaxy regions overlay? I have been trying to track one down without much luck.
Click to expand...

Just the overlay itself? I had to make mine in a high resolution for the map. I stuffed a copy of it here (currently about 2 MB, PNG with transparent background). That URL will get updated with whatever the current copy is, as I make changes.
 
Last edited:

marx

marx
Thanks for the numbers! To be honest, I expected a larger spike on the number of systems, but it's still pretty good. Of course, the update is most popular with new explorers, who are the least likely to upload to EDSM. As for the bodies and stars, that's a direct consequence of the FSS. A very nice unintended benefit for community exploration ;)
Would you mind running the same queries monthly? Should be interesting to see the results.
 
Last edited:

Orvidius

Orvidius
Yeah, I think I can put together some nice spreadsheets, and have them auto-updated on the website. I'll see what I can throw together.
 

Orvidius

Orvidius
Orvidius said:
Yeah, I think I can put together some nice spreadsheets, and have them auto-updated on the website. I'll see what I can throw together.
Click to expand...

OK, I've have a pair of spreadsheets set up, which will update on the same interval as the maps.

* Discovery Dates

* Discovery Months

This has the caveat of course that whatever the "current" month is will always have incomplete data, until we move on the next month.


Straha Yeagar said:
This is exactly what I was looking for!
Click to expand...

Awesome. :)
 
Last edited:

marx

marx
Sweet, thanks! Didn't expect to see historical data, but it's very good for context. It's curious that the highest levels of explorer activity, in numbers of systems visited, was around The Return (2.4), and Beyond Chapter One (3.0). The current spike is more of a return to regular levels after a lengthy decrease (little wonder, as few wanted to explore when the new mechanics were coming), even if we assume that 50,000 systems will be visited each day. I have to admit, this worries me a bit. But after all, it's the EDSM data only - seems to correlate nicely with overall Steam stats though.

Oh, and just to be certain: I assume the "systems" means new systems logged, not systems visited, right?
 

Orvidius

Orvidius
Yep that's right, it's new ones logged. Although an unfortunate side effect I discovered is that EDSM alters the system's date when a second visitor corroborates the coordinates. So it's the date of submission if only one commander has visited, or the date of the second commander's visit if it has had 2 or more visitors.
 
Last edited:

Straha Yeagar

S
Hey Orvidius...I noticed your overlay has Scutum-Centaurus Arm listed in two different regions... 26 and 16.

gCB2i0W.jpg


We need to verify that...


9dERsUQ.png


EDIT: Above, the issue in your overlay is region 9 and not 16...

Region 9 is INNER Scutum-Centaurus, and 26 is OUTER Scutum-Centaurus
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom