search

KSP-KOS / KOS

Fully programmable autopilot mod for KSP. Originally By Nivekk
Other
697 stars 230 forks source link

Provide optional API access to SCANsat data #881

Open hvacengi opened 9 years ago

hvacengi commented 9 years ago

Inspired by a requests in this post: http://imgur.com/a/eWYHC Use the SCANsat api to expose data based on satellite scans. First pass information should at least include bio-me data. Terrain elevation data would be a 2nd pass. With future ability to access resource maps and other data exposed by SCANsat.

I also think that I'd like to find a way to integrate it with RemoteTech communication checking, but that would be after getting the framework up and running.

Feel free to comment on implementation ideas and/or syntax concepts.

hvacengi commented 9 years ago

Adding a link to the applicable api in the dev branch of SCANsat, just to keep it all together: https://github.com/S-C-A-N/SCANsat/blob/dev/SCANsat/SCANutil.cs

erendrake commented 9 years ago

@hvacengi with 1.0 having some kind of scanner included. do we want to implement this for scanSAT or for the stock scanner first?

hvacengi commented 9 years ago

My short answer is yes. I think that stock data should be higher priority than interacting with a mod.

The long answer: I'll have to look at how they implemented the 1.0 data. Right now, the scansat api is a little less helpful than I originally thought it was going to be. I can still make it work, it will just take a little more effort.

It looks like 1.0 offers a "surface survey" or some such. We might use that as a baseline if scansat is not installed, with possibly more limited information. I'll have to see what info they give us in stock, and how it compares to the information that the users will want to get. I did not watch any streamers over the weekend using this feature, so it will really be a surprise for me when I load up 1.0. What small amount I did see appeared to be less involved than truly mapping the planet.

And I think that there is a part that will tell you the amount of ore at your current location, which we should expose to the user I think. It might be that it uses the same method as existing "sensors" in which case it would be pretty easy to include.