AGL and problem map creation
This is the problem : my takeoff location is the top of a slope and i need to map everything beneath it. Basically, in order to have best photogrammetry results, the lower the better. Thus, i could set the value to a negative one or at most at zero, as the base of the slope de facto will be like 30 meters lower than the takeoff point.
Now this creates a problem with map creation. It seems that this command actually does take into account AGL to make its calculatations. Setting the value to zero gives me a completely blue filled map and setting it to a very small value, like 1 or 4 m, gives me a very dense path taking ages to preview (and even more to execute).
Why doesn't DL seem consistent here?
Practically, in map creation, must i guess or estimate the AGL of my takeoff point, on GE f.ex., and then use this as the maximum height for my DL map?
Comments
5 comments
The map component calculates the GSD using the flight altitude, which in your case is not the altitude above the ground. Until full AGL support is added we could add an option to specify a different altitude for the calculations to use when determining the GSD, but it would be on you to figure out what number to put in.
Ok, and the flight altitude is calculated based on the takeoff location, is that right ?
Is there a way to have DL do its GSD maths taking into account a (manually set) altitude above the mapped area itself (or am i just rephrasing here what you already stated above)?
Yes that was what I meant.
ok, well, that really does sound like something that would certainly facilitate one's workflow, especially in uneven terrain.
Added this to the map component:
Basically put in whatever number you want for GSD calculations. The flight altitude will have no bearing if you fill in this box.
Please sign in to leave a comment.