linked-places-format icon indicating copy to clipboard operation
linked-places-format copied to clipboard

Linked Places format is used to describe attestations of places in a standard way, primarily for linking gazetteer datasets.

Results 35 linked-places-format issues
Sort by recently updated
recently updated
newest added

### Existing situation Currently, geometry in Linked Places format (LPF) has a "certainty" attribute, which allows one of three values, "certain", "less-certain", and "uncertain" (see B below). This convention is...

Wikidata being somewhat ubiquitous these days, wouldn't it be desirable to include a namespace prefix for it in the Linked Places context document, like this? `"wd": "http://www.wikidata.org/entity/"` This is the...

JSON Schema

I'm working on a Pelagios-related project with data about historical places and events, and we are experimenting with CIDOC CRM to model the domain. Is there an "official" owl or...

enhancement
question

There is almost always _some_ approximation in the expression of Point coordinates, and it would be useful to be able to indicate the degree of approximation. For example, archaeological find...

enhancement
JSON Schema

PROPOSAL: An optional `uuid` property that can be used in Geometry Collections to associate particular geometries with one or more of their parent feature's types. This might be used, for...

enhancement
JSON Schema

The LP standard limits `types` to **places**, but the format has been found usefully to serve datasets in which the `features` are actually geolocated objects, for example archaeological finds. Visualisation...

enhancement
JSON Schema

[Specification](https://github.com/LinkedPasts/linked-places-format#when-required) requires one of in|earliest|latest, but the given examples omit these properties.

JSON Schema

In comments below, please add links to or snippets of data that should be considered for further LPF development and/or interaction with [Linked Traces format](https://github.com/LinkedPasts/linked-traces-format) or similar.

Before we get into the weeds of discussing various proposals for new properties of LPF, I think there is a need for consensus on the high-level vision for the format....

PROPOSAL: Add optional `sourceLabels` to the `relations` properties (as already specified for feature `types`). Outlined in [LP.json](https://github.com/docuracy/Locolligo/blob/main/schemas/LP.json).

enhancement
JSON Schema