Glorious HIPs - 3306

Slice 33 is finally finished! (along with the carrier-only systems from slice 32)
Results are as follows

....
Also, question regarding systems with approximate coordinates: For unreachable systems is it still acceptable to put in the approximate/partial coordinates in the sheet?

You can put them in the notes column if you want, but they must include the word "unreachable" somewhere. (I leave any "unreachable" notes untouched).

If you have the coordinate data already, it might be easier to complete the table in the same way you did for slice 32.
 
You can put them in the notes column if you want, but they must include the word "unreachable" somewhere. (I leave any "unreachable" notes untouched).

If you have the coordinate data already, it might be easier to complete the table in the same way you did for slice 32.

Yup, I will add them to the notes in the future. Wouldn't want to corrupt actual coordinates columns with approximate data.
 
I have updated the spreadsheet with the latest data from edsm.
Also included are unreachable star approximate coordinates where known.

I now have several hundred unreachable star coordinates, but not yet all of them.
My next project is to find the closest edsm star, and it's distance, to each of them,.
This is quite a challenge, and will require a lot of computer power.
 
Well, it didn't take too long to find all the nearest visited stars to each of the "Unreachable" stars.
Some of them are apparently within FC range ;
Remember that some approximate coordinates are more approximated than others..

ED Name HIP number Approx.coordinates Nearest Visited Actual Coords Distance
HIP 72147 HIP 72147 (-1020, 2828, 891) "HIP 72062" ( -948, 2833, 953) 95.3
HIP 115414 HIP 115414 (-1472,-2522, 330) "HD 221296" (-1367,-2501, 247) 135.2
HD 224502 HIP 118195 ( 30,-2945, 670) "HD 225112" ( 122,-3089, 684) 171.8
HD 14589 HIP 10914 ( 870,-2600, -500) "HD 16715" ( 964,-2468, -607) 194.7
HD 151328 HIP 82053 (-2365,-2507, 2177) "HD 203347" (-2482,-2282, 2110) 262.4
HD 88866 HIP 50209 ( 2140, 2390,-1130) "HIP 50922" ( 2089, 2248, -897) 277.0
rt caeli HIP 20665 ( 2310,-2500,-1290) "HD 28686" ( 2202,-2478,-1562) 293.1
HD 88194 HIP 49824 ( 1900, 2300,-1240) "HD 88071" ( 1705, 2491,-1401) 317.3
HD 87740 HIP 49571 ( 2030, 2400,-1300) "HD 88071" ( 1705, 2491,-1401) 352.6
HD 88666 HIP 50091 ( 2100, 247,-1200) "HIP 50922" ( 2089, 2248, -897) 375.2
HD 93178 HIP 52625 ( 1640, 2900,-1030) "HD 92425" ( 1995, 2773, -948) 385.6
HD 126032 HIP 70293 ( 30, 2600, 1487) "HIP 68292" ( 107, 3029, 1206) 396.6
HIP 76908 HIP 76908 (-1478, 2551, 1318) "HIP 73960" (-1109, 2634, 1061) 457.0

And here are today's top 10 most unreachable stars

HIP 84939 (HIP 84939 ) (-19435, 9015, 26212) "Pha Aud VL-B d14-0" (-19981, 2061, 27028) d= 7023.3
HD 89775 (HIP 50749 ) ( 9400, 9000, -5500) "HD 69561" ( 9994, 1894, -5677) d= 7133.0
HD 202946 (HIP 105367 ) ( 410, -9679, 9532) "Flyae Phreia TM-W d1-0" ( -459, -2580, 9341) d= 7154.7
HD 83685 (HIP 47444 ) ( 11000, 9500, -7100) "NGC 2506 MMU 1112" ( 9831, 2232, -8087) d= 7426.8
HIP 106727 (HIP 106727 ) ( -8629,-10119, 8020) "Preia Hypoea VO-Z d13-0" ( -6691, -2578, 9107) d= 7862.1
HIP 106710 (HIP 106710 ) ( -7201,-10985, 9259) "Auq Eaec GM-T d4-0" ( -6920, -2871, 10897 ) d= 8282.7
HIP 105452 (HIP 105452 ) ( 315,-10985, 11401) "Grooe Hypue MR-C d0" ( -214, -2745, 13025) d= 8415.3
HIP 106142 (HIP 106142 ) ( -9898,-10985, 9879) "Eafaiscs BQ-V d3-0" ( -7929, -2743, 10794) d= 8523.6
HIP 110978 (HIP 110978 ) (-10895,-10995, 9590) "Flyai Phraa QE-H d10-0" ( -9984, -2333, 10056) d= 8721.9
HD 270920 (HIP 23177 ) ( 20178,-10985, 2167) "Whuefua ZK-N d7-0" ( 19856, -1938, -416) d= 9413.8
 
Last edited:
Meanwhile, preliminary parsing for Slice 43 is finished and has revealed
  • 30 unreachables
  • 66 not found
  • 30 carrier-only systems
and a further 76 already mapped, either "named" systems or sent to EDSM by other CMDRs. The rest are ripe for the taking.
Sadly no intriguing invisible systems or other anomalies, but the furthest system in the slice is a whopping ~33000ly from Sol, out in Tenebrae in between arms and not reachable.
The system names are in the sheet and known coordinates should show up on the next EDSM script run.

On another note, I found out the hard way that there's a 128 bookmark limit to squadrons as well. Why do you do this to us FDev :D
Also @Iron Body I updated the coordinate notes for the unreachable systems in Slice 33. Not sure if these made it in your search.
 
Last edited:
I wasnt very active lately, so my progress on my slice 1 was rather slow. But now finally finished 🥳
Some raw statistics:

  • systems i visited and should be available on EDSM now: 274
  • unreachable systems (few of them might be reachable with a FC): 72
  • systems with non HIP/HD names, most of them in the Bubble: 40
  • systems i didnt visit, but already on EDSM: 2
  • not found systems: 127
  • untagged systems: 33

Was surprised by the large number of systems i couldnt find on Galaxy Map. Also didnt expect to find untagged hand made systems on the main highway to Sag A. but there were some, most unexpected find was a 267RSol untagged red giant.

If anyone needs more detailed data, let me know. I can also provide access to my spreadsheet.
 
I have just completed the weekly update of the spreadsheet coordinates with 343 new entries.
Also entered the approximate coordinates of even more stars reported as being unreachable. But not sure how many.

There are new reports of unreachable systems (even with FC) with entries in EDSM.
For example, HD 151 (HIP 516) which is 3727ly below the bubble, yet has a visited entry in EDSM.

It may be possible to add entries in EDSM without a visit, but I don't know how.
 
There are new reports of unreachable systems (even with FC) with entries in EDSM.
For example, HD 151 (HIP 516) which is 3727ly below the bubble, yet has a visited entry in EDSM.

It is possible to reach HD151 with the following route:
Prooe Dryeia EU-B c2-0 (496.74ly)
Nidgiae CU-Z d0 (497.06ly)
HD 257 (274.13ly)
HD 224778 (494.30LY)
HD 223934 (410.6LY)
HIP 117566 (395.9LY)
HD 151

I found this route by searching the dump data from EDSM with a bespoke 'C' program to start with, and then finalised it with
the fleet carrier router planner https://spansh.co.uk/fleet-carrier

Spansh's carrier program/data didn't find HD 151 so failed to calculate the full route.
It shows that it is worth using Spansh's route finder to check a route, but of course it wouldn't find a route to a star not already in EDSM.
My 'C' program can hunt for known stars in EDSM within 500ly of any position, regardless of whether there is a star there or not.
I would suggest to Spansh that it would be good for edge explorers to be able to put in coordinates rather than star names.
 
IIRC the Gap Jumper tool allows direct coordinate input, as well as some very "wide" routing options, allowing it to find a route with a much larger detour than the default router or the spansh router, if needed. It's still only as good as the most recent EDSM snapshot, but it could help you.
 
Lastly, we have HIP 52199, HD 69262 and HIP 52992. These are systems I visited pre-FSS (and in fact pre-Journals). As a result, I can't scan the main stars and would need to map some of the other bodies, and so I can't mark them finished in EDSM. Can someone please visit and scan these 3 if you happen to be near them.

Been there, done that (on my I need to visit & delete some bookmarks near the bubble trip). Should show up after the EDDN/EDSM sync is finished.
Plus, found an undiscovered system with 2 terraformable HMCs, 1 tf WW with a 1 tf Rocky Moon, and a 1 non-tf WW just 1 jump away from HD 69262 at Col 173 Sector EN-J D9-23.

On that occasion I couldn't read and vistied HIP 69262 in the first place. :oops:
 
Just completed the weekly update of the spreadsheet.
No reported completed sectors, but 112 new entries this week.

On my way back to finish clearing up slice 3 now, got to Colonia and picked up my original Python, it's home now and it's staying. Probably a couple of thousand LY to go and maybe 20 or so FC accesible only systems to visit.
 
This is my first post on the ED forums, been digging for an exploration project to take part of and it seems I've found one that piques my interest! I just fitted up a brand new 'conda and this feels like the perfect project for it.

Just to clarify and make sure I'm reading the thread history correctly, exactly which data needs to be manually input into the spreadsheet as we search? Just the in-game names, right? And the coordinates will fill themselves in next time the sheet is synced with EDSM data?
 
Need to also note which stars are in the spreadsheet but not in game and which stars are in the spreadsheet, in game but otherwise unreachable because too far outside the galaxy body. There's a notes column for extra comments and the "does not exist" can go in the name column.
 
Gotcha, thanks. I've started work on Slice 27 and have already been keeping tally of those things. Of course I happened to pick the slice that runs through that large area of unknown-permit-locked systems near the Witch Head/Orion/Barnard's Loop/Horsehead nebulae...so it looks like a heavy chunk of these will be unreachable.
 
Gotcha, thanks. I've started work on Slice 27 and have already been keeping tally of those things. Of course I happened to pick the slice that runs through that large area of unknown-permit-locked systems near the Witch Head/Orion/Barnard's Loop/Horsehead nebulae...so it looks like a heavy chunk of these will be unreachable.

There's almost always a few unreachable because outside ship jump range, just make a note of those outside your jump range but close enough for a FC, 500ly to the closest star is all we need, if you don't have access to a FC just post the list here and one of us with a FC will go and scan them.
 
This is my first post on the ED forums, been digging for an exploration project to take part of and it seems I've found one that piques my interest! I just fitted up a brand new 'conda and this feels like the perfect project for it.

Just to clarify and make sure I'm reading the thread history correctly, exactly which data needs to be manually input into the spreadsheet as we search? Just the in-game names, right? And the coordinates will fill themselves in next time the sheet is synced with EDSM data?

Welcome to the Glorious HIP project.

You only need to enter the in-game name into the spreadsheet if it is not an HIP or HD style name, these get found automatically.

I maintain separate lists because some folk (like me) find it easier to use their own lists rather than update the spreadsheet every time.
For example ...
a) unreachable stars, preferably with good estimates of coordinates
HIP 75175 , HD 137001 , -2217, 3109, 479.
HIP 78460 , HIP 78460 , -2873. 3258, 745.0

b) not found stars
HIP 100100
HIP 100113
HIP 100173

c) named stars (ie not HIP or HD names)
HIP 88033 Gliese 9608
HIP 49908 Groombridge 1618
HIP 85017 Gungnir

If you post lists here they will get picked up and included in the next update of the spreadsheet, usually on Sundays.
Lastly, it's obvious but not been mentioned, you should use either EDdiscovery or EDMC to upload your travel data to EDSM.

Any more questions, just ask.
 
OK, I am just about to start slices 52 and 53 together. So have updated the spreadsheet (sheet 2 "Tranches") with that info.
Just a reminder that we can't update the opening posts from Jackie atm, so the spreadsheet is the place to look for free slices.
 
Seeing as it's the end of the year, I figured the campaign logo needs some quick christmassing

glorious_hips_patchx.png


Happy holidays CMDRs!
 
Back
Top Bottom