I have experimented a bit with the api and came up with a program that generates live EBuLa based on api info. Unfortunately the api misses some data that would be great for the EBuLa so the ebula creator is currently pretty limited in info and function current limitations: only signal and speed data for a short part of the upcomming tracks are displayed, so for routes with long distances without signals or speed limits parts of the ebula can be empty due to missing data, also the api does not show if a speedlimit is a standard one or one indicated by a signal, and there are way more limitations by the api too