[CLOSED] EDDB - a site about systems, stations, commodities and trade routes in Elite: Dangerous.

jamfour

jamfour
It would be nice if we could list the security and size of bases on EDDB, as this information is quite useful for engineers. Or, actually, now that I realize it: catalog bases at all! :)
 
Last edited:

djadjok

djadjok
jamfour said:
It would be nice if we could list the security and size of bases on EDDB, as this information is quite useful for engineers. Or, actually, now that I realize it: catalog bases at all! :)
Click to expand...

themroc said:
I have the size of a settlement. So you wanna filter this again by the + ? https://eddb.io/station?i=1&t=16
Click to expand...
I'm sure we have discussed this idea many times. While the settlements sizes are great and it's introduction at least solved the issue with some users entering planetary bases as planetary ports, this information can be also accessed from the in-game map (for already discovered systems). Two other essential parameters - settlement's security level and settlement's "layout" (base model) - are not covered now, at the same time they are accessible in game - for security - only while in same system - and for layout - only on "direct visual", so both of them are first candidates to third-party mapping tool/database. And this information proved to be useful for commanders, you can check this forum thread and this list (info from the latter can be much better reflected on the eddb, maintaining it and manually entering system coordinates is not the thing I' dreaming of=)).
I know that at the moment of the first introduction of settlements in eddb some info on security/layout classification was unclear/uncertain (not speaking about amount of time and work you've already invested in eddb, also introducing great "stellar body" feature). However I think that now most of this "uncertainties" has been solved and the relation between layouts and corresponding FD unofficial "naming" established for all 54 persistent-not-hidden settlement's variations (page "SVS->EDH FNC" in my mapping doc).
As conclusion - it looks like this is a good time to write a new proposal about settlements, and the fact that it's not done already is due to my poor English level, not the absence of actual data.
 

djadjok

djadjok
About possible filtering in application to MEF "safe" search as example:
Using in-game "size" classification (that slightly differs from the "model" size naming) this can be:
(Size:"+++")AND(Security:"Medium")AND(Economy:"Industrial".OR."Exploration".OR."Scientific")
other approach
(Size:"+++")AND(Security:"Medium")AND.NOT(Economy:"Military")
This will filter out all officially "large" settlements where you don't need to put up a fight with one exception - Medium size high/medium security "Extraction" layout (it is "++" in game but in fact it is "+++" by its properties). So the more correct complete form will be:
(...any filter from above...).OR.((Size:"++")AND(Security:"Medium".OR."High"))

heh, I hope no mistakes with parentheses =)
 

Uri

Uri
Hi, I was wondering if a find full ship outfitting feature could be added to the website, per example, an option in https://eddb.io/station to import a Coriolis/EDshipyard ship outfitting and add the ship and all the modules to the filters to be able to look for a station where everything is sold, so isn't necessary to add each module one by one.
 

themroc

themroc
Uri said:
Hi, I was wondering if a find full ship outfitting feature could be added to the website, per example, an option in https://eddb.io/station to import a Coriolis/EDshipyard ship outfitting and add the ship and all the modules to the filters to be able to look for a station where everything is sold, so isn't necessary to add each module one by one.
Click to expand...

This is generally possible. I opened up the search via URL and asked the Coriolis maker long ago to implement this to Coriolis. He now is kinda very rl busy so I'm not sure when/if this is gonna happen. If you get the EDShipyard maker to contact me I'd be more than glad to help him create a link to EDDB for a ship module search.

If nothing helps I might be indeed able to offer a Coriolis/EDShipyard data import function. But then again if any of the references change, I always have to fix my code. My reference IDs will never change again, so imho it's better they link to me instead of me importing their data.
 

Morwo

Morwo
with current state of detail surface scanner we get all elemental matrials a planetoid body contains listed inclusive amount of %. i like to type these new numbers in ross i came across until edmc can fetch numbers due api.

edit:
i like to avoid planets with %-rates less then at least 1.5% of that element im looking for. there are crazy low numbers.
 
Last edited:

themroc

themroc
Morwo said:
with current state of detail surface scanner we get all elemental matrials a planetoid body contains listed inclusive amount of %. i like to type these new numbers in ross i came across until edmc can fetch numbers due api.

edit:
i like to avoid planets with %-rates less then at least 1.5% of that element im looking for. there are crazy low numbers.
Click to expand...

That's coming soon...
 

themroc

themroc
Material distribution!

The official introduction of the detailed distribution of materials on bodies made the logging almost obsolete.

  • The place to input material data is ROSS now. Below the ring input area, a material input area has been established. It is now possible to set specific distribution based material information for every body.
  • The material logger history has been purged. Instead you can find all changes on the Database Change History page on ROSS.
  • And of course the Bodies - Search & Find page has been pimped as well! For every material that is searched in the finder, a seperate sortable column with the distribution value is added to the result list. This will make it easy to find the right body for your demands!
  • Unfortunately, with this update it is not possible to add material data to rings anymore, only bodies and belts are supported now. This might change at a later point though.
Enjoy o7
 

Andargor

Andargor
I debated where to post this or to start a new thread, but ultimately EDDB is where I think this should eventually belong: station orientation, so that one may exit super cruise directly in front of the mail slot. And also because this is one of the places the smart people reside. :D

Now, we all know the following (right?):

- Initially stations were facing the body they orbited (Beta-era, IIRC), but then they were rotated 45 deg. from their orbital plane after launch.

- They still point straight inward, albeit at 45 deg. "up" or "down" (EDIT: actually, in addition to being at 45 deg. from the plane, they also point approx. 20 degrees prograde)

- You know you are on the "correct" side of the orbit when the station is moving counter-clockwise on its orbit (you usually can see this within about 4Mm)

Now easy solution is for FD to update the HUD with station orientation, and then you can just use that to navigate. This has been suggested for as long as I remember and... it's still not there. Moving on.

Now wouldn't it be cool if this was in EDDB? There are however several problems, for which I hope someone has thought of solutions, or perhaps help brainstorm:

- How do you represent the position of the station in EDDB? Or more accurately how do you represent its orbit? Yes, there are parameters in the system panel, and that can probably be used, but it does not indicate which way the station is inclined.

- How do you define "up"? There used to be in-system coordinates dumped when using verbose netlogging, but I believe that is gone. The coordinate system is obviously useful to have a normalized way of describing which way a station is inclined. (EDIT: The netlog does have relative coordinates to what seems to be local origins that vary according to where you are in supercruise or in normal space. In normal space, the relative position could be useful to determine station orientation, but is not seemingly related to supercruise coordinate systems, so to correlate the two is non-trivial)

- Who knows, maybe all stations are actually inclined the same way, e.g. towards planetary +Z (or whatever the rotation axis is). Perhaps there is a correlation with planetary coordinate systems.

- How would a player make use of this information while in supercruise? There is no indication on the HUD of where "up" or "down" is, all that is obvious is the ecliptic.

Any thoughts, or I'm just a crazy old man?

EDIT: I've updated with further findings.
 
Last edited:

Andargor

Andargor
Eventure said:
Abil Midena created a video, how to do that!

Look here: https://www.youtube.com/watch?v=1WHwkyyJi9o
Click to expand...

Actually that illustrates my point. Of course, if you've been to a system before, then you just have to note it down and remember which side of the orbit is the "good" side. However, this method has very little value if it is a station where you haven't been before, and maintaining that list without a tool can be tedious.

This is why it should belong in EDDB: to share this information with other pilots. And my original questions stand, how do you do this? Simply noting on which side the galaxy was for each station is enough or is there a more normalized way?
 
Last edited:

Andargor

Andargor
As a low priority feature request, can the following stellar data be added to the station editing screen?

Orbital Period (float days)
Semi Major Axis (integer km)
Orbital Eccentricity (float)
Orbital Inclination (float degrees)
Argument of Periapsis (float degrees)

EDIT: Added to GitHub: https://github.com/themroc5/eddb.io/issues/110
 
Last edited:

Andargor

Andargor
How to use MongoDB to query EDDB data

For those that wish to use MongoDB to query or crunch EDDB data, here's how I do it under linux (under Windows you could do the equivalent with cygwin and such).

1. Create a shell file to download and update your database

Code: 
#retrieve newer versions of the JSONL (line-delimited JSON) from EDDB
wget -N https://eddb.io/archive/v4/systems.jsonl
wget -N https://eddb.io/archive/v4/bodies.jsonl
wget -N https://eddb.io/archive/v4/stations.jsonl

#for each .jsonl, create import into a collection, and create an index on "id"
ls -1 *.jsonl | sed 's/.jsonl$//' | while read col; do
    mongoimport -d eddb -c $col --drop < $col.jsonl;
    mongo eddb --eval "db.$col.createIndex({'id':1},{'unique':true})"
done



2. Use either a program or the mongo shell to perform your queries

Example:

Code: 
#Start mongo shell with eddb selected
mongo eddb

Enter a JSON query on the command-line, e.g.

Code: 
db.systems.find({"name":"Shinrarta Dezhra"})

Result
Code: 
{ "_id" : ObjectId("57dee14ee724b2d1cda0509d"), "id" : 16827, "edsm_id" : 4345, "name" : "Shinrarta Dezhra", "x" : 55.71875, "y" : 17.59375, "z" : 27.15625, "faction" : "The Pilots Federation", "population" : 85206935, "government" : "Democracy", "allegiance" : "Independent", "state" : "None", "security" : "High", "primary_economy" : "High Tech", "power" : null, "power_state" : null, "needs_permit" : 1, "updated_at" : 1471901589, "simbad_ref" : "", "is_populated" : 1, "reserve_type" : null }



3. Do some more useful stuff.

Here, I wanted to get all bodies in EDDB that have a gravity greater than or equal to 5 and that are landable. Then I wanted to get the system coordinates (equivalent to a JOIN in SQL), and then only retrieve the interesting information (so that I can for example, make distance calculations from a reference system).

Code: 
db.bodies.aggregate([
	{ "$match": {
			"$and": [
				{ "group_id": 6 },
				{ "atmosphere_type_id": 1 },		
				{ "gravity": { "$gte":5 } }
			]
		}
	},
    { "$lookup": {
       "from": "systems",
       "localField": "system_id",
       "foreignField": "id",
       "as": "system"
    }},	
	{ "$project": {
			"_id": 0,
			"name": 1,
			"gravity": 1,
			"system": {
				"name":1,
				"x":1,
				"y":1,
				"z":1
			}
		}
	}
])

Result
Code: 
{ "name" : "Achenar 3", "gravity" : 6.73, "system" : [ { "name" : "Achenar", "x" : 67.5, "y" : -119.46875, "z" : 24.84375 } ] }
{ "name" : "HIP 101504 11", "gravity" : 32.1839, "system" : [ { "name" : "HIP 101504", "x" : 28.40625, "y" : -163.78125, "z" : 213.625 } ] }
{ "name" : "Maia A 1", "gravity" : 14.62, "system" : [ { "name" : "Maia", "x" : -81.78125, "y" : -149.4375, "z" : -343.375 } ] }
{ "name" : "Dryao Chrea GR-W f1-3453 A 2", "gravity" : 6.64, "system" : [ { "name" : "Dryao Chrea GR-W f1-3453", "x" : -1109.15625, "y" : 405.75, "z" : 29262.46875 } ] }
{ "name" : "Mukun A 5", "gravity" : 14661.8, "system" : [ { "name" : "Mukun", "x" : -40.9375, "y" : 31.15625, "z" : -100.25 } ] }
{ "name" : "Selgeth B 6", "gravity" : 11, "system" : [ { "name" : "Selgeth", "x" : -44.1875, "y" : 37.1875, "z" : -115.34375 } ] }



4. ???



5. Profit!

For a full reference to the find or aggregate syntax, please refer to the documentation: https://docs.mongodb.com/manual/reference/operator/
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom