How urvan-nomads/ggi works
Project Type and Purpose
• Urban Nomad Server is a full-stack, server-rendered web application built with Spring Boot (Java 17) and Thymeleaf.
File Structure Analysis
• Top-level
• build.gradle, settings.gradle, gradlew scripts → Gradle-based Spring Boot project
• HELP.md, README.md → documentation
• Source (src/main/java)
• urbanNomadServer/UrbanNomadServerApplication.java → application entry point
• config/SecurityConfig.java → security setup
• controller/RouteController.java → REST endpoints (/departure, /waypoint, /done)
• service/RouteService.java → business logic (Tour API calls, Greedy+Haversine route algorithm)
• dto/*.java → data transfer objects for Tour API and geocode responses
• Resources (src/main/resources)
• application.yml/properties → external config (API keys, endpoints)
• static/ → CSS, JS (naver-map.js, travel-data.js, travel-map.js)
• templates/result.html → Thymeleaf template for SSR result page
• Tests
• UrbanNomadServerApplicationTests.java
README Insights
• Architecture: LLM Playground (chat) uses Function Calling/API Connector to invoke backend endpoints.
• External Dependencies:
• KoreanTourAPI (tourapi.service-key)
• Naver Maps API (client_id, secret)
• Wanted LaaS platform
• Business Flow:
1. User enters travel request in chat
2. LLM selects API Connector → calls /departure, /waypoint, /done sequentially
3. Backend fetches data, computes optimal route, generates SSR page
4. User views page in browser; map JS renders on page