Update for ESI

[mglinski]

Crest is going to get a bullet in it's head sooner or later, either through natural sunsetting or breakage via wontfix bugs. There was a bug in the industry/systems endpoint this release on both ESI and Crest that broke a lot of people's build spreadsheets. The ESI bug is already fixed and live but the crest fix won't go in until the next downtime. Frankly I'm surprised Crest is getting fixed at all.

Can we get this toolset using ESI as much as is currently possible?

[nuadi]

Both the CREST and XML APIs are scheduled for an 8 May 18 sunset ref. So, we have some time to get migrated.

I will have another look at the ESI catalog. Last I had checked, it would have actually been a downgrade to migrate GCS over to ESI. Hopefully, it produces more data at this point.

Since you brought this up, what are the high priority functions that you need migrated? Keep in mind that anything requiring an auth key will take significantly longer to implement.

[mglinski]

My priorities are:

• getRegionMarketPrice
• getNPCLoyaltyStore
• getAdjustedPrice
• getCostIndex
• getItemVolume

It might make sense to make a sister project called googleesiscript and start implementing things in there.

[Marcehs]

I use GCS functions 99% of the time when I am 'playing' Eve online. I have several different purpose built sheets that all revolve around the functions in GCS. I would be heartbroken if all of a sudden they were no longer available... I absolutely love it's functionality, so please keep up the good work and thank you very very much for creating GCS, I love it so much!!!
Here are the functions I have used. The ones with an * at the end are critical to me, so I put them at the top.

Critical:

• getStationMarketPrice*
• getHistoryAdv*
• getAverageDailyVolume*
• getMarketItems*

Secondary:

• getAdjustedPrice
• getCostIndex
• getRegions
• getMarketGroups
• getMarketGroupItems

have used and plan to use more in the future:

• getOrders
• getOrdersAdv
• countStationOrders
• countStationVolume
• getAverageDailyOrders

[nuadi]

So it seems ESI will continue to be a downgrade for GCS. Unfortunately, CCP has failed to recognize that they are providing a public ID for citadel markets, but refuse to provide as little as a name for said ID.

I do not have a means of authenticating with CCP right now. Therefore, migrating to use ESI is going to result in a loss of functionality in the short term.

There is also no endpoint to get all item names and their IDs if they are listed on the market. So, again it is bewildering why CCP would not provide an endpoint for this functionality, but the getMarketItems function will eventually die unless CCP gets their act together.

Due to the ramifications of this migration, I will release a beta script. I'll post in /r/evetech as usual to let you know when it's up.

[Marcehs]

I am simply an end-user but I do appreciate all the work that goes into making GCS. It is interesting to read your remarks about what is lacking in ESI. I do not trust CCP to get their act together. I am sure you will come through with the best possible version of GCS using ESI! I watch with eager anticipation.

[nuadi]

Just an update on this to fill in all involved:

I have been rebuilding my analytics engine using only ESI to learn the layout of the new service and what it will take to update GCES fully moving forward. Fortunately, CCP Bartender and I had a discussion regarding the lack of support for getMarketItems and he implemented a replacement. It's not a parity replacement, but it is a little better in some regards.

The primary issue I am going to have moving forward is that ESI is an ID-centric service architecture, meaning getMarketItems (for example) no longer returns an ID:Name pair, but instead just a list of item IDs. As a result, constructing a lookup table is no longer possible since it could easily deplete one's UrlFetchApp quota for the day with a single function call.

So, this is going to cause a paradigm shift moving forward. If it becomes too much of a problem, I have designed my own service architecture on Google App Engine to support more heavy lifting and will push it if needed. I will have to wait and see what my users say about the new paradigm. At the very least, people will be able to build the lookup table themselves either using the getMarketItems endpoint or the getGroupItems functions - their choice.

[Mezoti]

Hi nuadi

I have been trying to get your esiwalletpull to work, but i am having trouble With getting the CHARACTERID, i have try to use the following lookup =IMPORTDATA("https://esi.tech.ccp.is/latest/search/?search=J%J&categories=character&language=en-us&strict=true&datasource=tranquility"), and i get some weard Numbers that is NOT working in the script, i get a error saying that the id do NOT match the token.
Do you have an idea to what i am doing wrong, or am i getting the characterid the wrong Way.

characterid got changed to character_id recently

[nuadi]

@Mezoti, that is not in my script. I think you have the wrong github project. :)

[Mezoti]

sorry, just notis that it was Fuzzwork that had this script. :-)