I guess you made a mistake on topics, this is EDDN and not EDDB
Release EDDN - Elite Dangerous Data Network. Trading tools sharing info in an unified way.
- Thread starter wolverine2710
- Start date
- Status
Beta of a realtime visualiser for EDDN is up. With the sudden flurry of status pages, I don't know how relevant this is any more, but hey, it's pretty and another way to view the EDDN data.
Features:
Few little visual bugs I want to iron out, but it's working as far as I can tell! Bug reports & feature requests to my private messages for now, while I tidy up the codebase enough to move it to github & allow for proper issues.
Things I already want to do:
Aside: searching for my own web page found a hit in China; apparently someone has already borrowed the source, not that I'm fussed, but an amusing anecdote about how quickly stuff gets crawled.
Features:
- Automatic feed of incoming EDDN data
- Visual display of where the data came from in the Elite galaxy
- Lets you see at a glance most uploader activity, and whether anything might be behaving strangely
Few little visual bugs I want to iron out, but it's working as far as I can tell! Bug reports & feature requests to my private messages for now, while I tidy up the codebase enough to move it to github & allow for proper issues.
Things I already want to do:
- The text billboards are rather ugly to my eyes - these need revamping to be neater and better positioned (but there's a fair amount of maths to tackle so I need some quality free time to look into it)
- Better ways to navigate the galaxy & display system names as you zoom in
- More active link to galaxy updates (EDSC for example)
Aside: searching for my own web page found a hit in China; apparently someone has already borrowed the source, not that I'm fussed, but an amusing anecdote about how quickly stuff gets crawled.
Last edited:
Very nice work.
Just as a heads up, some of the tools have started sending messages with the v2 commodity schema, which features an array of commodities instead of individual messages for each commodity. It was provided by Anthor, and the reference can be found here:
http://schemas.elite-markets.net/eddn/commodity/2
It would be great if tool developers could start supporting this more efficient and faster format.
http://schemas.elite-markets.net/eddn/commodity/2
It would be great if tool developers could start supporting this more efficient and faster format.
Last edited:
wolverine2710
Tutorial & Guide Writer
I don't know who is subscribed to EDDN. What I can provide is a list of tools with authors who have wrote in the the lengthy EDDN that they had created (PUB/SUB) something for EDDN. I've gone through that darned thread twice for ED3PTT, to get all relevant tools/scripts. That way we can send the authors a PM.
Note: With some luck Cmdr Thrudd (who was waiting for V2) has a bit of time and can create a V2 uploader for his tool ;-) On the homepage of his Cmdr Thrudd website he has already mentioned EDMC for uploading data and that it works great with his tool.
Let me know what is needed.
Note: With some luck Cmdr Thrudd (who was waiting for V2) has a bit of time and can create a V2 uploader for his tool ;-) On the homepage of his Cmdr Thrudd website he has already mentioned EDMC for uploading data and that it works great with his tool.
Let me know what is needed.
Last edited:
Once I get 5 minutes, I'll PM the CMDR concerned.
We have a last pull request to finish before pushing the new release to production.
Switching over to v2 schema is little bit more complicated than that. We have to have transition period where EliteOCR, RegulatedNoise, Maddavo's Market Share, EDDB and all the other major players are on board with the switch.
We/you cant just come here all of the sudden and say "hey now we start to use v2", it doesn't work like that. The transition period also varies quite a bit, for me two days notice is nothing but for others even two weeks might be too fast. Switching over to new schema is not something you should take lightly.
And hey, we haven't even agreed on the final v2 schema yet so starting to use it is BIT premature
We/you cant just come here all of the sudden and say "hey now we start to use v2", it doesn't work like that. The transition period also varies quite a bit, for me two days notice is nothing but for others even two weeks might be too fast. Switching over to new schema is not something you should take lightly.
And hey, we haven't even agreed on the final v2 schema yet so starting to use it is BIT premature
Switching over to v2 schema is little bit more complicated than that. We have to have transition period where EliteOCR, RegulatedNoise, Maddavo's Market Share, EDDB and all the other major players are on board with the switch.
We/you cant just come here all of the sudden and say "hey now we start to use v2", it doesn't work like that. The transition period also varies quite a bit, for me two days notice is nothing but for others even two weeks might be too fast. Switching over to new schema is not something you should take lightly.
And hey, we haven't even agreed on the final v2 schema yet so starting to use it is BIT premature
We let a month for people having complains on the v2, and I heard from no one
Some publishers are already preparing to switch, so i'll have to contact subscribers and follow the conversion progress.
Once the conversions are made, publishers can switch to v2.
The conversion for subscriber from v1 to v2 is very trivial, I made some examples on the github repository and it shouldn't take more than 5 minutes to do it.
If you have a better solution, I'm all ear, I do not tend to have the perfect solution however.
We let a month for people having complains on the v2, and I heard from no one
I was just about to say something similar
v2 has been live for a month and a half. I imagine the way forward here will be for us to announce an end-of-life date for the v1 schema - without a deadline, there's no real incentive for developers to do anything (I know, I'm a developer!) - but I don't know what that date will be.
I will implement v2 in EliteOCR over the weekend.Just as a heads up, some of the tools have started sending messages with the v2 commodity schema, which features an array of commodities instead of individual messages for each commodity. It was provided by Anthor, and the reference can be found here:
http://schemas.elite-markets.net/eddn/commodity/2
It would be great if tool developers could start supporting this more efficient and faster format.
wolverine2710
Tutorial & Guide Writer
@Snakeman. Sometimes emotions take over (no problem) but remember "The tone makes the music".
Like Anthor and James have said a draft for V2 was announcement (and live) and everybody could comment on it. In fact it was announced on the 15th of April. Its also on the OP. Not many commanders have commented on it. Aside from EDCE (url) the last week two new "mobile api based" (url) tools have emerged, EDAPI (url)and EDMC (url). All links found/read on redit so they are independent of the FD forum). This has the potential that a LOT more data is going to come to EDDN. V2 is much more efficient and faster then V1. Anthornet didn't push/decide anything. It was discussed in the EDCE email group and it was decided that now would be a good time to introduce V2. EDCE and EDMC will both switch to V2 asap. EDAPI does not use EDDN atm but hopefully that changes as well. I'm gonna recommend V2 to him. Glad to see that Seebek is going to implement as well. After all atm his tool sends the most messages to EDDN.
Note: Cmdr Thrudd who doesn't use EDDN because V1 causes technical issues for him was waiting for V2. Perhaps he's able to send data to EDDN as well in the near future. That would bring a lot more data to EDDN ;-). His site is quite popular....
Update: I´ve removed the url(s) to be in compliance with the FD forum rules. Apply google-fu.
For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
Like Anthor and James have said a draft for V2 was announcement (and live) and everybody could comment on it. In fact it was announced on the 15th of April. Its also on the OP. Not many commanders have commented on it. Aside from EDCE (url) the last week two new "mobile api based" (url) tools have emerged, EDAPI (url)and EDMC (url). All links found/read on redit so they are independent of the FD forum). This has the potential that a LOT more data is going to come to EDDN. V2 is much more efficient and faster then V1. Anthornet didn't push/decide anything. It was discussed in the EDCE email group and it was decided that now would be a good time to introduce V2. EDCE and EDMC will both switch to V2 asap. EDAPI does not use EDDN atm but hopefully that changes as well. I'm gonna recommend V2 to him. Glad to see that Seebek is going to implement as well. After all atm his tool sends the most messages to EDDN.
Note: Cmdr Thrudd who doesn't use EDDN because V1 causes technical issues for him was waiting for V2. Perhaps he's able to send data to EDDN as well in the near future. That would bring a lot more data to EDDN ;-). His site is quite popular....
Update: I´ve removed the url(s) to be in compliance with the FD forum rules. Apply google-fu.
For more information about and an overview of OCR error Free (OEF) aka mobile api based tools see this FD thread.
Relevant thread: Any news on the official ED API ?
Last edited:
That's okay we forgive you. But could you tell us why are you angry?
I was just about to say something similar
v2 has been live for a month and a half. I imagine the way forward here will be for us to announce an end-of-life date for the v1 schema - without a deadline, there's no real incentive for developers to do anything (I know, I'm a developer!) - but I don't know what that date will be.
I haven't done any work on supporting v2 because I had not known that it was finalised. I was kinda waiting for a msg here with a timetable for transition.
I suggest that we get some concensus on a timetable for transition so that we can have enough time to get our listeners/publishers tested and released. Something like:
- listeners/publishers should have v2 ready for test by dd/mm, (suggest anytime now)
- v2 test schema will then commence until dd/mm, (suggest two weeks)
- if all OK then v2 schema will go live, (same date as previous)
- v1 schema will be unsupported on dd/mm (a month or two?)
Since we are anything but organized, we would need a timetable to get a consensus on a timetable
The best approach for listeners/consumers is simply to look at the schema used in the message and handle appropriately whether v1 or v2. I'm being obvious here, I know...
Since users don't update their software until they are forced to, I would suggest looking at the stats as time goes along, and phase out v1 when it makes sense to do so. But consumers such as you and other community devs count for a lot with regards to phasing in and out stuff.
Last edited:
I would like to add schema v2 in the next version EliteOCR which I plan on releasing on Sunday and dump v1 all together. I know this is rather radical but since I have the most influence for now this would force most receiving points to update (add v2).
I know this will cause confusion and anger at the beginning. The positive side: angry users will create pressure on the services.
I'm not even sure I should ask your opinion here. I think I should just be the bad guy and take the blame. (I will not even cry over lost users. I think they should switch as soon as possible to those other "OCR error free" tools)
I know this will cause confusion and anger at the beginning. The positive side: angry users will create pressure on the services.
I'm not even sure I should ask your opinion here. I think I should just be the bad guy and take the blame. (I will not even cry over lost users. I think they should switch as soon as possible to those other "OCR error free" tools)
That's assuming that the interface that those other tools rely on remains in place - which isn't a given.
Last edited:
wolverine2710
Tutorial & Guide Writer
I received from the author of the "OCR error free" tool EDAPI the following headsup.
He first reported that EDAPI gave an error when the installation of PP on the Fs servers began. Later EDAPI worked again and he mentioned the above. So it seems things still work. Its totally possible that a lot of the PP stuff will not be in the JSON structure. BUT we have to wait till PP lands and we use our arsenal of "OCR error free" (I like that phrase - OEF) tools to check and verify things.
Note: The author mentions TD because his tool is specially made for that. There is a standalone version and a plugin for TD. The standalone version aside from updating the .prices file of TD also shows some stats info. EDAPI does not upload to EDDN (atm).... Both versions (afaik) DO however ALSO update the .stations file of TD.
Last edited:
Given that a bit of work has to be done updating other things due to the Powerplay release, and I would actually like to have some time to play and then there is stuff IRL, I'm not in favour of transitioning in such a short timeframe. Plus I have enough self-imposed pressure, I don't need more pressure from angry users and don't see it as a positive.
Can you push that back a week please?
Hello All!
Author of EDAPI here. I've implemented EDDN v2 support this evening and it's working great in test. I'm not having any luck in prod.
I'm very sorry is this is obvious, but quick question... it seems test accepts and broadcasts both v1 and v2. Does prod broadcast v2 yet? Or is that what this whole discussion is about?
EDIT: Never mind I suppose. It's working now. It's just somewhat inconsistent whether or not my receiver sees the post.
Author of EDAPI here. I've implemented EDDN v2 support this evening and it's working great in test. I'm not having any luck in prod.
I'm very sorry is this is obvious, but quick question... it seems test accepts and broadcasts both v1 and v2. Does prod broadcast v2 yet? Or is that what this whole discussion is about?
EDIT: Never mind I suppose. It's working now. It's just somewhat inconsistent whether or not my receiver sees the post.
Last edited:
- Status