/geodata/getnearest - Find nearest resorts

Overview

The /geodata/getnearest endpoint finds ski resorts nearest to a given geographical location using latitude and longitude coordinates.

Purpose

• Find resorts near a specific location
• Search within a customizable distance radius
• Get distance-sorted results
• Support location-based resort discovery
• Enable "resorts near me" functionality

Endpoint

GET /geodata/getnearest

Parameters

Query parameters

lat (float, required)

Latitude coordinate of the search origin point.

Range: -90 to 90 (decimal degrees)

Examples:

• lat=59.9139 - Oslo, Norway
• lat=61.3150 - Trysil area
• lat=60.4720 - Bergen area

---

lon (float, required)

Longitude coordinate of the search origin point.

Range: -180 to 180 (decimal degrees)

Examples:

• lon=10.7522 - Oslo, Norway
• lon=12.2680 - Trysil area
• lon=5.3340 - Bergen area

---

distance (integer, optional, default: 50)

Maximum search radius in kilometers from the origin point.

Default: 50 km Range: Any positive integer (practical range: 1-1000)

Examples:

• distance=10 - Find resorts within 10 km
• distance=100 - Find resorts within 100 km
• distance=500 - Find resorts within 500 km

Note: Results are limited to a maximum of 50 resorts, ordered by distance (closest first).

---

sourceFields (string, optional)

Return only specific fields from each resort's _source object using dot notation (comma-separated).

Purpose: Optimize response payload size by requesting only needed fields

Examples:

• sourceFields=name,location
• sourceFields=name,resort_open,lifts,slopes
• sourceFields=name,location.lat,location.lon,conditions.combined.top.snow.depth_terrain

---

Response format

Success response structure

{
  "took": 1,
  "timed_out": false,
  "hits": {
    "total": 8,
    "max_score": null,
    "hits": [
      {
        "_index": "fnugg_resort",
        "_type": "resort",
        "_id": "89",
        "_version": 1,
        "found": true,
        "_source": {
          "id": 89,
          "name": "Oslo Vinterpark",
          "description": "Oslo Vinterpark ligger bare 30 minutter fra Oslo sentrum...",
          "location": {
            "lat": 59.9700,
            "lon": 10.6700
          },
          "resort_open": true,
          "lifts": {
            "total": 11,
            "open": 9
          },
          "slopes": {
            "total": 18,
            "open": 16
          },
          "conditions": {
            "combined": {
              "top": {
                "snow": {
                  "depth": 85
                }
              }
            }
          }
          // ... more fields (see /get/resort/{id} documentation)
        },
        "sort": [12500.0]
      },
      {
        "_index": "fnugg_resort",
        "_type": "resort",
        "_id": "73",
        "_version": 1,
        "found": true,
        "_source": {
          "id": 73,
          "name": "Norefjell",
          "location": {
            "lat": 60.1800,
            "lon": 9.5500
          },
          "resort_open": true
          // ... more fields
        },
        "sort": [45300.0]
      }
      // ... more results
    ]
  }
}

Error response (missing parameters)

{
  "error": "Missing required parameters: lat and lon"
}

---

Response fields

Top level fields

• took (integer): Request processing time in milliseconds (always 1 for compatibility)
• timed_out (boolean): Whether request timed out (always false)
• hits (object): Results container
  • total (integer): Number of resorts found within the radius
  • max_score (null): Always null (not used for geo queries)
  • hits (array): Array of resort result objects

Individual Result Fields

Each resort in hits.hits contains:

• _index (string): Index name, always "fnugg_resort"
• _type (string): Type name, always "resort"
• _id (string): Resort's site_id as string
• _version (integer): Document version, always 1
• found (boolean): Whether resort was found, always true
• _source (object): Complete resort data (same structure as /get/resort/{id})
• sort (array): Array with single element: distance in meters (float)

---

Example requests

Find resorts near Oslo

GET /geodata/getnearest?lat=59.9139&lon=10.7522&distance=50

Finds all resorts within 50 km of Oslo city center.

---

Find very close resorts

GET /geodata/getnearest?lat=60.4720&lon=5.3340&distance=10

Finds resorts within 10 km of Bergen.

---

Find resorts with specific fields only

GET /geodata/getnearest?lat=61.3150&lon=12.2680&distance=100&sourceFields=name,location,resort_open,lifts.open,slopes.open

Finds resorts within 100 km, returning only name, location, status, and facility counts.

---

Wide area search

GET /geodata/getnearest?lat=59.9139&lon=10.7522&distance=200

Finds resorts within 200 km (large search radius for broader discovery).

---

Use cases

1. "Resorts near me": Use device geolocation to find nearby resorts
2. Map-based search: Display resorts on a map around a clicked location
3. Regional exploration: Find all resorts in a region by searching from a central point
4. Trip planning: Find resorts within driving distance from a city
5. Mobile apps: Provide location-based resort recommendations
6. Distance-based filtering: Combine with other filters (e.g., only open resorts nearby)

---

Notes

• Both lat and lon parameters are required; omitting either returns an error
• Results are automatically sorted by distance (closest first)
• The sort array in each result contains the calculated distance in meters (not kilometers)
• Maximum 50 results are returned, even if more resorts exist within the radius
• Default search radius is 50 km if distance parameter is omitted
• The response uses the same resort structure as /get/resort/{id} (see that documentation for complete field descriptions)
• Use sourceFields to reduce payload size, especially when displaying many resorts on a map
• Distance calculation considers Earth as a sphere (not a perfect sphere/ellipsoid)
• Coordinates should use decimal degrees format (not degrees/minutes/seconds)
• The endpoint automatically loads related models (resortTypes, regions) for each resort
• Distance is calculated "as the crow flies" (straight-line distance), not driving distance
• For driving distances, use the /geodata/getdistance endpoint instead
• Empty results (no resorts within radius) returns hits.total: 0 with empty hits.hits array