Stephen Gadd

Results 20 issues of Stephen Gadd

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

@kgeographer has drawn our attention to the OGC draft standard for JSON-FG (features and geometry) [here](https://docs.ogc.org/DRAFTS/21-045.html), which proposes adding a simple time element to GeoJSON (among other things). The proposals...

enhancement
JSON Schema

LP standard at present requires `coordinates` within geometries. The GeoJSON standard allows for unlocated features but requires that they have _null_ geometry. PROPOSAL: Drop the requirement for `coordinates` to allow...

enhancement
JSON Schema

LP standard requires the `names` property and at least the first of the `toponyms` to have a `citation`, and for at least one `citation` to have a year (implemented as...

enhancement
JSON Schema

'Linked Places format supports four types of linked resources', not including 'exactMatch' although this is used in examples within the documentation. PROPOSAL: Add 'exactMatch' to the standard list.

enhancement
JSON Schema

PROPOSAL: Add `fragmentSelector` as an optional property for `depictions`. These can be applied to any image, but can be particularly useful for IIIF sources. Outlined in [LP.json](https://github.com/docuracy/Locolligo/blob/main/schemas/LP.json).

enhancement
JSON Schema

PROPOSAL: drop the _requirement_ for a 'when' property to temporally scope a) an entire Feature; b) a name; c) a geometry (representative point or extent); d) a type; or e)...

enhancement
JSON Schema

PROPOSAL: Add optional root properties to the LP standard to facilitate indexing by search engines ([example](https://search.google.com/test/rich-results/result?id=iBSG1FT2zxMeArtNnZrupw)) and the embedding of citation data. These are the properties described in this [xLP...

enhancement
JSON Schema

## Description At present, it seems that when an input dataset is read from an hdf5 file, the file is locked in read-only mode, making it impossible to export another...

## Description Setting `--export_source` as an array of values would cause the export of multiple datasets (defined by corresponding multiple values for `--output_format` and `--output_filename_format`). ## Scenario - I am...