Skip to main content

Failed: Ground Elevations Not Available

Comments

4 comments

  • Jim McAndrew

    This means that the web-app was not able to cache all the necessary ground elevations during mission planning. Can you share the mission plan that is having the issue? 

    0
  • Scott W

    Unfortunately, I already updated the Plan -- or more specifically, components used in the plan.  There were (2) components with AGL references, so I changed those to use ATL and then updated the plan's linked components.  It worked successfully after that.

    I opened one of the failed "Mission" files (not the plan, but the Mission), chose "Copy", and copied it to a new repository.   Never opened that new plan or updated it, just loaded it in the native app and ran it.  And it worked fine.  No errors.

    So I guess I'll go back and change the component references to AGL again, and see what happens.  If I can eventually reproduce the problem, I'll try to keep the plan/components unchanged until you have a chance to review it.

    0
  • Jim McAndrew

    You should be able to find it in your recent missions list.

    0
  • Scott W

    "Finding" it isn't the problem.  I "found" 3 missions, all of which failed with the "ground elevations not available" error in my list of recent missions.

    But when I "copy" one of those to a new plan, make no changes, and load that new plan into the native client -- the new mission succeeds, without any errors.

    What would explain that?

    0

Please sign in to leave a comment.