It appears that bodies.jsonl is not just no longer updated (for the reasons mentioned earlier), but also no longer available. Just the bodies_recently. Could I trouble you to upload the last built one somewhere please? Although to be frank, I'm only looking for the ELWs and AWs from there, and will be filtering those out and discarding the rest anyway, so a smaller dump containing just those would be perfectly fine - for me. I imagine others will find these useful too, either the whole body data or a filtered one. So, even if it's not an automatic update, could you upload a manual one please?
Adding to the list of "I miss bodies.jsonl". I, too, would like a one-off generation - or some other solution.
Would it be possible to get it semi-regularly - say once a month, or even one a quarter? And with, say, a monthly version of Recent Bodies ? I (and I expect many others who use it for exploration purposes) tend not to update it every 2 days, more like every couple of months...
**Reposting from another thread in hopes EDDB will make my Christmas dreams come true
Yes, this is pretty much what I was worried about and so I attempted to normalize the numbers a little. I used the two independent variables and multiplied the percentages after removing outliers to try to establish some figure which would be useful.
I should specify that the ELWs shown here were the only ones with coordinates available (until EDDB returns my call) and represent only about 15% of ELWs in the database. Therefore, it is very likely the data is skewed, simply because only the CMDRs who took the time to submit data with coordinates likely know very well how to find them, and I believe Allitnil submitted at least a few hundred so it should definitely be met with a grain of salt.
As far as "small numbers" this was and is a concern, but I should specify I took ALL systems into account (15,332,441 systems at the time of download.) Which is EVERY system with coordinates added to EDSM. Unfortunately, if I were to cutoff intervals with say, no less than 50k systems, we would only have data extending to +/- 1,200 Ly. Unfortunately, until I have access to the data I am at a bit of a standstill.
In the meantime, I threw this together, which is simply the number of discovered ELWs in interval/total systems in interval.
It looks pretty similar to the last graph but maybe useful while we wait.
will i ever be able to sort the search results by more then one column?
it kinda sucks when i am searching for something that has eg. the highest of criteria 1, but is also the closest to my reference system (criteria 2)
i know, sorting tables by two criteria seems to be the most obvious thing for users, but the hardest thing for coders?
or else i would not even have to ask for something so fundamental everywhere i am confronted (looking at you UI FDEV)
would be nice to get a column with "estimated jumps"
since sorting by multiple criterias to work, requires data with identical numbers to work.
only if criteria 1 is identical, there is a chance for sorting criteria 2
so breaking down "distance" to "jumps" would solve this.
simplier: let me put in a search radius, reducing the result from 20k entries to 50 or so
what about systems and stations search?
im more often in search for systems in a certain state and population with a certain goverment, then looking for bodies with a certain composition
even more when the new engineer update comes