Skip to content
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

Endpoint to get accessible structures for a character in system/constellation/region #616

Open
Ligraph opened this issue Oct 23, 2017 · 16 comments

Comments

@Ligraph
Copy link

Ligraph commented Oct 23, 2017

Would be nice to have an authed structure endpoint to get structures that are accessible/visible for the authed character. Could limit by system or region. This endpoint would give structure browser functionality, e.g. the ability yo see all dockable structures in the system/constellation/region.

Many uses, but the one that prompted the post me wanting to make a version of dotlan's jump planner that would prefer systems with dockable citadels.

@Aidansavage
Copy link

This is likely an "after parity" feature, mainly because dealing with ACLs is going to be a big cluster of pain- for us, and for tech co.

@jowrjowr jowrjowr changed the title Endpoint to get accessible stations for a character in system/constellation/region Endpoint to get accessible structures for a character in system/constellation/region Jun 19, 2018
@jowrjowr
Copy link

since using /search as a workaround is now no longer allowed (see: https://developers.eveonline.com/blog/article/the-esi-api-is-a-shared-resource-do-not-abuse-it ) this request matters a lot now.

(edited stations to structures to be correct and more possible to find)

@ghost
Copy link

ghost commented Jun 20, 2018

Now that using /search is no longer allowed, there are several useful usecases that are now banned from ESI, a endpoint like this would really be helpful, especially when writing tools that deal with routing.

7slen8o

@Seavert
Copy link

Seavert commented Jun 20, 2018

What do you mean by "not allowed"? It was announced only about most brutal things like evewho scanning huge intervals to spot player entities.
Location partition is redundant. If you have access to structure - just read system with {structure_id} request.
List of ids is more than enough - but this is separate and monumental topic.

@ghost
Copy link

ghost commented Jun 20, 2018

What do you mean by "not allowed"? It was announced only about most brutal things like evewho scanning

As quoted from the devblog.

From this point forwards, using the search endpoints as a discovery mechanism will be considered abuse of the API

So even legitimate usecases, such as trying to find structures to aid the routing of jump freighters, and other assets are now rather hard to pull off, because you can't scan for them anymore

@Seavert
Copy link

Seavert commented Jun 20, 2018

I'm sure that mistakes about 100-200 inaccessible structures isn't a problem.
Unlike about 10000 nonexistent ids from structure interval (which I assume "discovery" is).

@Blacksmoke16
Copy link
Member

As of now the only way to discover structures that you can dock in is use the authed /search, set filter to structures, and hit up each system name. An endpoint, like this, would be a good replacement and probably reduce some of the load/need to scrap it.

@Slazanger
Copy link

+1 for getting the dockable structures without the need for /Search

@ghost
Copy link

ghost commented Jun 25, 2018

+1 this would be hugely helpful.

@TheCoyote
Copy link

Even before /search discovery was forbidden it felt largely like a hack/workaround.

Some use cases:

  • Navigation software. Plot routes through areas containing friendly structures you can eg. tether your capital to
  • Asset management software (One that doesn't bomb the ESI with requests about assets in inaccessible citadels.)
  • Industry management software. Combine with navigation you can eg. find a shipyard close to you so you can optimize your jump fuel usage.

@QuakeIV
Copy link

QuakeIV commented Feb 21, 2020

I'm going to politely poke at this, because I would greatly benefit from this. This is really killing me right now because some major hubs like Tranquility in Perimeter have their permissions set such that they aren't technically public structures (they dont show up in the public structure API and cannot be discovered automatically) but pretty much everyone has access.

@JacksonWages
Copy link

I'd really like this as well. If there's any way this can be bumped up the list, I'd greatly appreciate it. I'll even send some exotic dancers to whoever pushes the code!

@fluidsonic
Copy link

This would also help with fetching the market more efficiently.

Currently market orders from all structures are returned, even if inaccessible. But I only know that after I've tried fetching info about these structures. That basically forces me to trigger a lot of 403 Forbidden which in turn leads to 420s.

@cvweiss
Copy link

cvweiss commented Oct 7, 2020

I created this awhile back to help with information on these structures: https://www.reddit.com/r/evetech/comments/hvltq3/zkill_22k_structures_w_name_and_position/

@fluidsonic
Copy link

That's a crutch at least.

Are you sure that such data gathering is not violating the terms of service? It's a public collection of private in-game information that you've got through per-player authorization in order to do something useful with it. But likely not to collect and share it.

@graywolf
Copy link

Is there any progress on this issue? I've runned into situation when I need this to complete my script. There are workaround, but none of them is 100% working, so getting this implemented would be great. If nothing else, even query argument for universe/structures that would get the old behaviour back would suffice for my usecase (I can query every one of them later to check for permissions).

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

No branches or pull requests