Skip to content

GeoCoordinates builder

Creates geographic coordinates from numbers or strings. The GeoCoordinates builder injects @type, validates synchronously, and rejects unknown properties.

// Astro — shown first when Astro is selected
import { GeoCoordinates } from '@unschema-graph/astro';
// Svelte 5
import { GeoCoordinates } from '@unschema-graph/svelte';
// Core / Node.js
import { GeoCoordinates } from '@unschema-graph/core';
import { GeoCoordinatesSchema } from '@unschema-graph/core';

The GeoCoordinatesSchema Zod schema is also exported for composition and advanced validation.

import {
GeoCoordinatesSchema,
type SchemaInput,
type SchemaOutput,
} from '@unschema-graph/core';
type GeoCoordinatesInput = SchemaInput<typeof GeoCoordinatesSchema>;
type GeoCoordinatesOutput = SchemaOutput<typeof GeoCoordinatesSchema, 'GeoCoordinates'>;
Property Input type Required Default / constraints
@id string No —
latitude number | string Yes —
longitude number | string Yes —
elevation number | string No —

The aliases above remain the exact authority for nested object types. The builder also accepts a validation configuration as its second argument and always returns @type: 'GeoCoordinates'.

import { GeoCoordinates } from '@unschema-graph/core';
const entity = GeoCoordinates({
"latitude": 48.8566,
"longitude": 2.3522
});
{
"@type": "GeoCoordinates",
"latitude": 48.8566,
"longitude": 2.3522
}
  • Passing an unknown property to the strict builder.
  • Using source data that is missing a required property.
  • Assuming valid Schema.org guarantees a search appearance.

Use GeoCoordinates.safeParse(input) for external data. If Schema.org supports a property that is not modeled yet, validate the entity first and then use withAdditionalProperties(). Never pass invented properties to the strict builder.