Materializer - A Material prospecting API and Web App

Under development!

An application for Jumpium Hunters and Scientific Surveyors. The application started up during Distant Worlds expedition. I've decided to open up discussion now because others are taking interest so might as well create a place for it. :)

There are 2 things currently:

Materializer API

A materials database and API. Primarily implemented as a place for EDDiscovery to store/retrieve material data online. Currently has just enough functionality for that purpose. Data is constantly being imported from the Monster Spreadsheet.

Development Project is here:
https://github.com/gregmalcolm/ed-materializer

API link/Schema wiki:
http://api.edmaterializer.com/

Materializer Frontend

This is also a web app under development for viewing and adding data using the API. It is still in it's infancy. Not a lot to see yet.

Development Project is here:
https://github.com/gregmalcolm/ed-materializer-frontend

API link:
http://edmaterializer.com/

Contributing

If you have need to consume data from there a couple of different offerings for getting access. That is on a per comamander registration basis (now available through the frontend app) or though special application accounts (I have to generate ids for this one. Not always a good fit).

I'm also happy take any form of contributions or assistance. Feel free to chat about your prospecting needs here, on Discord channels or by creating Github Issues. I'm also always happy to take Pull Requests for code changes.

Also just spun up a Discord server for more convoluted realtime chat on this... :)

https://discord.gg/0wESJJF3brdY0NVK
 
Last edited:
Hugely looking forward to this.

Actually, in which way is data pulled from the monster, and is it following a specific template at some point ?
I'm keeping records of some data here myself, and would gladly share it once all the analysis side is layed down more clearly.

... If it can be of some help, obviously :)
 
Hugely looking forward to this.

Actually, in which way is data pulled from the monster, and is it following a specific template at some point ?
I'm keeping records of some data here myself, and would gladly share it once all the analysis side is layed down more clearly.

... If it can be of some help, obviously :)

I'm using the spreadsheet api to download the main 4 sheets and update the database every hour at the moment. The schema is roughly similar:

https://www.youtube.com/user/FrontierDevelopments/live

The documentation doesn't mention that theres a Systems table as well now. I've only just added this because EDDiscovery didn't really need it. My web app does though.

Yeah, need to integrate with EDSM at some point too, but one thing at time... :D
 
Well, here's my message that provided the impetus to have a forum post started. I'm posting so people can add their feedback:

What I'd like is something that keeps track of input data by user, for finding errors and stuff, with each user able to modify their own data, a bit how EDSM seems to work. For entering data it has the necessary fields for system, planet and material info all ready to just enter numbers in. Some of the fields might be required, like system coordinates, others optional like star class etc.

On the search side, it should be able to limit a search by Ls distance (max value) and surface gravity range (some min and max value). Then a way to enter your location by system name, if EDSM known, or by map coordinates if off exploring somewhere distant.

The material search fields follows this: Because there are only 6 possible materials per planet (ignoring the very commons), and all the synthesis except premium FSD boost and premium AFMU refill are possible to find on a single planet, a user selects what synthesis they want, and the 6 material search fields would be auto-filled out.
At that point any of them could be changed to something other than the default and results would be displayed by number of matching materials and Ly distance (and displaying all the known elements). There would also be an option to select some materials as required by the search, not optional. An advanced search option would look at materials present in a system as a whole (instead of per planet) and return hits based on that.

SynthesisCommon element1rare element1very rare element1
LocationCommon element2rare element2
max Ls distanceCommon element3
Gravitysearch by planet/ by system toggle


Finally, there would be a way to search for or have indicated incompletely prospected planets, so that interested people can finish them off.
 
Sounds more or less what I have in mind Drownerfood! Though may not be all there in v1. Certainly the search will be better when we get to the point that its also using the edsm points in the search.

The key 3 features I'm focusing on for early versions if the webapp is basic search, jumpium surveys and then detailed data entry/scientific surveys. It'll probably be a little underwealming at first but get better in later iterations.
 
Searching for combinations of materials I think would be good to start out with, because right now we can only search for one at a time using the spreadsheets (have to visually search for secondary mats).
 
I absolutely can't wait for this :D

I will happily be a janitor here as well. Also, if something in The Monster needs fixing to make it fit Materializer let me know. Clean data is good data!
 
Be warned, if you enter bad data, Nexolek will find you! :D

I call for the blame sheet ... :D

Also, the data maintained on my side is more generalistic (Star Data Log + System Log) as the purpose is to compare Elite's engine's procedural generation toward real life MilkyWay, so regarding what's done in the monster it might be TOO generalistic, but if a pattern is starting to appear more clearly there I could just add a "landable verifier" for each celestial body. It's a lot of supposition but as LordFedora has his neural network that predict output of materials on a given landable, the more the data, the more predictions will be precise.

Thus ... it might be a complete dream but ... throught time we might have a workable material finder :p
 
Last edited:
I think the landable part is covered by the planet stats. Although making it easy to just mark a system as landable by clicking a button might be convenient for people who don't want to fill out all the details.
 
Took me a while to get there, but it's now there's a prospector form!

hTtND5H.png


You'll need to be logged in and registered to get add surveys.

The form is just the absolute basics for now. I'll expand it with all the other call things covered by the Monster in due time.

Let me know if you find bugs :)
 
Last edited:
Already found Bug #1. Apparently it doesn't work well on IE10. Every other browser seems ok. I'll get that one fixed soon... :D
 
Hey, this is fantastic! Granted, it hasn't yet helped me in my fruitless search for polonium in The Rift (although I suppose I could solve both problems by getting Mr. Putin to send me a fruit basket). But I'll be putting everything I find since I started keeping track a few weeks ago. So far it's working well.

I found out about this from an authentication error in the latest beta of EDDiscovery, btw. I haven't found any other reference to it in the program, but I gather they are planning on some sort of integration.

Thanks for the hard work!!
 
Heh heh, that's an interesting way to find the app. I beleive the credentials are currently missing from the install media but we're only a little part if the way along with integrating it anyway.
 
I've keyed in the most completed records I've got from my expeditions.
Could you do me a small favour please? Could you assign any records attributed to Zenith to be attributed to me (Zenith Ddraiglas) please? We are one and the same, and I see my prospecting for Varati is included but I didn't enter them into your framework.

So can you tell me more about how this is going to be integrated into EDD2? Will it be like EDSM where we have an API key associated with our login and use that within EDD2 to send data in?
 
Back
Top Bottom