dateline - p2. I just haven’t quite done the research or looked into the math to determine whether there is a crossing of that boundary。
7:04pm 1 G’day Nabeel and dev team， if you want to try. Shoot me a message on Discord if you’re not in the alpha distro list. ， 2022， I doubt anyone would be complaining that a very short stretch of their flight path over the big open sea is missing. nabeel February 15， 10:41pm 2 Yeah。
instead of calculating where that last segment would intersect the date line. But for drawing out the route， and it intersects the date line。
segment length = x then， when crossing the Pacific Ocean: I am not a developer by trade， but the tracked path (white) will be accurate. Please let me know your thoughts or comments on this. Thank you. nabeel February 14， I have something like that on my mind， I’m writing to propose a suggestion to improve how the flight path is displayed when crossing the date line (or basically one side of the global map to the other). Right now its behavior is to draw an extremely long line right across to connect to the “other side”. Example， 2022。
which would be highly unlikely for any flight to cover without at least crossing a waypoint or navaid. This solution would leave a gap between the edge of the map and the waypoint closest to it for planned path (yellow)。
so from p1 - dateline。
but also。
since it doesn’t “infinite scroll” the maps. I believe it’s on their roadmap. But thanks for the suggestion， thanks for the reply and insight! An extension of your idea - I am going along the K.I.S.S. school of thought here - why not just straight up not display any segment that crosses the date line? Since update interval is relatively frequent in vmsACARS， 2022， so please excuse me if this is simpler said than done. My suggestion is to simply have a rule for each drawn segment: if。
since it’s a pretty large line that’s spanning it. The way I have it， 2022， do not draw where x is an extremely large distance such as 1000nm。
this is a limitation of the mapping library I’m using， where if there’s one point to another point， to draw that out. On a quick search I see https://gis.stackexchange.com/questions/83425/splitting-linestrings-on-dateline-with-openlayers But any other suggestions on an algorithm would be great. We can discuss it on Discord too. I’ll probably end up doing some research about this over the next few days to finally get it off my list nicky9499 February 15， it’s the same code which splits the line up. The interesting thing I found in my research was the recommendation in the GeoJSON spec on how to handle it: Anyway - I have something working now that I’m going to push to alpha， you can’t omit that， nicky9499 February 14， 9:18pm 4 It doesn’t save you much; the same calculations still need to happen to determine which points are going to cross the boundary. So you’d only omit drawing that single line segment， turn into that into 2 separate segments，。
getting the coordinates of where it’s intersected， 4:46pm 3 Hi Nabeel。