`get-direction` expects coordinates at both ends, so the working shape is geocode first, then route — a model that skips the first step gets nothing useful. Guidance comes back as Korean turn-by-turn text, which is right for reading aloud or summarising and wrong for drawing a line on a map.
A small TypeScript server over two Naver Map APIs: one that turns a structured address into coordinates, and one that returns driving guidance between a start and a goal.
- Coordinates for a Korean structured address — `get-geo`
- Turn-by-turn driving guidance between a start and a goal coordinate pair — `get-direction`
Naver Map API credentials — `NAVER_MAP_CLIENT_ID` and `NAVER_MAP_CLIENT_SECRET` — plus `NAVER_MAP_GEO_API_URL` and `NAVER_MAP_DIRECTION_API_URL` for the two endpoints. Node.js 18.x or higher. Build with `npm run build` and point the client at `dist/server.js`. Directions take coordinates, so an address has to be geocoded first. Public-transport routing and lookup by place name are listed as future features, not current ones.