BUT I now foresee a problem with timezones. I am in +11:00 at the moment and the timestamp for each price doesn't account for timezone.
Before I modified tradedangerous I always used the ingame time for the timestamp. To get the data I use screenshost, so my first screenshot was of the station display (which includes the date/time) and than the item list (It helps to have a two monitor setup, one side screenshot and the other the editor).
Now I automaticly use CURRENT_TIMESTAMP (which is always UTC) for new entries with the "update" command of tradedangerous.
Sorry, I didn't follow that much. Are you saying that you use some switch in trade.py which includes the UTC timestamp? Did you edit that yourself or is that standard? I didn't see a switch for that in "trade.py update -h". Could you run me through the procedure to get UTC timestamps?
Wolverine: Take a look at "SourceTree" from Atlassian, I use command-line git in the easy command-line cases. When I run into a problem or I know I'm likely to, I bring up SourceTree
-Oliver
$ git remote add bgol https://bitbucket.org/bgol/tradedangerous.git
$ git pull bgol update_all_switch
@maddavo (and anyone interrested):
I've created a clone of tradedangerous on bitbucket and commited my changes for the "update" command.
- changes to the "update" command:
- new [--all] switch - Generates the temporary file with all columns and new timestamp.
- if the station is unknown it will generate a list of all items with "0" prices/demand/stock
Q: How do I get it?
A: Use git (add my repository and pull from it)
Code:$ git remote add bgol https://bitbucket.org/bgol/tradedangerous.git $ git pull bgol update_all_switch
I've tagged the changes, so only this will get merged.
INSERT INTO "System" VALUES(327,'Perkwunos',-40.500125,46.749916,6.749930,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(328,'LP 274-8',-29.738246,44.949649,20.326609,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(329,'Rho Coronae Borealis',-29.874378,42.095439,22.217774,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(330,'LP 386-49',-25.530545,33.376693,25.999697,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(331,'LP 329-18',-26.624757,39.874844,23.280697,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(332,'LHS 3124',-26.281543,43.432673,24.188797,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(333,'LHS 399',-13.562117,36.157422,25.780629,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(334,'LHS 396',-9.875744,30.840733,20.469069,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(335,'OT Serpentis',-11.125686,30.341506,18.407225,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(336,'DE Bootis',-7.437122,32.625116,16.999972,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(337,'Veren''s Stop',-12.968789,21.967734,20.281170,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(338,'G 181-6',-20.312616,20.312786,14.062621,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(339,'Marcov''s Point',-22.342586,14.626760,17.655981,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(340,'LP 229-17',-23.031609,9.032729,8.970076,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(341,'G 203-51',-15.874793,12.031296,5.343640,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(342,'Bidmere',-7.436494,13.219486,1.904265,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(343,'Wise 1405+5534',-8.030538,13.438036,-1.844549,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(344,'LHS 455',-16.905804,10.219086,-3.437526,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(345,'LP 71-165',-20.906919,11.092810,-2.218044,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(346,'LHS 465',-23.937852,12.217715,-0.623736,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(347,'Austern',-25.155543,15.344502,9.374928,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(348,'G 202-48',-15.531001,14.375125,1.875516,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(349,'2MASS 1503+2525',-6.187486,17.999670,8.124526,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(350,'DG Canum Venaticorum',-3.125089,25.529649,2.687266,'2014-10-15 00:00:00');
INSERT INTO "System" VALUES(351,'LP 378-541',1.187879,20.719592,2.343413,'2014-10-15 00:00:00');
Here are some additional star systems I've mapped the estimated coordinates for:
Thanx Harbinger. How did you estimate the coordinates? Do you know about the 1/32LY quantisation? I read somewhere all the x/y/z positions are rounded to 1/32LY .
Nice, I added them to my fork. I have made a plot hereHere are some additional star systems I've mapped the estimated coordinates for:
Code:..Snip..
Yep, being pushed back bit by bit.Are all these forks and branches reintegrated into the master at some point?
I fail go get an impression what is the most feature- and data-complete version.
Nice, I added them to my fork. I have made a plot here
Got some other coords from JesusFreke and Wolverine2710.
Got up to 386 systems now!
Well they are in bitbucket, but in SQL format. My fork is HERE and this is file you need TradeDangerous.sql. However separating the data from the code is probably a good idea.Thank you for this compilation.
I wonder if it would make sense to create a github/bitbucket project where system coordinates could be kept with this information. Perhaps in json format that can be parsed by anyone easily. I guess most people interested in using them are programmers anyway.
Well they are in bitbucket, but in SQL format. My fork is HERE and this is file you need TradeDangerous.sql. However separating the data from the code is probably a good idea.