Mysterious LocationID

EVE Technology and Research Center Third Party Developers
1

Hey All ESI question

So when pulling assets a character has, you get the following:
[ {
“type_id”: 10246,
“location_id”: 1023318669768,
“location_type”: “other”,
“item_id”: 1024500659790,
“location_flag”: “Hangar”,
“is_singleton”: false,
“quantity”: 5,
“type_name”: “Mining Drone I”
},
{
“type_id”: 41649,
“location_id”: 9001385739000254000,
“location_type”: “other”,
“item_id”: 1026140437377,
“location_flag”: “AutoFit”,
“is_singleton”: false,
“quantity”: 1,
“type_name”: “Small Ancillary Remote Shield Booster Blueprint”
}]

Awesome cool stuff, looking at other posts with people asking about locationIDs you have Stations which are coded at the 60000000 range, so you can look up a station that way, and structures are in 1000000000000 range.

But here is where the issue starts, what the hell is 9000000000000000000 ??? The above JSON has that locationID and it kills the universe/structures/9001385739000254000/ end point. If you don’t believe me try it yourself.

PS: CCPlz give me a universe/location/names endpoint

2

Probably a container that that item is in. Check to see if another object has an item_id of 9001385739000254000

3

Nope, there isn’t… Still lost about this one.

4

Hmm, where is the item actually located?

5

that location_id is a so called fake item

6

A fake item?

Yeah and I can’t find it in my ingame asset list…

So should I just ignore any items without a proper location_id matching a station or citadel? Strange that CCP is feeding us these items then.

7

well you cant access these items so id petition them bc they are still yours

8

Possible it is in asset safety?

9

You should create an ESI issue for it: https://github.com/ccpgames/esi-issues/issues
You’re not the only one getting the strange locationIDs, some of the jEveAssets users are getting them as well. I’m not able reproduce it myself, so, I don’t have the data to create an issue for it.

What to include in the bug report:

  • The character name or id you’re getting this on
  • The strange locationID
  • The endpoint name
10

I have create a ESI issue for this:

11

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