Great work Biobob. I've linked this on the Galactic Mapping thread 
Good job as always! I'll update the map for the next release of EDTB.
EDSM stores any system you send to it (using EDSM's own import, or exporting from EDTB or EDDiscovery), coordinates or not. You can view your own flight logs on EDSM much like you can with ED ToolBox.How did I miss this? It's awesome!
I wasn't sure if I should post here or the EDSM thread or the ED Toolbox thread, but I am into the black looking for neutrons atm and am looking for systems that have not been visited. Now I know EDSM only has data from systems that have been reported with coordinates, and ED Toolbox keeps a log of visited systems. Could ED Toolbox submit visited systems to EDSM without coordinates? Without coordinates this couldn't be represented on the map, except maybe areas with the same star name prefix, e.g. "SYNOOKIO" or "PUELIO". So we could see where people are going, and maybe that way choose where to go explore.
Sure it doesn't help the EDSM mapping effort if someone is just blasting through, but it would show where people are going and increase the star inventory, and the occasional coordinate entry would be better than not at all.
Thoughts?
EDSM stores any system you send to it (using EDSM's own import, or exporting from EDTB or EDDiscovery), coordinates or not. You can view your own flight logs on EDSM much like you can with ED ToolBox.
When you export to EDSM using their API, one of the responses is "System not in database". I think this response could be used to determine whether a system has been visited before (by a EDSM user).
I do like these ideas. Something to bring up with the authors of EDSM and ED3D.This is where the integration with ED Toolbox and the ED3D map would shine: log to EDSM at every system, and show a list of commanders that have visited the system (or just a count if too many). Show activity on the map in star regions with the same prefix. That way you can have an idea if you are in an unexplored area.
I do like these ideas. Something to bring up with the authors of EDSM and ED3D.
Loving this map. I found it quite easy to implement on my server. I have my routes plotted as systems now: http://gerdofal.net/ed/1krouting.php
Do you have an example json for plotting as routes instead of just systems? Or maybe just a description of the syntax? I can always just dig through your source, but would like to avoid that if you have an example laying around.
Thanks for an awesome tool!
Lelna
@Gerdofal
I've release an update for routes, I've rebuild completely the part for routes on the JSon file (I was unsatisfied of the old way).
+ I've a add a small JSon sample to show multiples routes on the repo: https://github.com/gbiobob/ED3D-Galaxy-Map/blob/master/json_samples/routes.json
It's not yet fully complete but you can already show a route (or multiple routes) just by define a list of successive systems.
Some improvement are incoming soon
- Add the routes list on the HUD to navigate through each route (if multiple routes),
- add a way to show optional labels on some waypoints of a route,
- then I plan also a way to play an animation to follow a route.
(NB: in the JSon sample you will see some titles & labels fields, not yet used but will be soon)
controls.center.set(moveFrom.mx, moveFrom.my, moveFrom.mz);
Do not work in opera browser, endless load.
Hi Cmdr!
I just test the Neutron Map on Chrome, on my side no problem,
For the map staying empty, have you try to clean your browser cache ?
Also you have to check the console if there is no error message (CTRL+MAJ+I to show the dev tool, go on "Console" tab then reload the page to view if there is some error)
I've check the CSS of the Neutron Highway app and maybe there is a small issues for resize:
the map container has some 'vh' unit sizes, on some iOS device it can cause some issues (are you on iOS ?)
Also I suggest some change on the CSS to make the map more responsive on resize:
#edmapcontainer {
min-height: 400px;
width: 100%;
}
#edmap {
max-width: 100%;
}