ODIN

Coordinates: 68.41539, 15.839. The default view is concise. Select one data category to avoid unnecessarily large responses.

Search scope: ODIN is a named place within LØDINGEN municipality; municipality-filtered results cover the whole municipality.

Addresses and place names

Source: Geonorge.

total_count:
41
addresses:

5 results

  1. address:
    Erikstadvegen 100
    postnummer:
    8410
    poststed:
    LØDINGEN
    kommunenummer:
    1851
    kommunenavn:
    LØDINGEN
    lat:
    68.4149977
    lon:
    15.8388092
    epsg:
    EPSG:4326
    distance_km:
    0.044
  2. address:
    Erikstadvegen 80
    postnummer:
    8410
    poststed:
    LØDINGEN
    kommunenummer:
    1851
    kommunenavn:
    LØDINGEN
    lat:
    68.4159227
    lon:
    15.8376007
    epsg:
    EPSG:4326
    distance_km:
    0.082
  3. address:
    Erikstadvegen 78
    postnummer:
    8410
    poststed:
    LØDINGEN
    kommunenummer:
    1851
    kommunenavn:
    LØDINGEN
    lat:
    68.4162374
    lon:
    15.8378519
    epsg:
    EPSG:4326
    distance_km:
    0.105
  4. address:
    Erikstadvegen 84
    postnummer:
    8410
    poststed:
    LØDINGEN
    kommunenummer:
    1851
    kommunenavn:
    LØDINGEN
    lat:
    68.4156403
    lon:
    15.8363634
    epsg:
    EPSG:4326
    distance_km:
    0.111
  5. address:
    Erikstadvegen 82
    postnummer:
    8410
    poststed:
    LØDINGEN
    kommunenummer:
    1851
    kommunenavn:
    LØDINGEN
    lat:
    68.4159126
    lon:
    15.836276
    epsg:
    EPSG:4326
    distance_km:
    0.126
total_count:
51
places:

8 results

  1. names:

    1 results

    1. name:
      Erikstadvegen
      language:
      Norsk
      status:
      hovednavn
    type:
    Adressenavn
    status:
    aktiv
    distance_km:
    0.08
    lat:
    68.41026
    lon:
    15.83462
    stedsnummer:
    1026801
  2. names:

    2 results

    1. name:
      Erikstad
      language:
      Norsk
      status:
      hovednavn
    2. name:
      Erstták
      language:
      Nordsamisk
      status:
      hovednavn
    type:
    Bygdelag (bygd)
    status:
    aktiv
    distance_km:
    0.252
    lat:
    68.41404
    lon:
    15.83406
    stedsnummer:
    17322
  3. names:

    1 results

    1. name:
      Langskjeret
      language:
      Norsk
      status:
      hovednavn
    type:
    Skjær i sjø
    status:
    aktiv
    distance_km:
    0.284
    lat:
    68.41303
    lon:
    15.84163
    stedsnummer:
    40698
  4. names:

    1 results

    1. name:
      Bakken
      language:
      Norsk
      status:
      hovednavn
    type:
    Bruk
    status:
    aktiv
    distance_km:
    0.312
    lat:
    68.41379
    lon:
    15.83275
    stedsnummer:
    1081896
  5. names:

    2 results

    1. name:
      Erikstad
      language:
      Norsk
      status:
      hovednavn
    2. name:
      Erstták
      language:
      Nordsamisk
      status:
      hovednavn
    type:
    Gard
    status:
    aktiv
    distance_km:
    0.317
    lat:
    68.41416
    lon:
    15.83202
    stedsnummer:
    989384
  6. names:

    1 results

    1. name:
      Erikstad
      language:
      Norsk
      status:
      hovednavn
    type:
    Bruk
    status:
    aktiv
    distance_km:
    0.335
    lat:
    68.4129
    lon:
    15.83443
    stedsnummer:
    989406
  7. names:

    2 results

    1. name:
      Gårdsøya
      language:
      Norsk
      status:
      hovednavn
    2. name:
      Gardsøya
      language:
      Norsk
      status:
      hovednavn
    type:
    Holme i sjø
    status:
    aktiv
    distance_km:
    0.388
    lat:
    68.4165
    lon:
    15.84855
    stedsnummer:
    138302
  8. names:

    1 results

    1. name:
      Erikstad
      language:
      Norsk
      status:
      hovednavn
    type:
    Bruk
    status:
    aktiv
    distance_km:
    0.398
    lat:
    68.41236
    lon:
    15.83385
    stedsnummer:
    989408

Scoped lookups for this place

Are you generating code? Programmatic access

Use the read-only JSON endpoint after verifying the parameters and data category in HTML.

Programmatic access to this place section (JSON)

How an AI agent should use this page

Ground rule: Navigate with HTML GET links to keep explanations and relationships. Use the page's JSON alternative only when concrete values must be extracted, compared or computed.

How to use the combined place page

  1. Confirm the place with the Geonorge section. The coordinate is the linking key for the rest of the page.
  2. Read the availability status per source. "Unavailable" is not the same as "no results".
  3. Follow a concrete result onward to a vessel, port, aquaculture site or air station when more detail is needed.

Related lookups

Precision: Do not present nearby results as if they are at the coordinate itself. State the distance or search radius.