nausika

Name: nausika
Author: nausika

Marine, maritime, nautical and sailing data for AI assistants and chatbots.

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

Nausika Marine Forecast: Marine + atmospheric weather forecast for a coordinate (latitude, longitude in decimal degrees) at sea or on a coast. Provides marine variables (waves, swell, currents, SST, s
Nausika Seasonal Forecast: Seasonal weather outlook for a coordinate (latitude, longitude in decimal degrees), sourced from ECMWF SEAS5 (1–7 month horizon) via Open-Meteo. USE CASE: planning a sailing
Nausika Tides: Get tide predictions or discover tide stations near any location. By default, finds the nearest station and returns tide predictions. Use stations_only: true to discover nearby stations

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Marine, maritime, nautical and sailing data for AI assistants and chatbots. Mediterranean marine forecast: wind, wave, swell, gust. Tide tables and tidal predictions. Sea routing and passage planning on a coastline-aware maritime graph. Curated POIs: marinas, ports, harbors, anchorages, moorings, fuel. Real data, cited sources, never invented.

Список инструментов сервера (19)

Технические названия из tools/list. Нужны только разработчикам.

nausika_marine_forecast	Marine + atmospheric weather forecast for a coordinate (latitude, longitude in decimal degrees) at sea or on a coast. Provides marine variables (waves, swell, currents, SST, sea level) together with atmospheric variables (wind, gusts, pressure, weather code, visibility, precipitation, temperature, UV, sunrise/sunset). All directions are reported FROM in degrees and 16-sector compass labels in the text content. PRESETS (default = tactical): - now: current snapshot only. - today: 24h hourly_1 + daily. - tactical: 3-day hourly_3 + daily. - planning: 8-day daily. - extended: 14-day daily. Marine variables truncate to 8 days; days beyond are returned as null on marine fields with a "marine coverage ends" marker in the text. - none: same shape as tactical (3 days, hourly_3 + daily) but with NO core variables seeded — caller MUST supply a non-empty variables[] list (the call fails otherwise). Use when you want exactly N variables and nothing else. Window overrides (most-specific wins): start_hour/end_hour > start_date/end_date > forecast_hours > forecast_days. Sub-day windows (forecast_hours, start_hour/end_hour) automatically drop the daily summary — a 24-hour aggregate doesn't represent a sub-day slice. start_hour/end_hour additionally defaults temporal_resolution to hourly_1 so bucket labels (e.g. "08:00") match the requested timestamps exactly; pass temporal_resolution explicitly to override. Variables (additive to preset core): see schema for the full list — covers waves/swell/wind-wave components, ocean currents (FROM-corrected), SST, sea level / inverse-barometer height, wind/gusts/pressure, weather_code, visibility, cape, precipitation (sum + rain/showers), cloud layers, temperature, apparent temperature, dew_point, RH, UV index, daylight + sunshine duration. Every variable that is selected renders in the text output (singletons included), and structured arrays carry the raw data. Coverage and graceful degradation: Nausika is centered on the Mediterranean basin; the underlying global atmospheric and marine endpoints still answer worldwide. Best marine-variable coverage is in well-modeled seas (Mediterranean, North Sea, Atlantic shelves). If marine forecast has no coverage (lake, inland) or the nearest sea cell is too far from the requested point, the response carries marine_unavailable_reason and the atmospheric block. The same applies in reverse for atmospheric outages.
nausika_seasonal_forecast	Seasonal weather outlook for a coordinate (latitude, longitude in decimal degrees), sourced from ECMWF SEAS5 (1–7 month horizon) via Open-Meteo. USE CASE: planning a sailing trip 1–7 months ahead — "what does August in Sardegna typically look like?" Returns ENSEMBLE-MEAN absolute values (NOT anomalies). For deterministic short-term (≤16 days) use nausika_marine_forecast instead. GRANULARITY: response carries both DAILY arrays (one entry per day in the requested range) and MONTHLY arrays (one entry per calendar month touched by the range). Daily values are noisier at long horizons; monthly aggregates are statistically more reliable. CORE VARIABLES (always seeded): wind_speed_10m, wind_direction_10m (daily-only — SEAS5 has NO monthly direction), sea_surface_temperature, temperature_2m, precipitation, cloud_cover. Add more via variables[]: pressure_msl, surface_pressure, sunshine_duration, shortwave_radiation, apparent_temperature, dew_point_2m, relative_humidity_2m, weather_code (daily-only), sunrise_sunset (daily-only), snowfall, snow_depth. CONSTRAINTS: start_date must be today or future (UTC); end_date ≤ today + 210 days; range ≤ 215 days. SEAS5 has NO wave data — for waves at any horizon use nausika_marine_forecast (≤8 days marine). LIMITS: 36 km grid resolution, NOT bias-corrected, area forecast only. coordinates_resolved.distance_km exposes the snap distance (commonly 10–25 km for coastal points). Surface the disclaimer in client-facing text.
nausika_tides	Get tide predictions or discover tide stations near any location. By default, finds the nearest station and returns tide predictions. Use stations_only: true to discover nearby stations without fetching predictions. Coverage: official tide stations cover US coasts and territories. Outside that area the tool falls back to a global modeled-tide source. Examples: - "Tides near San Francisco" -> latitude=37.77, longitude=-122.42 -> finds nearest station, returns predictions - "What tide stations are near Miami?" -> latitude=25.76, longitude=-80.19, stations_only=true Tip: use nausika_geocode to convert place names to coordinates. Check nausika_marine_forecast for full sea conditions.
nausika_search_places	Search for nautical places and points of interest by proximity. Supports text search, type/category filters, and promoted attribute filters (shelter, bottom type, coverage score). Coverage: the curated Nausika dataset focuses on the Mediterranean basin. Searches outside the Mediterranean typically return zero or sparse results until coverage is expanded upstream. Returns places with name, type, category, coordinates, distance, ratings, and relevant attributes including i18n names/descriptions, wiki image URLs, and OSM/Wikidata links. Authenticated users also get personalization (favorites, own rating). Place types: marina, port, bay, fuel_station, yacht_club, city, island, cape, gulf, lighthouse. Examples: - Nearby marinas: latitude=44.3, longitude=9.21, types=["marina"] - Text search near location: latitude=40.84, longitude=14.27, query="marina napoli" - Sheltered bays: latitude=44.3, longitude=9.21, type="bay", shelter_from="NW" - Italian display names: latitude=44.4, longitude=8.93, names_lang="it" For single-place lookup by id (with raw OSM tags), use nausika_get_place(id). Tip: use nausika_sea_route to calculate distance to results.
nausika_get_place	Fetch full detail for a single place by ID. Returns canonical attributes (name/coords/category/type), localized i18n names+descriptions, wiki image URLs, ratings aggregates, plus extras only this tool provides: the raw OpenStreetMap tags of the primary OSM feature, and direct links to OSM, Wikidata, and Wikipedia. Use this after nausika_search_places returns a result you want to drill into. For proximity / text search, use nausika_search_places.
nausika_sea_route	Calculate the maritime route between two points, avoiding land. Routes have enhanced precision near Nausika places (marinas, anchorages, etc.). Coverage: routing graph is centered on the Mediterranean basin and adjacent waters. Outside that area the tool returns an explicit error rather than a misleading partial result. Returns: Distance, estimated duration, and waypoint count. Full GeoJSON route available in structured output. Use include_waypoints: false for quick distance/duration without route details. Examples: - "Route from Genova to Bastia" -> origin_lat=44.4, origin_lon=8.93, dest_lat=42.7, dest_lon=9.45 - "Distance Naples to Palermo" -> origin_lat=40.84, origin_lon=14.27, dest_lat=38.12, dest_lon=13.36, include_waypoints=false Tip: use nausika_geocode to resolve place names. Use nausika_calculator for fuel/time estimates from the returned distance.
nausika_calculator	Evaluate a math expression and return the numeric result. Useful for fuel consumption, range/autonomy estimates, unit conversions, and any ad-hoc arithmetic the user needs. Supported (exhaustive): +, -, , /, ^, %, parentheses, sqrt(), abs(), ceil(), floor(), round(), sin(), cos(), tan(), log(), exp(), min(), max(), PI, E. Anything else (atan2, pow, log10, hypot, if, comparisons, factorial, …) is rejected. Examples: - "How much fuel for 120 nm at 8.5 L/h and 6 kn?" -> expression: "(120 / 6) 8.5" - "Convert 45 nm to km" -> expression: "45 * 1.852" Tip: combine with nausika_sea_route distance and nausika_get_boat_profile fuel rate for consumption estimates.
nausika_geocode	Resolve place names to coordinates or find places near coordinates. Two modes: - Forward: provide 'query' to search by place name. Searches the curated marine database first; if no confident match, falls back to a global place-name source. - Reverse: provide 'latitude' + 'longitude' to find nearest curated places. Coverage: the curated database is Mediterranean-focused (marine POIs). The global fallback covers forward queries outside the Mediterranean. Reverse geocoding returns empty results outside the Mediterranean basin. Each forward result includes a 'source' field: "local" (curated marine database) or "osm" (OpenStreetMap fallback). Returns: Matching places with name, type, category, coordinates, plus similarity (forward, local) or distance (reverse). Examples: - query: "Portofino" -> matches with coordinates and similarity - query: "Lisbon" -> falls back to the global source - latitude: 44.3, longitude: 9.21 -> nearest places with distance Tip: use coordinates from results with nausika_marine_forecast, nausika_tides, nausika_search_places, or nausika_sea_route.
nausika_describe_place_schema	Returns the expected attributes and their types for a given place type. Useful to understand what fields are available on places of a given type.
nausika_is_water	Check whether a coordinate (latitude, longitude in decimal degrees) is on water or land, and how far it is from the coast. Returns: - is_water: boolean (true if over sea, false if over land) - distance_to_coast_m: meters to the nearest coastline boundary; meaningful on either side (sea → distance to shore, inland → distance to sea, e.g. Rome ≈ 25 km). - source: detection source Useful to verify waypoints in route planning, or to gauge how coastal/inland a point is.
nausika_convert_coordinates	Convert coordinates between decimal degrees, degrees-minutes-seconds (DMS), and degrees-decimal minutes (DM). Accepts any mix of formats as input and returns all three representations. Input formats: - Decimal: 41.0289 or "41.0289" - DMS: "41°01′44.04″N" or "41°01'44.04\"N" - DM: "41°01.7340′N" or "41°01.7340'N" Examples: - Decimal to DMS: latitude=41.0289, longitude=9.545 → 41°01′44.04″N, 009°32′42.00″E - DMS to decimal: latitude="41°01′44.04″N", longitude="009°32′42.00″E" → 41.0289, 9.545 - DM to decimal: latitude="41°01.1'N", longitude="009°32.7'E" → 41.01833, 9.545 Tip: use this to verify coordinates from nautical charts before route planning or place lookup.
nausika_manage_boat_profile	Create, update, delete, or set default boat profile. Multiple boats per account, identified by name. Examples: - Create: action="upsert", name="Freya", type="sail", loa_m=12.5, draft_m=1.8 - Update draft: action="upsert", name="Freya", draft_m=2.0 - Delete: action="delete", name="Freya" - Set default: action="set_default", name="Freya" Tip: saved boat parameters (speed, consumption) enrich nausika_sea_route duration estimates.
nausika_get_boat_profile	Get your saved boat profile(s). Omit name for the default boat, or use name="*" to list all boats. Tip: use boat speed/consumption with nausika_sea_route and nausika_calculator for trip planning.
nausika_manage_favorite	Add or remove a place from your favorites list. Examples: - Add: action="add", place_id="<uuid>", note="Great anchorage for overnight" - Remove: action="remove", place_id="<uuid>" Tip: find places first with nausika_search_places, then bookmark by place_id.
nausika_get_favorites	List your favorite places with details and personal notes. Ordered by most recently added. Tip: use place coordinates with nausika_sea_route or nausika_marine_forecast for trip planning.
nausika_manage_rating	Rate a place (1-5 stars) with an optional private comment. One rating per user per place. Examples: - Rate: action="upsert", place_id="<uuid>", score=4, comment="Clean facilities" - Delete: action="delete", place_id="<uuid>" Tip: find places first with nausika_search_places, then rate by place_id.
nausika_get_ratings	View ratings for a place (aggregate + your own) or list all your ratings. Examples: - Place ratings: place_id="<uuid>" - My ratings: my_only=true Tip: ratings are visible in nausika_search_places results to help other sailors.
nausika_manage_route	Save a route or compose a multi-day itinerary. A route has one or more legs, each optionally linked to places. Typical flow: calculate legs with nausika_sea_route, then save results here. Examples: - Save single route: action="upsert", name="Genova to Bastia", route_type="single", legs=[{...}] - Create itinerary: action="upsert", name="Corsica Trip", route_type="itinerary", legs=[{leg_order:1,...}, {leg_order:2,...}] - Delete: action="delete", id="<route-uuid>" Tip: calculate legs with nausika_sea_route first, then save the route here.
nausika_get_routes	List and search your saved routes and itineraries. Examples: - List all: (no params) - Single route detail: id="<route-uuid>" - Only itineraries: route_type="itinerary" Tip: use leg coordinates with nausika_marine_forecast or nausika_tides to check conditions along the route.