Polonium.4725:

To improve the event API, it would be nice to know the closest Waypoint to the event.

We would need a new API Waypoint_names, that gives the waypoint_id and the name (in the language passed as argument). And we would need a new waypoint_id in the event API that would link to the closest Waypoint.

Events that move (like “escort a NPC”) would return the closest waypoint of their current position if the event is active and the closest one from the beggining if not.

This API could also be used by the suggested Vendor API.

Snowreap.5174:

sounds unlikely. it requires the server to do too much calculation, rather than having it simply report facts that it can look up in a database.

what might be more reasonable, however, would be to add map coordinates for each event, and to also have an API that lists the map coordinates of all the waypoints, portals, points of interest, etc. for each map.

then an application could calculate the distances to each waypoint on its own and show the user the waypoint with the smallest distance. “advanced” applications could even calculate shortest paths that span maps by having you waypoint to an adjacent map then take a portal.

-ken

Lil Puppy.5216:

While it is a very easy calculation, it is something best handled by the client, it is much less intensive to simply send data and that seems to be what Anet is focusing on with the API’s, just the raw data and that is perfect.

vitl.2306:

Yes … this feature would be very very cool.

zwei.9073:

There should be map api returning locations/ids of all map completion items (waypoints, but also hearts, pois)…

And events should return more info (map markers and their locations).

Pairing up this information should be left as exercise by reader :-)