ncloud-maps_skill

Overview

This skill queries Naver Cloud Maps APIs to calculate vehicle routes with smart routing between Directions5 and Directions15. It automatically selects Directions5 for up to four waypoints and switches to Directions15 when five or more waypoints are provided. The skill returns distance, duration, tolls, taxi and fuel estimates, and basic error information.

How this skill works

The skill validates coordinates provided in longitude,latitude format and rejects malformed input. It selects Directions5 or Directions15 based on waypoint count (auto-switch) or an optional override, then requests a vehicle route from Naver Cloud Maps. The response is parsed into distance, duration, toll_fare, taxi_fare, fuel_price and a timestamp; errors are reported when validation, authentication or quota issues occur.

When to use it

• Calculate driving directions and travel time between two or more points
• Estimate tolls, taxi fares, and fuel costs for a planned vehicle trip
• Route optimization workflows that require up to 15 waypoints
• Automated tools that need programmatic, real-time driving routes
• Scenarios where pedestrian or public transit routing is not required

Best practices

• Provide coordinates in longitude,latitude format and validate them before calling the skill
• Keep waypoint counts within API limits: use up to 4 for faster Directions5 calls, 5–15 for Directions15
• Set NCLOUD_API_KEY_ID and NCLOUD_API_KEY as environment variables and confirm the Directions15 API is enabled
• Handle and surface common errors: invalid coordinates, authentication failures, and quota exceeded
• Cache frequent route queries where appropriate to reduce API usage and stay within quota

Example use cases

• Compute a delivery vehicle route with multiple stops and get total distance, duration and fuel estimate
• Preview toll and taxi fare estimates for a planned road trip between cities
• Automatically switch routing API based on waypoint count in a fleet management pipeline
• Integrate vehicle-only navigation into a logistics dashboard that needs real-time traffic-aware results
• Force Directions15 for complex itineraries that require more than five stops