Determining the region of a system

[Bravada Cadelanne]

49ly sounds like it'd be a 2048x2048 grayscale texture with the region number encoded in the intensity (or a RGB texture with each region assigned a certain colour), anchored at the origin (i.e. X=-49985, Z=-24105). If it's 49ly per pixel, that'd put the centre of that texture at X+166ly, Z+171ly from Sagittarius A*

If we assume the pixel size is 49ly +/-0.05ly, that would put EOR CHRUIA FV-N C20-1724 on the bottom edge of pixel 1063 (49.024ly/pixel) or pixel 1064 (48.978ly/pixel)

Edit: Some data points:

An edge between Inner Scutum-Centaurus Arm and Odin's Hold lies between Eol Prou TY-W a60-0 (X=-9074.62500) and Eol Prou TY-W a60-1 (X=-9074.34375)
I had more, but I wasn't writing them down, and I forgot they aren't recorded in the journal, so I'll have to go back through them later.

Oddly, using a 49.025ly pixel size, and with the bottom left corner of the bottom left pixel anchored at the origin, that edge would be at 834.5 pixels (48.978ly would give 835.279).

Another edge lies between Eol Prou WG-Z b29-37 (Z=20062.53125) and Eol Prou YB-Z b29-22 (Z=20062.75000). If the texture is perfectly aligned to X and Z axes, this would give a vertical pixel size of 49.0435ly +/- 0.001ly (162 pixels apart)

 

[Orvidius]

Yeah, I'm assuming they went with 2048 pixels translating to 100,000 lightyears. The entire reachable galaxy fits within 90,000 x 90,000, but I guess they wanted to be sure they got everything.

 

[Bravada Cadelanne]

Between Inner Orion Spur and Outer Orion Spur, one of the boundaries lies between Flyua Dryoae NA-A b33-0 (X=2276.00000) and Flyua Dryoae AB-A c16-1 (X=2276.09375). This would put the X pixel size at 48.9245ly +/-0.001ly (232 pixels between Eol Prou TY-W a60-0 and Flyua Dryoae NA-A b33-0) or 49.1365ly +/-0.001ly (231 pixels).

Another data point: a boundary lies between NGC 2546 Sector JA-C c14-5 (Z=-812.46875) and NGC 2546 Sector SF-N d7-65 (Z=-812.03125), which is incompatible with a perfectly aligned texture with vertical pixel size of 49.0435ly (it would be more like 49.0020ly +/-0.001ly, with a pixel distance of 426 pixels between Eol Prou TY-W a60-0 and Flyua Dryoae CA-U c5-3)

Yet another data point: Boundary between Sanguineous Rim / Inner Orion Spur / Outer Orion Spur lies between Outotch JW-E d11-17 (Z=-1354.90625) and Oochoxt FS-H d11-17 (Z=-1355.15625), which is about 3.5ly south of where a pixel size of 49ly would have put it versus NGC 2546 Sector JA-C c14-5.

Edit: Codex discoveries do not seem to follow the same region as the region displayed when jumping to a system. The in-game display when jumping to a system says Flyua Dryoae HB-V d3-2 is in the Outer Orion Spur, yet:

{
  "timestamp": "2020-03-12T15:40:42Z",
  "event": "CodexEntry",
  "EntryID": 1101201,
  "Name": "$Codex_Ent_Y_Type_Name;",
  "Name_Localised": "Y Type Star",
  "SubCategory": "$Codex_SubCategory_Stars;",
  "SubCategory_Localised": "Stars",
  "Category": "$Codex_Category_StellarBodies;",
  "Category_Localised": "Astronomical Bodies",
  "Region": "$Codex_RegionName_18;",
  "Region_Localised": "Inner Orion Spur",
  "System": "Flyua Dryoae HB-V d3-2",
  "SystemAddress": 79683307811
}

The codex is also confused by the literal edge case - the hub says I'm in the Inner Orion Spur, yet when I click Discoveries it says I'm in the Outer Orion Spur.

Edit 2: I think the region the front page says you're in (and the region codex discoveries puts you in) might be linked to where the corner of the boxel is - e.g. it puts Flyua Dryoae HB-V d3-2 (X=2297.47, Boxel X=2255) in the Inner Orion Spur, yet it puts Flyua Dryoae IR-B b18-1 (X=2297.44, Boxel X=2295) in the Outer Orion Spur. It also puts Flyua Dryoae JR-Q c7-1 (X=2295.94, Boxel X=2295) in the Outer Orion Spur, while it puts Flyua Dryoae EL-S c6-5 (X=2291.44, Boxel X=2255) in the Inner Orion Spur.

Edit 3: To add to the confusion, despite the journal entry assigning the Y discovery to the Inner Orion Spur, in [Hub > Discoveries > Astronomical Bodies] the game puts that discovery into the Outer Orion Spur.

 

[Bravada Cadelanne]

I have submitted an issue about the inconsistent region (https://issues.frontierstore.net/issue-detail/13286)

Also, all evidence so far points at the region map pixel size being about 49.3494ly/pixel (approx 4096/83 ly/pixel), anchored at the origin.

• The left edge of column 1059 (from the left) would be at X=2276.0126 (between Flyua Dryoae NA-A b33-0 [X=2276.00000] and Flyua Dryoae AB-A c16-1 [X=2276.09375]
• The bottom edge of row 472 (from the bottom) would be at Z=-812.0832 (between NGC 2546 Sector JA-C c14-5 [Z=-812.46875] and NGC 2546 Sector SF-N d7-65 [Z=-812.03125])
• The bottom edge of row 461 (from the bottom) would be at Z=-1354.9266 (between Oochoxt AQ-F a93-1 [Z=-1354.90625] and Outotch FR-R b45-0 [Z=-1354.93750])
• The bottom edge of row 460 (from the bottom) would be at Z=-1404.2760 (between Outotch KF-X b43-0 [Z=-1404.28125] and Outotch KF-X b43-0 [Z=-1404.25000])
• The left edge of column 829 (from the left) would be at X=-9074.3474 (between Eol Prou TY-W a60-0 [X=-9074.62500] and Eol Prou TY-W a60-1 [X=-9074.34375])
• The bottom edge of row 895 (from the bottom) would be at Z=20062.713 (between Eol Prou WG-Z b29-37 [Z=20062.53125] and Eol Prou YB-Z b29-22 [Z=20062.75000])
• The bottom edge of row 1056 (from the bottom) would be at Z=28007.9664 (0.2664ly north of EOR CHRUIA FV-N C20-1724 [Z=28007.7])
• The bottom edge of row 1055 (from the bottom) would be at Z=27958.6170 (0.083ly south of EOR CHRUIA ZO-I D9-8054 [Z=27958.7])

These coordinates constrain it to between 49.349388ly/pixel (from Outotch KF-X b43-0) and 49.349404ly/pixel (from Eol Prou TY-W a60-1).

 

[Rudi Raumkraut]

This shows perfectly how much FD underestimate the meticulosity of their community
(and why they should fear it )

 

[Bravada Cadelanne]

I'm sure others have found this, but one discovery I have made about the region map is that in the galaxy map screen it appears to have 93 evenly-spaced radials (spaced ~3.87 degrees apart), and 30 equally-spaced concentric rings (spaced about 1665ly apart - about 33.75 pixels in the region bitmap), centred at about X=400, Z=26900.


(square grid pattern is due to taking the screenshots at 20kly steps, and Elite Dangerous's darkening of the corners.)
Link takes you to an 8k x 8k image (1 pixel = 12.5ly), with the bottom left corner at approx. X=-49987.5, Y=-24100

Below are the borders I plotted out while investigating the border pixel grid.

 

[MattG]

I'm sure others have found this, but one discovery I have made about the region map is that in the galaxy map screen it appears to have 93 evenly-spaced radials (spaced ~3.87 degrees apart), and 30 equally-spaced concentric rings (spaced about 1665ly apart - about 33.75 pixels in the region bitmap), centred at about X=400, Z=26900.

That’s fantastic work. I was close, but probably still a couple of weeks away from getting there. All that’s needed now is confirming the centre point - which should be easy if same borders on a circle are checked. With that, and assuming same drawing algorithm as FDev, it should be possible to accurately tell region for any system.
We should get an accurate reading of how far apart the circles are - I think ~1665 / ~49 will have to be an integer (= 34).

 

[Bravada Cadelanne]

That’s fantastic work. I was close, but probably still a couple of weeks away from getting there. All that’s needed now is confirming the centre point - which should be easy if same borders on a circle are checked. With that, and assuming same drawing algorithm as FDev, it should be possible to accurately tell region for any system.
We should get an accurate reading of how far apart the circles are - I think ~1665 / ~49 will have to be an integer (= 34).

The 1665ly is based on the outer (30th) circle being slightly less than 50000ly (between 3995 and 4000 pixels on my 8k pixel map).
The outer part of ring 17 is about 574 pixels from Z=26900, which would give a ring spacing of about 33.7647 pixels. To have a ring spacing of 34 pixels, the centre point would need to be at Z=27119.

I have been zig-zagging my way up the border between Inner Scutum-Centaurus Arm and Orion's Hold (my ship has a jump range of 49ly, so I shouldn't miss any border pixels), making my way up to where the border of Orion's Hold passes the horizontal centreline.

Edit: I was playing around in the galaxy map, and it looks like the region name displayed at the top is the region at the bottom left corner of the A boxel the cursor is in, so the actual edge of the region can be up to 10ly away from where the galaxy map region name change says it is.

 

[Spansh]

Fantastic work @BravadaCadelanne it really feels like we're making some progress now. This certainly feels like something we can start making inroads on coming up with an algorithm for.

 

[Bravada Cadelanne]

The ring spacing appears to be 304/9 = 33.777(7) pixels, and the centre appears to be at Z=1034.388(8) pixels (assuming round to nearest - round down would be 1034.888(8)).
Sheet I have used to record ring steps: https://docs.google.com/spreadsheets/d/1Nq7dvlBVUMJNLe-Cy530gRmjF_nulOhNK7m-yBMAo2g/edit

I'll find the X axis ring intersections this afternoon.

Edit: Fixed a couple of errors, and the ring spacing is now somewhere between 33.7857 and 33.7895 pixels.

 

[Latenoid]

I've mapped four species that can only be found in certain regions. I plotted them onto the basemaps of CMDR Cadelanne and CMDR Leth. As you can see, the CMDR Cadelanne basemap is much more accurate. Their correctness is thus confirmed. Thank you for your research, Cmdr Bravada Cadelanne!
...
Problems with uploading :-(
Have a look for better Quality here: German Forum

 

[Michael Ryan]

Is somewhere the list of all sectors and regions where are they?
Even if it's not 100% accurate bacuse some secotors are in two, or three regions if they are on the border

 

[MattG]

Is somewhere the list of all sectors and regions where are they?
Even if it's not 100% accurate bacuse some secotors are in two, or three regions if they are on the border

Holy necro

Not aware of anything, but depends what you're trying to do. You can hit up EDAstro map, turn on both region and sector overlays. You can also search a specific sector on the edastro map with the search icon on top left to see exactly which region(s) it's in.

 

[Michael Ryan]

Ok, maybe different case...

List of all sectors.
I want to do some X,Y,Z coordinates but only for sectors in sector matrix (not coordinates in galaxy).

Like for that example:

Would be X,Y,Z:

Fleckeou: 0,0,0
Freckia: 0,0,1
Streau Eork: 1,0,0
Freckie: 1,0,1
Hyaea Eork: 0,1,0
Myua Theia: 0,1,1
Hyia Eork: 1,1,0
Myeia Theia: 1,1,1

Regions are irreleveant in fact.

 

[Lord Kril]

Is there a way to request a Region property for the FSDJump (or other) event, from FDev? Codex entry just won't do.
I'm currently dabbling with the journals and my own api and would like to be able to have more navigation data. Especially, in the future, concerning colonization.

PS, no intent to necro, but it's like the only thread regarding this issue.