{"action":"created","issue":{"url":"https://api.github.com/repos/fgx/fgx.github.io/issues/23","repository_url":"https://api.github.com/repos/fgx/fgx.github.io","labels_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/23/comments","events_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/23/events","html_url":"https://github.com/fgx/fgx.github.io/issues/23","id":160991993,"number":23,"title":"Adding a new FlightPath","user":{"login":"geoffmcl","id":1333435,"avatar_url":"https://avatars.githubusercontent.com/u/1333435?v=3","gravatar_id":"","url":"https://api.github.com/users/geoffmcl","html_url":"https://github.com/geoffmcl","followers_url":"https://api.github.com/users/geoffmcl/followers","following_url":"https://api.github.com/users/geoffmcl/following{/other_user}","gists_url":"https://api.github.com/users/geoffmcl/gists{/gist_id}","starred_url":"https://api.github.com/users/geoffmcl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geoffmcl/subscriptions","organizations_url":"https://api.github.com/users/geoffmcl/orgs","repos_url":"https://api.github.com/users/geoffmcl/repos","events_url":"https://api.github.com/users/geoffmcl/events{/privacy}","received_events_url":"https://api.github.com/users/geoffmcl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-06-17T23:21:30Z","updated_at":"2016-06-30T23:53:42Z","closed_at":null,"body":"# New Flightpaths\r\n\r\nThis addresses #22, a little...\r\n\r\nThis is a **great** demonstration of rendering a flight track in 3D... thank you Theo... it is beautiful...\r\n\r\nI now have two more interesting `flightpaths` to add, VNLK and VHSK, and only ask what files you need added to do this...\r\n\r\nAt this point I have recorded the FGFS flights in csv, which has many, many values, but 3 of which can be easily extracted - namely lat, lon, alt - which can be presented in any form possible... What do you need? What is the best?\r\n\r\nOne of the many values included is the exact model orientation... roll, pitch, ... at present this seems `calculate` for track turns, descending, ascending... but these model values **are** included in the raw recorded csv file... not yet used...\r\n\r\nIn examining the last [FGx FlightPath R13](http://fgx.github.io/sandbox/flightpath/fgx-flightpath-r13.html), it is near **perfect**... really thanks... it is like a real time video of a **sim** flight... that is the aim...\r\n\r\nSo I guess I seek the API to add other flights... some simple menu selection... to switch flightpath viewed...\r\n\r\nMinor Feature Requests:\r\n\r\n 1. The model be at least 75% smaller... the wing of the model must **not** cut through moutains it flies near...\r\n 2. Auto-rotate defaults OFF. There is enough visual stimulus, without adding more...\r\n \r\nBut even without those `requests`, what should I upload to add these two new exciting, mountainous, `FlightPaths`?\r\n"},"comment":{"url":"https://api.github.com/repos/fgx/fgx.github.io/issues/comments/229820480","html_url":"https://github.com/fgx/fgx.github.io/issues/23#issuecomment-229820480","issue_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/23","id":229820480,"user":{"login":"geoffmcl","id":1333435,"avatar_url":"https://avatars.githubusercontent.com/u/1333435?v=3","gravatar_id":"","url":"https://api.github.com/users/geoffmcl","html_url":"https://github.com/geoffmcl","followers_url":"https://api.github.com/users/geoffmcl/followers","following_url":"https://api.github.com/users/geoffmcl/following{/other_user}","gists_url":"https://api.github.com/users/geoffmcl/gists{/gist_id}","starred_url":"https://api.github.com/users/geoffmcl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geoffmcl/subscriptions","organizations_url":"https://api.github.com/users/geoffmcl/orgs","repos_url":"https://api.github.com/users/geoffmcl/repos","events_url":"https://api.github.com/users/geoffmcl/events{/privacy}","received_events_url":"https://api.github.com/users/geoffmcl/received_events","type":"User","site_admin":false},"created_at":"2016-06-30T23:53:42Z","updated_at":"2016-06-30T23:53:42Z","body":"@theo-armour well I, for sure. do **not** know the full answer...\r\n\r\nBut we are trying to display, in 3D, a single `FightPath`... a track we know, after loading, the full limits...\r\n\r\nThe map, or maps, background, become a little irrelevant, but **very** important... added reality to the scene... added information, ... so somehow, it seems the bounding box of the `FlightPath` is the only relevant object... that is what we are trying to display... \r\n\r\nSo yes, we can zoom in, or out, and rotate the scene, but by default, the current 'FlightPath' box should default to **center** stage...\r\n\r\nSo in a way, that flights bounding box, plus perhaps a 10-20% smudge factor, should be where we start the view...and that `smudge` factor is also important... always begin with slightly more...\r\n\r\nBut I can understand, maybe we should focus on the map, **or** maps, that this particular `FlightPlan` traverses... but given that the set of slippy maps, pngs, needed to cover this specific `FligthPlan`, will always be larger, especially if we include **all** tiles covered at this zoom, then it means we are showing **more** than the specific `track`...\r\n\r\nLike I say, really do not know the answer, but somehow I would concentrate the default view to the `FlightPaths` bounding object, plus some smudge factor... if that makes sense...\r\n"}}
{"actor":{"display_login":"geoffmcl"}}