EVE Technology Lab

 
 

EVE API and Public CREST discussion

First post First post First post
Author
C C P Alliance
#141 - 2014-05-06 10:48:04 UTC
Leebe wrote:
I noticed the "columns" attribute in the rowset of PlanetaryPins mention "headRadius" but it is missing from the rows.
(also the columns don't mention longitude and latitude)

columns="pinID,typeID,typeName,schematicID,lastLaunchTime,cycleTime,quantityPerCycle,installTime,expiryTime,headRadius,contentTypeID,contentTypeName,contentQuantity

row pinID="1011768140479" typeID="2848" typeName="Barren Extractor Control Unit" schematicID="0" lastLaunchTime="0001-01-01 00:00:00" cycleTime="15" quantityPerCycle="21296" installTime="2013-08-25 17:07:49" expiryTime="2013-08-25 18:37:49" contentTypeID="0" contentTypeName="" contentQuantity="0" longitude="-3.11917281639712" latitude="-3.11917281639712"


Working on a fix now, will get it out ASAP.

@CCP_FoxFour // Technical Designer // Team Size Matters

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

C C P Alliance
#142 - 2014-05-06 10:48:26 UTC
Aithnee Hayes wrote:
I'm trying to access /char/PlanetaryColonies but it is returning an empty colonies rowset for both of my characters that actually have PI colonies. I'm using an API with all feeds on...

Anybody else had this problem?


Is this working for you now? I haven't changed anything but also have not seen any other reports of this problem. :/

@CCP_FoxFour // Technical Designer // Team Size Matters

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

C C P Alliance
#143 - 2014-05-06 10:49:31 UTC
Polarina wrote:
Can the attribute "description" be added to /char/Medals.xml.aspx for the "currentCorporation" rowset? It is present in the "otherCorporations" rowset.

The legacy API keys granted access to /corp/Medals.xml.aspx, getting the description was easy and trivial from that endpoint. With the new customizable keys, it is not possible to get the medals' descriptions without a corporation key form a director or the CEO.


This seems reasonible... will see what I can do.

@CCP_FoxFour // Technical Designer // Team Size Matters

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

C C P Alliance
#144 - 2014-05-06 10:53:12 UTC  |  Edited by: CCP FoxFour
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.

Please continue this disscuission here: https://forums.eveonline.com/default.aspx?g=posts&m=4558401#post4558401

@CCP_FoxFour // Technical Designer // Team Size Matters

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Official Winners Of Takeshi's Castle
#145 - 2014-05-06 11:15:51 UTC
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.
Official Winners Of Takeshi's Castle
#146 - 2014-05-06 11:28:22 UTC
Bloemkoolsaus wrote:
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.


+1. Speeds up WH content creation.
Split Infinity.
#147 - 2014-05-06 11:33:41 UTC
Quote:
Bloemkoolsaus wrote:

CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.

+1. Speeds up WH content creation.


Another nerf for folks that create content in the game.. sad sad sad Sad
#148 - 2014-05-06 11:36:37 UTC
Sounds like bull. Does CCP hate wormholes? It keeps getting ****** with, for the worst.
Unseen Wolves
#149 - 2014-05-06 11:37:19 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.


Here we go: while I have to agree that from clearly technicall standpoint this is correct - we cant see kills data on map for wspace, removing this data affects wspace gameplay and should looked at from game design viewpoint.

In wspace we have to strugle with a lot of issues to get content. We leave in barelly working posses, have to roll for hours to get pvp content, heavly rely on third-party apps to do basic stuff like knowing our conection map.

Information about kills lessen some burden of rage-rolling for pvp as we caj faster assess if given system is promising we we shoul spend time and scan chain from it or close it and roll more.

Ofc one can say that kill data only show past kills and its not guaranted to have anyone logged in still in that chain but its a filter kind off thing, something that slightly ease out hard life of wspace. And as such IT SHOULD BE DISCUSSED AT LEAST WITH WH REPRESENTATIVE ON CSM.

Also - during ff you said that you are thinkimg about providing all killmails trough api. Soooo that contraditcs this change. If you will get greej light for km's then what you are sayijg is this: I will not tell you how many kills where in this system, but this is a list of all 23 of them.
Galaxy Spiritus
#150 - 2014-05-06 11:40:48 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.

RMTers finnaly paid a bill to CCP or what? just cant find another reason for CCP to do it
Pandemic Legion
#151 - 2014-05-06 11:45:27 UTC
Is there a chance to get some timetable instead of "whenever I have time"? Would be nice to have time to test some existing tools so that people aren't suddenly left with broken mappers.

If thuggin' was a category I'd win a Grammy

#152 - 2014-05-06 11:48:21 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.

But that's only because we (the whole dwellers) don't have a nice ingame, ccp made map.
The rest of the eve residents do have a map, in which case they can see the stats without a problem.

So to counter this problem we made our own maps, tools ander other whatnots
=>
Bloemkoolsaus wrote:


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.

And now you are telling us we wrote our maps with info we should not have?
Because it to powerfull? If that's really the case, maybe it should be removed from the game and not only whole space.

Come on think this over, we need this info as much as other eve players.
We even worked for it, unlike non whole residents, we fiddled, tinckerd and tried untill we had our own tools and maps.

don't take that away from us ccp.
#153 - 2014-05-06 11:51:32 UTC
Also THIS =>
Max Kolonko wrote:
And as such IT SHOULD BE DISCUSSED AT LEAST WITH WH REPRESENTATIVE ON CSM..

C C P Alliance
#154 - 2014-05-06 11:58:39 UTC
Bloemkoolsaus wrote:
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.


What do you mean by status?

@CCP_FoxFour // Technical Designer // Team Size Matters

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

#155 - 2014-05-06 12:01:58 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.


You should not break tools people have already written.

At the very least this is an issue for the CSM, because these endpoints are widely used.

-

Diplomatic Immunity.
#156 - 2014-05-06 12:03:19 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.


Could we at least get some discussion as to the reasons behind you think it's a powerul tool and discuss it with our WH CSM rather than just removing a valuable tool from WH space?

It's hard enough to get content in WH space without you removing tools we use to help us find it...

Resident forum troll and fashion consultant

#157 - 2014-05-06 12:05:05 UTC  |  Edited by: Hidden Fremen
CCP FoxFour wrote:
Bloemkoolsaus wrote:
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.


What do you mean by status?


As in, is this system active? Are they going to be active?
Caldari State
#158 - 2014-05-06 12:05:45 UTC
CCP FoxFour wrote:
Hey guys,

as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint. This is data that exists in the API but not the client and is incredibly powerful. As with everything I am open to discussing this, but I will admit that you will have a damn hard time convincing me of not doing it.


I think this is a mistake, as many others that use mapping tools that show this information. It has already been stated that this little bit of intel generates content (fights).

If you want to think of it in a more realistic matter - Scientists can right now detect and track "explosions" in space (Armageddon anyone lol). So it makes sense that in a universe as advanced as EVE that sensors could detect ship explosions. Now when ship jumps were removed from w-space It did make sense - realistically it would be hard to believe you could track a ships movements in a far away solar system in such a way you could tell when it left/entered a system versus simply losing track of it for a moment.


Keep w-space kill API end-points!

Creator of Tripwire mapping tool - EVE-O thread

Twitter | daimian.mercer@gmail.com

#159 - 2014-05-06 12:06:12 UTC
CCP FoxFour wrote:
Bloemkoolsaus wrote:
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.


What do you mean by status?



Having the kill history gives us an idea if there will be people online in the next x hours, or were active x hours ago. The API pulls show kills over an hour ago, so even if we see activity as "now" it was really "an hour ago" and probably isn't active now.
Official Winners Of Takeshi's Castle
#160 - 2014-05-06 12:07:08 UTC
CCP FoxFour wrote:
Bloemkoolsaus wrote:
CCP FoxFour wrote:
as a heads up as soon as I can find the time I will be removing WH systems map/kills endpoint.


Our wormhole mapper software relies on this information to determine the current status of the systems we are connected to. I would very much like to keep this information in the API as the information it provides is essential for us.


What do you mean by status?


NPC/PVP kills recently = explore the system cause people are clearly here.
Forum Jump