20,741
edits
Canvas development: Difference between revisions
→Adding new Projections
| Line 2,151: | Line 2,151: | ||
=== Adding new Projections === | === Adding new Projections === | ||
{{Note|Discuss base class that needs to be implemented}} | {{Note|Discuss base class that needs to be implemented}} | ||
[[File:Map_north_pole_route.jpg|thumb|We've already fixed that in the (old) map dialog, by using an aimuthal equidistant projection. Porting the projection to Canvas is on the todo list. Such a projection is much much better for navigational use. | |||
Curves in routes are not calculated by Canvas, nor by the ND though. It's the route manager that splits up a route in segments in order to get smooth transitions.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=227838&sid=91acc3b270c5520b6cc03b34d1b8d011#p227838 | |||
|title = <nowiki> Re: Canvas ND performance issues with route-manager </nowiki> | |||
|author = <nowiki> Gijs </nowiki> | |||
|date = Dec 23rd, 2014 | |||
|added = Dec 23rd, 2014 | |||
|script_version = 0.36 | |||
}}</ref> | |||
]] | |||
that's a coordinate singularity of a (lat/lon) grid and things like your course cease to be well-defined in the vicinity - so you can't expect normal code to work. Usually you need special provisions to deal with such singularities (from my own experience, the Shuttle has four different coordinate systems to switch, and fallback rules what to display when close to a singularity and the AP for liftoff uses a different coordinate grid (based on vectors rather than angles) from the AP later during launch because the launch is done right into the singularity (there's no course defined for vertical ascent) and so one can't steer to any particular course until later). <ref>{{cite web | that's a coordinate singularity of a (lat/lon) grid and things like your course cease to be well-defined in the vicinity - so you can't expect normal code to work. Usually you need special provisions to deal with such singularities (from my own experience, the Shuttle has four different coordinate systems to switch, and fallback rules what to display when close to a singularity and the AP for liftoff uses a different coordinate grid (based on vectors rather than angles) from the AP later during launch because the launch is done right into the singularity (there's no course defined for vertical ascent) and so one can't steer to any particular course until later). <ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/36184377/ | |url = https://sourceforge.net/p/flightgear/mailman/message/36184377/ | ||