-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prospecting Backend API (EDDB) #49
Comments
A quck backend would be good. EDDB will support it in the future but it But i guess that a solution from others are maybe months away, Den 4 jan 2016 05:44 skrev "Greg Malcolm" notifications@github.com:
|
Hello, I think themroc was asking for help in how it works to model it and I think I need to. May be we should open an issue on EDDB to discuss it |
Sounds good, EDDB ultimately would be an ideal place for it. Where is EDDB the codebase hosted btw? In the interim my app can just act as a api placeholder/prototype. Any preference on the schema? I could just mirror whatever is already in the codebase if it's in the master branch. I haven't actually looked too close to see what you've pushed up yet. |
Still working on a simple schema. I hope to get a idea finnished later 2016-01-04 18:47 GMT+01:00 Greg Malcolm notifications@github.com:
|
EDDB is sadly a closed-source project. Maybe @themroc5 could share his vision here. If we want/need, I'd be willing to create an API for this, or a just prototype for now, whatever we want. |
Yes I want to add body mapping to EDDB. I'm still planning how to approach this but it is coming closer to reality. I don't want to release half finished stuff, so it got to be right. My initial plan was:
Now those questions arised:
I'm afraid I can't offer any realtime data. Still I'd be happy to help wherever I can. |
Would be good if EDDiscovery could upload at least new data thats nonexistent in EDDB. For prospecting in Distant worlds expedition we will record materials on many planets. Even if i will get coordinates for those i prospect on i imagine that not every one will do so. So yes it will be a problem. Nightly json export might be little slow for prospectinginfo to spread. |
As we have a good EDDB discussion going here I've renamed the issue and will talk about the API prototype in another issue. So we don't keep crossing the streams. |
I'm closing this one out for now. We can always create fresh issues if EDSM starts expanding into prospecting data. |
@finwen : Did EDDN work out as a place to store prospector data?
The reason I ask is I'm going to be stuck with the mac laptop next week while out at a coding convention. Putting together a quicky backyend api/db project would be a fun thing to work on while out there. No obligation to stick with it if something better becomes available.
The text was updated successfully, but these errors were encountered: