Player Features and Ideas Discussion

For example in system crest endpoint:

Tanoo system Crest endpoint

you have a list of stargates:

"stargates": [
{"id_str": "50000056", "href": "https://crest-tq.eveonline.com/stargates/50000056/", "id": 50000056, "name": "Stargate (Akpivem)"},
{"id_str": "50000057", "href": "https://crest-tq.eveonline.com/stargates/50000057/", "id": 50000057, "name": "Stargate (Sasta)"},
{"id_str": "50000058", "href": "https://crest-tq.eveonline.com/stargates/50000058/", "id": 50000058, "name": "Stargate (Yuzier)"}
]

and for solar systems is easy enough for me to save all the systems to computer in various formats especially since i can iterate through:

Systems Crest Endpoint

There is no such endpoint for all stargates for understandable reason. This being the case, since its easy enough to be able to scrape data from the systems endpoint in bulk, to simply include at least the stargates destination system name and/or id, would make things considerably easier. Baring creating a spider to map the Stargate network, If the destination system of a stargate was included in the above dictionary it would mean it would be easier for a person to create personal and custom navigation script/program without requesting the destination for every gate through crest. I know we are already partially there by stripping away characters from the gate name, but it seems like an unnecessary difficulty especially since we have the id i personally feel the destination system is of more value than the gates name. Since we can also look it up, or i would think its easier to construct the name string, since its a set format of a string with the destination name inserted into it.

Just my thoughts