search

fgx / fgx.github.io

The FGx public web presence on GitHub
http://fgx.github.io
Other
2 stars 3 forks source link

2016-07-21 ~ LEIG FlightPath R1 ~ Many errors #33

Closed theo-armour closed 8 years ago

theo-armour commented 8 years ago

image

@fgx/owners

LEIG FlightPath

2016-07-21 ~ R1

geoffmcl commented 8 years ago

@theo-armour - many errors... well yeah...

The lon and alt look fine, and again the lat seems off...

And of course there is the inverted model orientation...

But otherwise, quite reasonable for a first - with model - commit...

It seems some adjustment needed for the new flightpath and model .js?

Who, how, were these generated?

But YEAH, we have a model flying the track... great... thanks...

Still reading the next six plus messages...

Regards, Geoff.

pedromorgan commented 8 years ago

Geoff can I make a suggestion we shut down fgx.goups google etc..

As @theo pointed out its in GH atmo.. and move that way..

Am behinh @theo cos i dont want @theo to be punched in the face like some forum members do.. Instead be critical and an credability of.. right.. this is reall cool ;-)))

On 22 July 2016 at 01:00, Geoff McLane notifications@github.com wrote:

@theo-armour https://github.com/theo-armour - many errors... well yeah...

The lon and alt look fine, and again the lat seems off...

And of course there is the inverted model orientation...

But otherwise, quite reasonable for a first - with model - commit...

It seems some adjustment needed for the new flightpath and model .js?

Who, how, were these generated?

But YEAH, we have a model flying the track... great... thanks...

Still reading the next six plus messages...

Regards, Geoff.

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/fgx/fgx.github.io/issues/33#issuecomment-234419401, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHkHDGqcgYKTwg42CB1xcNBIUxN1tPNks5qYAgSgaJpZM4JSTs0 .

theo-armour commented 8 years ago

I don't think the FGx Google Group actually needs to be 'shut down'. It can just sit there.

But I do think that GitHub issues are the way to go forward - if nothing else because they are so much closer to the code.