Should be working again. I told Tromador over Discord and he renewed the certificate.URL: https://elite.tromador.com/files/systems_populated.jsonl
Error: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:997)>
Thank you ! Dankeschön !Should be working again. I told Tromador over Discord and he renewed the certificate.
Hello Tromador, all not so wild ...Sorry, I had an accident, fell down the stairs and that tended to make me forget about such things. Fortunately, I have an SSH client for my android tablet.~
In other news, if anyone is interested in helping with a bit of testing and is comfortable with the tech, I want to see if we can use pypy to speed things up, or if it breaks things. I'll be doing some testing, but other datapoints would help.
$ trade.py import myfile.prices
If using the wildcard, will this effectively act as a "batch" update by updating all files, or would I need to import using the edmc_batch plugin?trade.py import mystation.prices
trade.py import *.prices
Just to clarify, "C:/Elite Dangerous/TD" is the location of your database, not your installation. Your CWD is the directory you are in when you run the trade command, so if you ran it from for example "C:/Elite Dangerous/TD (legacy)" instead, you would have a separate database with the same TD install.Have been looking at this for a little while, finally got round to giving it a go and worked a treat at making a fair amount of money in a starter ship in half a dozen trades. I do have a few questions I'm hoping I can get some clarification on, as I'm not entirely clear after reviewing the wiki/documentation.
Note: I've installed TD using the pip install method to the folder C:/Elite Dangerous/TD (aka my working directory "CWD"). The .exe files were installed by pip to C:\Program Files\Python311\Scripts. Used the terminal window as admin to run trade import eddblink which appears to have worked correctly, creating a data subfolder containing the database files within my CWD.
As long as you know what the location is, it doesn't matter.I'm using EDMC and was intending to output TD market data files and then update the database from these, however my attempts at this have been unsuccessful.
1. What should I use as the destination folder in EDMC for the output files? In the screenshot on the wiki it uses C:/Trade. I had originally used my CWD, however had problems trying to run the update command and want to verify if the issue may be related to the output folder I selected.
Please provide examples including the output, like so:2. Which folder should I be located in when updating the database with the EDMC output files? Again, I tried running this from within the CWD and it failed to recognise the .prices files, even when I've explicitly provided the file path/name in the command line.
C:\TradeDangerous\test>trade import -h
C:\Program Files\Python\Python3.11\Scripts\trade: TradeDangerous help
usage: trade import [--plug PLUG] [--url URL] [--download] [--ignore-unknown] [--option PLUGINOPTIONS]
[--reset-all | --merge-import] [--help] [--debug] [--detail] [--color] [--quiet] [--db DBFILENAME]
[--cwd CWD] [--link-ly MAXSYSTEMLINKLY]
[filename]
Optional Switches:
filename Name of the file to read, or, used with '--url', will save the downloaded file as this name.
--plug PLUG, -P PLUG Use the specified import plugin.
--url URL URL to download filename (default "import.prices") from.
--download Stop after downloading.
--ignore-unknown, -i Data for systems, stations and items that are not recognized is reported as warning but
skipped.
--option PLUGINOPTIONS, -O PLUGINOPTIONS
Provides a way to pass additional arguments to plugins.
--reset-all Clear the database before importing.
--merge-import, -M Merge the import file with the existing local database: only loads values that have an
explicit entry with a newer timestamp than the existing data. Local values are only removed if
there is an explicit entry with a 0/0 demand/supply price.
Common Switches:
--help, -h Show this help message and exit.
--debug, -w Enable/raise level of diagnostic output.
--detail, -v Increase level of detail in output.
--color, -c Add color to output for enhanced readability.
--quiet, -q Reduce level of detail in output.
--db DBFILENAME Specify location of the SQLite database.
--cwd CWD, -C CWD Change the working directory file accesses are made from.
--link-ly MAXSYSTEMLINKLY, -L MAXSYSTEMLINKLY
Maximum lightyears between systems to be considered linked.
This sub-command provides a plugin infrastructure, and comes with a module to import data from Maddavo's Market Share
(http://www.davek.com.au/td/). See "import -P maddavo -O help" for more help.
>trade import C:/Elite Dangerous/TD/example_file.prices
you would get the following:>trade import C:/Elite Dangerous/TD/edmc-export.prices
P:\Program Files\Python\Python3.11\Scripts\trade: ERROR: unrecognized arguments: Dangerous/TD/edmc-export.prices
usage: trade {import} ...
'myfiles.prices' is an example.3. The wiki setup guide has the import command for EDMC files as follow - is "myfile.prices meant to be used as a literal, or is an example only (i.e. replace myfile.prices with name of actual prices file)?
Wildcards can be used in filepaths.4. The wiki user guide suggests that wildcards can be used to import data:
If using the wildcard, will this effectively act as a "batch" update by updating all files, or would I need to import using the edmc_batch plugin?
>trade import *.prices
, TD would attempt to import all .prices files it found in that folder.I have no idea if TDHelper still works, I don't use it myself. The original developer quit working on it, and I haven't heard from the current maintainer in years. I'm not surprised it doesn't work anymore.Sorry for all the questions. I've read through the last dozen pages or so of the thread and I noticed that there's definitely a trend towards encouraging the use of TDHelper. Unfortunately, I've had zero luck getting the app to read my commander data and the github wiki has very limited information and seems to date back to 2018. To be honest, I feel quite comfortable executing through the command line over a gui provided I can work out the last couple of kinks in the update process.
>tradegui
. It's not great, and I'm being very slow at making it better, but I'd say it meets minimum usability requirements.Bravada saved the dumps after the announcement: https://edgalaxydata.space/EDDB/dumps/Does anyone have a copy of stations.jsonl and systems_populated.jsonl from prior to EDDB going down? I can get something working if I can get those. The only copies I presently have are the HTML of the goodbye notice and none of the data, which will make TD choke.
Eyeonus has sorted the server side, so we are now receiving new data, but TD itself also needs some work so I need to use the old files to give it something to think about until we work out another solution.
Fantastic. I had some from like 9 months ago, but not ideal.Bravada saved the dumps after the announcement: https://edgalaxydata.space/EDDB/dumps/
./trade.py import -P journal
./trade.py import -P edapi -O save,csvs
FDEVJRNDIR
set to the journal directory and the edapi plugin will ask you to log into your fdev account (like EDMC).$ ./trade.py import -P journal -O help
Plugin that parses the Journal file and add or update systems and stations.
Options supported by this plugin:
--opt=date Only parse Journal files from date, format=[YY]YY[-MM[-DD]].
--opt=last Only parse the last (newest) Journal file.
--opt=show Only show the system or station. Don't update the DB.
You can also chain options together, e.g.:
--opt=show,last,date
$ ./trade.py import -P edapi -O help
Plugin that downloads market and ship vendor data from the Elite Dangerous
mobile API.
Options supported by this plugin:
--opt=csvs Merge shipyards into ShipVendor.csv.
--opt=edcd Call the EDCD plugin first.
--opt=eddn Post market, shipyard and outfitting to EDDN.
--opt=login Ask for login credentials.
--opt=name Do not obfuscate commander name for EDDN submit.
--opt=save Save the API response (tmp/profile.YYYYMMDD_HHMMSS.json).
--opt=test Test the plugin with a json file (test=[FILENAME]).
--opt=warn Ask for station update if a API<->DB diff is encountered.
You can also chain options together, e.g.:
--opt=csvs,edcd,eddn
Hm, I don't know how you run TD. On windows you can set up environment variables over a GUI. The path to the gui in german win10 is:Hello @gazelle , thank you for your tip . Unfortunately I have a problem with this environment variable.
I play on a Windoof PC and I looked at the hint to set the variable in the text file of TD\scripts\README.txt, but I can't deal with it.
Is there any way to make it easier ?
C:\WINDOWS\System32>set FDEVJRNDIR=C:"\Path\to\journals"
C:\WINDOWS\System32>setx FDEVJRNDIR "C:\Path\To\Journals" /m