Why don't custom waypoints have correct altitude?

POI’s, runways, airports etc all have correct altitude set in the location
object in world locationinfos, but custom waypoints altitude are fixed at
1640ft or 500m everywhere.

I’m on SU12 beta, but I think this is also the case in live.

This is problematic later on when trying to use the custom waypoints as the
altitude is incorrect. It would be much better if custom waypoint altitudes
were consistent with all the other info element altitudes. Can we get that
changed, or is there some special reason it’s like that?

Thanks!

See the data dumps below of a custom waypoint on a lake next to a POI.

The poi is not ~600ft higher than the lake, it’s level right beside it. In any
event, just click all over the map anywhere creating custom waypoints and
you’ll see the altitude is always 500m/1640ft, which makes it difficult to
use.

[Log] GenericWorldLocationInfoElement.setData: (LocationInfos.js, line 347)

[Log] Object (LocationInfos.js, line 348)

Example 1 __Type: “WorldLocationWaypoint”

__Type: “WorldLocationWaypoint”

altitude: {__Type: “DataValue”, ID: 0, icon: “”, name: “”, valueStr: “1640”,
…}

icao: “”

icon: “/Icons/Waypoints/WORLDMAP/ICON_MAP_FREELOCATION.svg”

image: “/Textures/Locations/GENERIC_CUSTOM.jpg”

latDMS: “47° 32’ 50.25" N”

lla: {__Type: “LatLongAlt”, lat: 47.54729080200195, long: 12.975679397583008,
alt: 500}

longDMS: “12° 58’ 32.45" E”

name: “Custom”

type: “navaid”

waypointInfos: Object

__Type: “WaypointInfos”

frequency: {__Type: “DataValue”, ID: 0, icon: “”, name:
“TT:MENU.WAYPOINT_FREQUENCY”, valueStr: “”, …}

tacanChannel: “”

waypointType: “TT:MENU.LOCATIONTYPE_WAYPOINT_CUSTOM”

Object Prototype

weather: {__Type: “WeatherData”, index: -1, locked: false, name: "fec 3’8 21c

  • Large Loose Assemblages", category: “”, …}

wlType: 8

Example 2 __Type: “WorldLocationPOI”

[Log] GenericWorldLocationInfoElement.setData: (LocationInfos.js, line 347)

[Log] Object (LocationInfos.js, line 348)

__Type: “WorldLocationPOI”

altitude: {__Type: “DataValue”, ID: 0, icon: “”, name: “”, valueStr: “2215”,
…}

icon: “/Icons/Waypoints/WORLDMAP/ICON_MAP_LANDMARK.svg”

image: “/Textures/Locations/GENERIC_POI.jpg”

latDMS: “47° 32’ 41.08" N”

lla: {__Type: “LatLongAlt”, lat: 47.54474379122257, long: 12.972026467323303,
alt: 675.1640014648438}

longDMS: “12° 58’ 19.30" E”

name: “St. Bartholomew’s Church”

poiInfos: {__Type: “POIInfos”, POIType: “Point of Interest”, creator: “”}

type: “point of interest”

weather: {__Type: “WeatherData”, index: -1, locked: false, name: "fec 3’8 21c

  • Large Loose Assemblages", category: “”, …}

wlType: 4


I’ve worked around this (kind of, with a neat physics hack) but I could make a
much nicer UX if I had access to the actual height of a custom waypoint that
was 100% reliable. I’ve tried every method known trying to get the ground
altitude when doing a teleport (apart from calling an external API which I
don’t want to do, bc it seems silly when the sim has all the info) but none of
them reliably return it due to the highly variable nature of a teleport due no
control over the distance a use might choose to do one = highly variable
loading issues as the new location streams in.

Hello @sonicviz This altitude value is hard coded because waypoints in general
have no altitude, the POI altitude is right because it has been set by hand.
It is made like this by design and won’t be changed. Best regards, Yohan

Thanks for the info.