The Galactic Hub Cartography Project
This page describes the method that players can use to collect in-game data to expand the Galactic Hub Cartography Project. To facilitate collecting this data, it may be helpful to use quest markers, your freighter marker, base markers, etc. as visual bookmarks of anchor systems in the galaxy map. Essentially, to expand the map, you will need to record a new system's distance from each of the pre-existing anchor points (at time of writing, there are four in Euclid and five in Calypso)
If you don't care about how it all works and want to get straight to mapping, it's at the bottom under Network Expansion
Before we can begin, I think it would be helpful to explain some definitions and the big picture. Fun things first.
The Big Picture

Working Hubmap: A wireframe of Calypso hubspace. At time of writing, there are five anchors in [HUB][44,25,17,45,21]
My vision for this project is that we have a fully mapped out hubspace. Because of how the relative positions are calculated (a series of progressively improving trilaterations then n-laterations), spatial layout of systems on the galaxy map is preserved when close to an anchor point, which gives us a way to create our own galaxy map, but load it with way more handy information (that already exists on the wiki...). However, because we are not HG, we have to do some legwork by adding systems on the outskirts of the established network into the network. Over time and progressive expansion, all of this data can be used to make an increasingly precise map of hubspace.
Understanding the Hubspace Network
All data that is loaded into the map comes from a growing database of JSON objects that contain specific parameters about each system that has been mapped. The JSON object for a particular mapped system may look like:
{
id: "[HUB#-####]"
name: "Real System”,
anchors: “{
“A”: 0,
“B”: 0,
“C”: 0,
…etc
}”,
color: “red”
is_anchor: false,
anchor_id: 0,
confidence: 0,
galaxy: 'calypso'
},
(As a cartographer for this project, you can ignore the anchor_id, is_anchor and confidence attributes. They are used for internal calculations/validations.)
With this user-input data, the map will pull down wiki data about the system (if it exists) and display it as a pop up for the system in the map. Most attributes explain themselves, but the anchors deserve some special attention.
Anchor points are systems with whom all other systems in-network have a recorded distance. This means that every system in the map has a defined attribute for that anchor system, equal to the distance from the anchor point to the new system. The more anchor points we have, the better our map gets, but this requires a lot of time when you have many nodes. Realistically, expansion of anchor points will be much slower than expansion of network points, which will be fine as three to five anchor points already establish a coordinate system very well.
Once these anchor point distances are recorded and submitted, they are used in a more robust version of a process called trilateration to determine their position relative to the established anchor points (like with GPS!). Through this process, we can make a high spatial fidelity map of hubspace, or really any chunk of the galaxy you care to enter the data into.
In the future, the idea is to link these mappings of systems, complete with information straight from the wiki, to make a utility similar to the in-game galaxy map pathing but for more detailed and varied routes (i.e. make a route that only goes through systems with cargo bulkheads as guild rewards, or a tuned trade route)
The Index of Anchors
EUCLID ANCHORS
| Anchor Point | System Name | Distance from A | Distance from B | Distance from C | Distance to D |
|---|---|---|---|---|---|
| A | [HUB12-416] Lion Shield | 0 | 691 | 1334 | 967 |
| B | [HUB1-74] Sun Tzu | 691 | 0 | 875 | 435 |
| C | [HUB7-3FE] Aniwani | 1334 | 875 | 0 | 1148 |
| D | [HUB22-406] Legods | 967 | 435 | 1148 | 0 |
CALYPSO ANCHORS
| Anchor Point | System Name | Distance from A | Distance from B | Distance from C | Distance to D | Distance to E |
|---|---|---|---|---|---|---|
| A | [HUB44-A] Tashat | 0 | 1473 | 1136 | 1368 | 946 |
| B | [HUB45-A] Nasfiel-Nit | 1473 | 0 | 1127 | 1134 | 1016 |
| C | [HUB17-A] Ochleac | 1136 | 1127 | 0 | 1848 | 1043 |
| D | [HUB25-A] Snezhna | 1368 | 1134 | 1848 | 0 | 1390 |
| E | [HUB21-1E] Sidusius | 946 | 1016 | 1043 | 1390 | 0 |
Notice that this table is symmetric along the diagonal. It should never not be!
Network expansion
To help grow the Hubspace Network, follow these steps:
- Use each anchor's hubtag to find its glyph, then use a portal to get to the anchor.
- Mark the anchor points on your galaxy map. This could mean renaming them, pinning them, or using another method that works for you
- Visit any unmapped system in Hubspace.
- Open the galaxy map, and record the distances from this system to each of the anchor points.
- Submit your data via the map's website.
- Alternatively, you can use this CSV format for your data collection (pay attention to where quotations are!). This option is preferred for larger sets of entries:
| id | name | anchors | color | is_anchor | anchor_id | confidence |
|---|---|---|---|---|---|---|
| [HUB44-A] | Tashat | "{"A": 0, "B": 1473, "C": 1136, "D": 1368, "E": 946}" | yellow | true | A | 0 |
Sample data collection
This section uses a particular star system as a sample for how to collect the needed data.
So, you’ve found a star that’s in hubspace but not yet mapped. For our example, system Zouche

The first step is to travel to Zouche by whatever means available (freighter, portal, starship, etc.).
Next, you will need to record the distances of each anchor to this system. For this step, it is strongly recommended to mark the anchor points by placing a place in the anchor system, or putting your freighter there, or any other way to mark the systems so you can quickly navigate to them in the galaxy map.
Since Zouche is in calypso, we will need to locate the five anchors given above:





On the site, press the "initialize target" button and enter the date based on these distances:

And that's it! Collect as many of these entries as you please, and then submit them to me, Soideos, either via DM or the Calypso Galactic Hub discord channel for this project
For now, I will personally work on establishing more anchor points in the network.
Looking forward
- Expanding anchor points and network points around region 1 is a high priority. Proving that the method works will be the most important thing right now
- Equipping the tool so that solo interlopers can develop their own local maps, then optionally merge it back to the main map
- Add an appealing UI with as much linked information as possible, including optimal routes for X goal (guild rewards, dissonant systems, systems with player bases, etc.)
- Expand parameter tracking in JSON