New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved Structure information #203

Closed
jowrjowr opened this Issue Jan 7, 2017 · 3 comments

Comments

Projects
4 participants
@jowrjowr

jowrjowr commented Jan 7, 2017

Currently the structure API information is very minimal. This makes management "difficult".

The following features which are not in the ESI API would be godsends:

  • Fuel. Everything Fuel. Consumption, ETA until empty (in epoch time?), how much fuel in the bay.
  • Security. Full exposure of vulnerability windows, ACL and profile information. Anchor status too, in case something is being ninja-unanchored. Especially current status, reinforced (and how long until it is out, in case it is, and what level of reinforcement).
  • Fittings. "Nice to have." Would be nice to check these things remotely.
  • Services. What services does the structure have for an authorized user?
  • Industry/service information. This would be tricksy but it would be very nice if we could know industry tax, ore refine yields, market tax, industry tax, industry rig bonusing, etc. Everything of that nature.

@aquarhead aquarhead added the New label Jan 7, 2017

@wtfrank

This comment has been minimized.

Show comment
Hide comment
@wtfrank

wtfrank Jan 7, 2017

It would be sensible to put industry/service information in-game on the services tab when you click show info on a structure (as well as on ESI)

wtfrank commented Jan 7, 2017

It would be sensible to put industry/service information in-game on the services tab when you click show info on a structure (as well as on ESI)

@ErikKalkoken

This comment has been minimized.

Show comment
Hide comment
@ErikKalkoken

ErikKalkoken Jan 13, 2017

I am currently mostly working with public structure and the info that I would regard as most important to add to the endpoint is:

  1. Corporation ID
  2. Services

Both should be obtainable for public structures.

ErikKalkoken commented Jan 13, 2017

I am currently mostly working with public structure and the info that I would regard as most important to add to the endpoint is:

  1. Corporation ID
  2. Services

Both should be obtainable for public structures.

@jowrjowr

This comment has been minimized.

Show comment
Hide comment
@jowrjowr

jowrjowr Mar 7, 2017

THE NEW ENDPOINT IS CLOSE ENOUGH.

jowrjowr commented Mar 7, 2017

THE NEW ENDPOINT IS CLOSE ENOUGH.

@jowrjowr jowrjowr closed this Mar 7, 2017

@aquarhead aquarhead moved this from New to Done in ESI Development Mar 27, 2017

@aquarhead aquarhead added Done and removed New labels Mar 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment