id: https://nde.nl/ontology/hc/slot/has_geospatial_location
name: has_geospatial_location_slot
title: Has Geospatial Location Slot
description: 'Links a nominal place reference to its precise geospatial coordinates.


  **CRITICAL DISTINCTION**:


  | Nominal Place | GeoSpatialPlace |

  |---------------|-----------------|

  | Name-based reference | Geospatial data |

  | "het herenhuis in de Schilderswijk" | lat: 52.0705, lon: 4.2894 |

  | Identifies place by name | Locates place precisely |

  | May be vague ("the mansion") | Precise, measurable |

  | Source: archival documents | Source: GPS, cadastral surveys |


  **TOOI Ontology Pattern**:


  Following TOOI BestuurlijkeRuimte pattern:

  - TOOI: tooi:BestuurlijkeRuimte → tooi:hasGeometry → geosparql:Geometry

  - Here: Place → has_geospatial_location → GeoSpatialPlace


  GeoSPARQL: hasGeometry links Feature to Geometry representation.

  '
prefixes:
  linkml: https://w3id.org/linkml/
  hc: https://nde.nl/ontology/hc/
  geosparql: http://www.opengis.net/ont/geosparql#
imports:
  - linkml:types
  - ../classes/GeoSpatialPlace
slots:
  has_geospatial_location:
    slot_uri: geosparql:hasGeometry
    range: GeoSpatialPlace
    required: false
    multivalued: true
    inlined_as_list: true
    description: "Links this auxiliary place to precise geospatial coordinates and geometry.\n\n**W3C Location Core Vocabulary\
      \ (LOCN) Alignment**:\n\n`locn:geometry` - \"Associates any resource with a corresponding Geometry.\"\n\nThis property\
      \ aligns with:\n- W3C LOCN: locn:geometry (primary)\n- GeoSPARQL: geosparql:hasGeometry (for spatial queries)\n- TOOI:\
      \ tooi:BestuurlijkeRuimte-hasGeometry (Dutch government pattern)\n\n**CRITICAL DISTINCTION**:\n\n| Property | Type |\
      \ Example |\n|----------|------|---------|\n| latitude/longitude (this class) | Simple float | 52.1561, 5.3878 |\n|\
      \ has_geospatial_location | GeoSpatialPlace | Full geospatial object with WKT polygon, OSM ID, etc. |\n\n**When to Use\
      \ Each**:\n\n- **latitude/longitude only**: Quick geocoding, point location sufficient\n- **has_geospatial_location**:\
      \ Building footprints, boundary polygons, OSM/GeoNames linking, \n  accuracy metadata, temporal validity of boundaries\n\
      \n**Use Cases**:\n\n1. **Storage Facility with Building Footprint**:\n   ```yaml\n   has_geospatial_location:\n    \
      \ geometry_wkt: \"POLYGON((5.385 52.154, 5.390 52.154, ...))\"\n     osm_id: \"way/123456789\"\n     has_accuracy_in_meters:\
      \ 1.0\n   ```\n\n2. **Branch Office with GeoNames Linking**:\n   ```yaml\n   has_geospatial_location:\n     latitude:\
      \ 52.0705\n     longitude: 4.2894\n     geonames_id: 2759633\n     feature_code: \"S.LIBR\"\n   ```\n\n3. **Historical\
      \ Boundary** (temporal validity):\n   ```yaml\n   has_geospatial_location:\n     - geospatial_id: \"old-boundary\"\n\
      \       geometry_wkt: \"POLYGON(...)\"\n       valid_to_geo: \"2001-01-01\"\n     - geospatial_id: \"new-boundary\"\n\
      \       geometry_wkt: \"POLYGON(...)\"\n       valid_from_geo: \"2001-01-01\"\n   ```\n\n**Relationship to CustodianPlace**:\n\
      \nBoth CustodianPlace and AuxiliaryPlace can link to GeoSpatialPlace:\n- CustodianPlace.has_geospatial_location → main\
      \ building coordinates\n- AuxiliaryPlace.has_geospatial_location → subordinate site coordinates\n\nThis enables spatial\
      \ queries across all heritage custodian locations.\n"
    exact_mappings:
    - geosparql:hasGeometry
    related_mappings:
    - rdf:type
    broad_mappings:
    - schema:location
comments:
- Used by CustodianPlace (main places) and AuxiliaryPlace (subordinate sites)
- Links to GeoSpatialPlace class with coordinates, WKT geometry, GeoNames IDs
- Multivalued - a place can have multiple geospatial locations (e.g., historical boundaries)
- Optional - not all place references have known coordinates