Probably related to
When you inject latitude/longitude coordinates to the Topology View, there is a timing issue where sometimes the calculated coordinates are (0,0) and all devices are displayed at (0,0) (top left corner) of the view. Screenshot shows that x,y and px,py are calculated as (0,0).
I suspect the (0,0) comes from topoModel.js in the function coordFromLangLat due to its return statement assigning (0,0) if the projection of the coordinates is falsy. It is possible that the "projection" in the api isn't initialized at the time it is being called.
See code screenshot. p is undefined at the time the coordinates are being loaded – map data is loaded asyncronously so our projection is not defined at the time this code is being run. Some refactoring will have to be done. A cache might be implemented to save coordinates for later.
|4039,1||ONOS-2109: Fix for (0,0) coords bug - delay opening web socket until we have loaded the map projection.||master||onos||Status: MERGED||+2||+1|
|4096,1||ONOS-2109: Fix for (0,0) coords bug - delay opening web socket until we have loaded the map projection.||onos-1.2||onos||Status: MERGED||+2||0|