Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show waypoint AGL / AMSL altitude on the new style 2D map #1643

Closed
LorenzMeier opened this issue Jun 5, 2015 · 9 comments
Closed

Show waypoint AGL / AMSL altitude on the new style 2D map #1643

LorenzMeier opened this issue Jun 5, 2015 · 9 comments
Assignees

Comments

@LorenzMeier
Copy link
Member

LorenzMeier commented Jun 5, 2015

@dogmaphobic The old map suffers from zero situational awareness when it comes to altitude. It would be awesome if the new map would show the AGL altitude (based on the Google data?).

@acf986
Copy link

acf986 commented Jun 5, 2015

That would be awesome! I am still using the old version. May I ask whether
the offline map is available now?
On 5 Jun 2015 9:01 pm, "Lorenz Meier" notifications@github.com wrote:

@dogmaphobic https://github.com/dogmaphobic The old map suffers from
zero situational awareness when it comes to altitude. It would be awesome
if the new map would show the AGL altitude (based on the Google data?).


Reply to this email directly or view it on GitHub
#1643.

@dogmaphobic
Copy link
Contributor

I have to see how simple it is to get that (AGL altitude). It would be an http request for every position change to get the AGL for that specific coordinate. Let me look into it and see what I can come up with.

As to offline map, not really. The map tiles are cached as you load them but there isn't yet a tool for you to determine an area and ask for it to pre-load the tiles. As is, the caching is all done by the Qt mapping service, which isn't exactly great. It's in my to-do list. Adding our own caching on top of Qt's so I have better control over all this. The upcoming Qt 5.5 has a ton of fixes in this area and I'm waiting for it before putting too much effort in fixing things on this side of the fence.

By the way, all this is based on the new mapping display shown on the main flight view. I'm not doing anything to the old, Mission View.

@dogmaphobic
Copy link
Contributor

Google has an API for this. In theory, you need a key (developer or commercial) and it has a volume limit:

https://developers.google.com/maps/documentation/elevation

Though if you try it with no key whatsoever, it seems to work (no idea for how long though):

https://maps.googleapis.com/maps/api/elevation/json?locations=37.803784,-122.462276

@acf986
Copy link

acf986 commented Jun 6, 2015

But this means you will have to access the internet for the height
information?
On 6 Jun 2015 2:48 am, "Gus Grubba" notifications@github.com wrote:

Google has an API for this. In theory, you need a key (developer or
commercial) and it has a volume limit:

https://developers.google.com/maps/documentation/elevation

Though if you try it with no key whatsoever, it seems to work (no idea for
how long though):

https://maps.googleapis.com/maps/api/elevation/json?locations=37.803784,-122.462276


Reply to this email directly or view it on GitHub
#1643 (comment)
.

@dogmaphobic
Copy link
Contributor

But this means you will have to access the internet for the height
information?

The same as the map tiles. If this information is to be collected, it would also be cached. However, the more I look at it, the less practical I think it will be. For it to make any difference, it would have to have a minimum of a 1m precision. For that to happen, I would need to collect the altitude for every meter the vehicle moves. Real time updates for moving a straight line for 1km == 1,000 requests. Request to cache a 1km x 1km area == 1,000,000 requests. Yes, I could skip some and interpolate but the more that's done, the less accurate it becomes, to the point of being useless if you can't trust it. What we need is a radar altimeter...

@dogmaphobic
Copy link
Contributor

Something like this if you don't mind the 17kg (never mind the cost):

http://www.robotshop.com/en/sri500-precision-3d-laser-scanner.html

:)

@LorenzMeier
Copy link
Member Author

@dogmaphobic We only need the altitude for waypoint positions. So the requests would be much less.

@DonLakeFlyer
Copy link
Contributor

How does Mission Planner get heights do the terrain following thing?

On Jun 7, 2015, at 12:59 PM, Lorenz Meier notifications@github.com wrote:

@dogmaphobic https://github.com/dogmaphobic We only need the altitude for waypoint positions. So the requests would be much less.


Reply to this email directly or view it on GitHub #1643 (comment).

@LorenzMeier
Copy link
Member Author

Closing as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants