Is there a route for querying system details in bulk?

EVE Technology and Research Center Third Party Developers
, ,
1

Is there a route for querying system details in bulk?

I see EVE Swagger Interface route however,
/universe/systems/{system_id} only gives one system detail.

For example if I want to query a route using EVE Swagger Interface with /route/{origin}/{destination} but with more details on the system I have to perform N follow up queries for each system in the returned route of system_id’s. Local caching aside, there is still the issue of that first uncached bulk query.

For example this is problematic if you want a command line tool (using PowerShell for example) to query a route with system details. You’re spawning off N thread jobs (not a problem but just moving parts to wait and receive results for) for each system in the route rather than just one more query for the bulk route details. For tools like this you’re probably not locally caching anyway for simplicity.

Basically spawning follow up queries in PowerShell like this

foreach ($system in $route){
      if ($Parallel.IsPresent){
        $threadJobs[$routeIndex] = Start-ThreadJob -Name $routeIndex -InputObject $system -ScriptBlock {Get-EveSystem -SystemId $input}
        $routeIndex++
      }

waiting and receiving the results like so

    if ($Parallel.IsPresent){
      Wait-Job -Job $threadJobs -Timeout 60
      foreach ($threadJob in $threadJobs){
        $routeDetail[[int]$threadJob.Name] = Receive-Job -Job $threadJob
        Remove-Job -Job $threadJob
      }
    }
    $routeDetail
2

No, for that you can use Fuzzwork dumps and a database:
https://www.fuzzwork.co.uk/dump/latest/mapSolarSystems.sql.bz2
Querying EVE API for such nearly static data is bad resource usage.

3

No, I don’t want to consume more dependencies, it’s a module with functions written in Powershell for command line use.

What you’re asking me to do is bloat up a simple command line tool. No Fing way.

It is not a desktop app, it is not a hosted website, it’s a COMMAND LINE TOOL, a FEW FUNCTIONS.

As for static resources, SDE parity checklist · Issue #1103 · esi/esi-issues · GitHub is a ticket to move them into the API.

4

It’s just against the way the API wants to be used. Your tool is an edge case in this case.

Just because someone wants to see this in the API doesn’t mean that it’s a good thing.

5

Ahh yes the ESI is for websites only thinking.

Eve itself is an edge case in the gaming world.

6

Not what I said.

7

Well, what else is the API for if somebody doesn’t want it?

The whole point of the API is for somebody to use it.

I have no problem sending 100 query threadjobs every time I use the tool then. I am not going to bloat up my app just to suit your “no no” desires and hinder what is simply copy a PowerShell module across to deploy.

8

The API is for “changing” data. For static data you have the dumps. That’s a healthier way for the API’s resource usage.

9

That’s filed under “not my problem”.

The direction is to move to API parity SDE parity checklist · Issue #1103 · esi/esi-issues · GitHub

image
image968×157 21.4 KB

Source: SDE parity checklist · Issue #1103 · esi/esi-issues · GitHub

I am not going to code against something that is to be DEPRECATED.

10

Everyone can file feature requests. To assert that CCP wants to comply to this and will is pire speculation. The time this request is open doesn’t really support your assertion.

I am sure the API doesn’t care about your problem and I have a guess who will “win” this fight…

11

ESI is dead anyway, CCP abandoned it long ago. SDE to be deprecated too.

Not sure what you’re winning.

12

Yes, it’s easier for some people to think of their dream way but that’s not how it works.

13

You’re like the goblin who pops up in every topic just to respond, for the sake of it, see Roadmap for third party developers and the API - #2 by Paz_Lammaschtu you add nothing of value.

Powershell works with Objects, I don’t need your formatting or bloat.

14

I see you are not interested in a solution. Do yourself and the community a favour and leave the forum.

1 Like
15

Not yours no, if we followed your solutions, hosting a simple “hello world” in the cloud would have umpteen modules and services behind it and cost a fortune.

image
Figure 1: You

16

Classy, you act like you’re some kind of godlike entity with a non-answer for everything.

17

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.