Search: materials

[gregmalcolm]

We need the ability to look for planets that have specfic materials. I thin the search box string would look something like this:

"Ceek mat:Y mat:Cad mat:Cb"

... which would find planets with ytriam, carbon and cadmium for systems with CEEK in the name.

The selection for this would likely be checkboxes in an advanced search page. We'ed need to add something to the backend to support this kind of search. I think searching on world_survey model for those attributes would be a good way to do it.

[BloodyRain2k]

There's http://api.edmaterializer.com/api/v4/surveys?resource=Tin but it seems that the resource parameter is not working yet.
Was hoping it would be after finally finding it but ah well.

[gregmalcolm]

Sorry, resource actually refers to the rock type. Such as "Mesosiderite".
Also BINARY will pull back surveys with checkboxes rather than numeric results. A thing we inherited from the "Monster" spreadsheet.

Tell you what, I'll implement something for the api to look up materials this week, because it's an easy thing to do.

[BloodyRain2k]

That'd be so nice, I'd really like to find out where there's some Tin near me : /
Found tons of that before 2.1 but didn't need it at all so I had 0 when it became literally a rare sight.

Also if 'resource' refers to the source type it might be worth considering to rename it appropiately, like 'source'.
And having Outcrop 1 and 2 is just doing what FD did, bad naming : (
How about changing these to Rocky Outcrop and Metallic Outcrop?

[gregmalcolm]

Ah, well before I started the project the authoritative source collections was the "Monster" prospecting sheet:

https://docs.google.com/spreadsheets/d/1LgMaX9n6Yp8DQKq-u-eF1HH2xQ-_aUgSfSJna6mTuLs/edit#gid=574066838

Materializers mission is pretty much to make the need for this spreadsheet redundent. It actually imports data from it on a regular basis. Because of this I just kept their terminology to some extent, hence "resource". But I agree a better name could be worked out. If I did that though I'd be more likely to use "source" on the frontend app and leave the api be until I was sure it was going to stick.

Funny you should mention the renames of "Outcrop 1" and "Outcrop 2". I've had the same thoughts, I just haven't got around to doing something about it. I've kept it as the others so far because that's how I import them from the Monster. I'll be ditching BINARY and AGGREGATED at some point too, because tickbox vs numerical surveys should be a different attribute.

Anyway... I've been sidelined into another project (engineers spreadsheet to webapps) so probably won't be getting onto this as quickly as I'd like to. In the meantime, this might of help:

https://docs.google.com/spreadsheets/d/187DlDf_WOhpXtem686ffvuNAcd8G6W5d7061UNAjslU/edit?usp=drive_web

It only has data from Monster I think, but at the moment that accounts for much of it.