Guide / Tutorial Complete list of all third party tools, spreadsheets, manuals and other data sources

wolverine2710

Tutorial & Guide Writer
Its done. All tools/threads mentioned in the EDDN thread are now in ED3PTT. What is left is the "What is the most efficient way to crowdsource the 3D system coordinates" thread. This will be a piece of cake, a walk in the park. It only has 2190 posts in it atm. Me hitting brick wall with head - multiple times.......

Luckily I did create a partial list of tools in that OP - last updated a few months ago. Some are NOT in ED3PTT atm. BUT I know for a fact that there are relevant tools/threads in it which need to find their way into ED3PTT. I guesstimate in total 8-12 more entries to add. This will NOT be done in the next days...

Its Kingdsay (dresscode orange) today in the Netherlands and tomorrow will be lost also. Perhaps starting Wednesday I will have some time for the last thread. After that I can die in peace, so to say ;-)

Note: If I had known upfront how much work this whole thread, ED3PTT would be my newly found shrink would have told me: DO NOT DO IT.....

Live long and prosper.
 
Last edited:
Congrats!

g1395350382515600057.jpg
 

wolverine2710

Tutorial & Guide Writer
It seems I will not have time to fill ED3PTT any further at this time.

I've to do some stuff for EDDN. Also have to speak with biobob about the requirements for ED3PTT and how to progress. All of which takes time.
After all that dust is settled I will go ahead with adding new entries to ED3PTT.
 

wolverine2710

Tutorial & Guide Writer
[B said:
Andargor[/B];2173184]EDCE has just been released.

Copy/paste from my post in the EDCE thread:
Because of my "third party tools thread" commanders seem to find me. I've already been contacted by a commander who is using the EDCE data and displays the results. A picture indeed says more then thousand words. Mindblowing. Perhaps the tool will finds it way to the public soon.

Andargor: I appreciate the time so put into the tool. It could change third party tools landscape as we know it. I very much like the way you try to minimize the effect of the usage of the iOS API - hardcoded time limits, not running it constantly (till we have a way to dectecting docking in a 100% (as in 1000%) reliable way). I'm confident other commanders using EDCE will do the same. Remember: With great power comes great responsibility. Hence use the tool wisely as in minimize the usage of it - as it queries the FD servers.

I DO hope that although unsupported by FD they are going to tolerate it. At least till the full fledged ED API is released.
BUT for that all commanders using EDCE must minimize its usage. So the load on the FD servers is minimal. This includes authors using EDCE as a base for their tools. Do NOT run EDCE every time you want to parse the .json file for testing. Just run EDCE once and then operate on the .JSON file to see how it displays in your tools.

Note: A lot of tools like the BPC and other trading tools which rely on manual input data have an option to import data in the form of a .csv file. This is either a file in the format of an EliteOCR format .csv file or in the case of the BPC a .BPC file (which basically is a slightly tweaked/enhanced EOCR .csv file). I'm hoping a tool using EDCE will create such a file. It would mean a lot of new and good data for trading tools.

@Andargor: Perhaps something to consider by you or other commanders. In case of Trade Dangerous. Its using a .prices file. If a tool using EDCE would edit its .prices file (for the station currently docked at) it would mean a lot of more good data for TD.

Edit: Headsup. Relevant for EDDN listerners/subscribers. See also the posts following it.

Update: I´ve removed the urls to be in compliance with the FD forum rules. Apply google-fu.
For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
 
Last edited:
The EDCE thread has been closed by the moderators, pending Michael's decision. The thread has not been deleted, I will keep you posted.

I'm afraid I saw that coming a mile off. The problem is that the site that the EDCE accesses is what drives the iPad app (and may well also have the potential to affect the performance of the main game servers) and if 3rd party dev's start using the EDCE and write badly behaved app's (e.g. that don't follow your guidelines about not accessing it frequently) then they could flood and/or crash the site (inadvertantly, or deliberately). I don't see promises to use the tool wisely cutting it frankly. Sounds like Andargor's reverse engineered an API they didn't agree to publishing and, well meaning as everyone directly involved with this is, that's a bit of a no-no really.
 

wolverine2710

Tutorial & Guide Writer
ED3PTT is coming along quite nicely. Its reaching the point that a release is possible in the not to distant future. No ETA ;-)
A lot of the requirements/wishes I stated before (OP) are already implemented. You WILL be surprised!! Will keep your informed about the progress.
 

wolverine2710

Tutorial & Guide Writer
EDMC: E:D Market Connector

Released Today by Otis B. ED Market Connector
Added to ED3PTT.

Copy/paste from the OP of the ED Market Connector thread.

ED Market Connector
ED Market Connector is a new app that downloads commodity market data and, at your choice, either:



The user-interface is deliberately minimal - just press the "Update" button when you land at a station to automatically download and transmit or save the station's commodity market data:



You can download it here (from the GitHub repository hosting service)) for Windows 7+ and Mac OS 10.9+.

Please contact me if you're interested in packaging for Linux or in providing localization.

The app is inspired by and provides similar functionality to EDCE, but is hopefully a little easier to use and adds an offline mode.
Both this app and EDCE use the "Companion" interface that Frontier supplies to support their Elite Dangerous iOS app. This interface isn't officially supported, so could go away at some time in the future.

Update: I´ve removed the urls to be in compliance with the FD forum rules. Apply google-fu.
For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
 
Last edited:
What would really be nice is if one of these connector based applications would export a .csv for use with Cmdr Thrudds Elite Trading Tool. As it sits, we still have to run Elite OCR to update data on his site.
 

wolverine2710

Tutorial & Guide Writer
What would really be nice is if one of these connector based applications would export a .csv for use with Cmdr Thrudds Elite Trading Tool. As it sits, we still have to run Elite OCR to update data on his site.

I interpreted his post as that it would have support for EOCR files. Afaik a .bpc file is nothing more then a bit hardened .eocr file. I can imagine that when you create a post in his thread or send him a PM that he is willing to support eliteocr as well. After all the tool has just been released. Would indeed be superb for Cmdr Thrudd.
 
Last edited:
What would really be nice is if one of these connector based applications would export a .csv for use with Cmdr Thrudds Elite Trading Tool.
I've used Thrudd's in the past but I don't have enough rank to upload. Please try this version of the E: D Market Connector app and let me know whether Thrudd is happy with the data that it produces.
Edit:
Release 1.30 of E: D Market Connector supports exporting to CSV for use with Thrudd's Trading Tools.
 
Last edited:

wolverine2710

Tutorial & Guide Writer
EDAPI: Elite Dangerous API Tool

Publicly released Yesterday by bitbucket user Orphu.
Name: EDAPI: Elite Dangerous API Tool
Added to ED3PTT.

From the Overview page of the bitbucket repository for EDAPI by Orphu.

Code:
==============================================================================
EDAPI: Elite Dangerous API Tool
Requires Python 3.4, requests, and TradeDangerous.
==============================================================================
Automates pulling your profile information from the mobile API, and populating
TradeDangerous with station, market, and shipyard data.

==============================================================================
== Command line usage:
==============================================================================

Either place edapi.py in the TradeDangerous root, or tell it where to
find TradeDangerous with the --tdpath option.

usage: edapi.py [-h] [--version] [--debug] [--import FILE] [--export FILE]
                [--vars] [--basename BASENAME] [--tdpath TDPATH] [--no-color]
                [--keys [KEYS [KEYS ...]]] [--tree]

EDAPI: Elite Dangerous API Tool

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  --debug               Output additional debug info. (default: False)
  --import FILE         Import API info from a JSON file instead of the API.
                        Used mostly for debugging purposes. (default: None)
  --export FILE         Export API response to a file as JSON. (default: None)
  --vars                Output a file that sets environment variables for
                        current cargo capacity, credits, and current
                        system/station. (default: False)
  --basename BASENAME   Base file name. This is used to construct the cookie
                        and vars file names. (default: edapi)
  --tdpath TDPATH       Path to the TradeDangerous root. This is used to
                        locate the TradeDangerous python modules and data/
                        directory. (default: .)
  --no-color            Disable the use of ansi colors in output. (default:
                        False)
  --keys [KEYS [KEYS ...]]
                        Instead of normal import, display raw API data given a
                        set of dictionary keys. (default: None)
  --tree                Used with --keys. If present will print all content
                        below the specificed key. (default: False)

==============================================================================
== TradeDangerous plugin usage:
==============================================================================

Copy edapi_plug.py to the plugins directory in TradeDangerous. Use the
import command to connect to the API and import price and shipyard
data.

./trade.py import --plug edapi

Update: I´ve removed the urls as its against the FD forum rules for this kind of tool. Apply google-fu.
For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
 
Last edited:

wolverine2710

Tutorial & Guide Writer
(To be) found on another big well known Elite Dangerous forum.

The tools are already in ED3PTT so no action needed.

Note: Perhaps I add this overview as well to ED3PTT because its concise - but probably have to change urls so they point to ED3PTT.

A copy/paste snippet from the thread: "Mobile API" based tools. Ideal for trading, logbook, exploration, ship-loadout tools.
Similar (mobile api based) tools

As with other tools like trading tools there is no such thing as "one size fits all". Some commanders like a GUI, some like a command line tool, each trading tool has pros and cons (depending on the commander). For each and every tool there is a (different) audience. Which is great. The same is true for tools which use the mobile API.

At the moment of writing (20150604) there are three publicly available tools. I know there are quite a few more but those haven't been publicly released. All three have in common that they are written in Python and are open source. The source code is available on repository hosting services like Github and Bitbucket. Should a certain tool X not have a certain functionality all its takes for a coder is to look at the alternatives, update X with the needed functionality and create a pull request for it. The author of tool X can then decide if it should be merged in his/her tool.

In alphabetical order (tool. thread name)

  • EDAPI. EDAPI: Elite Dangerous API Tool. With Trade Dangerous support.
  • EDCE aka edce-client. EDCE: Elite Dangerous Companion Emulator
  • EDMC aka EDMarketConnector. Thread. Elite: Dangerous Market Connector


Update: I´ve removed the urls to be in compliance with the FD forum rules. Apply google-fu.
Relevant thread: Any news on the official ED API ?
 
Last edited:
I've used Thrudd's in the past but I don't have enough rank to upload. Please try this version of the E: D Market Connector app and let me know whether Thrudd is happy with the data that it produces.
Edit:
Release 1.30 of E: D Market Connector supports exporting to CSV for use with Thrudd's Trading Tools.

Annnd it's gone. I know the official policy is still in force, but since Michael indicated that they are discussing allowing the use of the Companion API, as long as it doesn't impact FD, can we have a bit of tolerance for these kinds of tools until official word?
 

wolverine2710

Tutorial & Guide Writer
damn, thats just sad, an simple and easy small app like that is precisly what is needed.

The author of EDMC has created a thread on redit for support, discussion. You can find it here (url).


Update: I´ve removed the url(s) to be in compliance with the FD forum rules. Apply google-fu.
Url involded. Thread name: "Elite: Dangerous Market Connector".

For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
 
Last edited:
Back
Top Bottom