Berth

Version: 0.0.1

Description

This data model is intended to provide information about Berths. We define 'berth' to each stop of a ship during a PortCall, both for a port-facility (berth) and as an anchorage area. Each berth has a berthing time (estimated, planned, etc.), a lifecycle (estimated, requested, approved, etc.), an main activity during the stop (commercial operations, major repair, etc.) and a number of attributes described below. When commercial operations take place, an Operation entity will define the details of each commercial operation

data model mapped from ERA ontology https://data-interop.era.europa.eu/era-vocabulary (European Union Agency for Railways)

Specification

Link to the interactive specification

Link to the specification

Examples

Link to the example (keyvalues) for NGSI v2

Link to the example (keyvalues) for NGSI-LD

Link to the example (normalized) for NGSI-V2

Link to the example (normalized) for NGSI-LD

Link to the example (keyvalues) for NGSI v2 in CSV format

Link to the example (keyvalues) for NGSI-LD in CSV format

Link to the example (normalized) for NGSI-V2 in CSV format

Link to the example (normalized) for NGSI-LD in CSV format

Dynamic Examples generation

Link to the Generator of NGSI-LD normalized payloads compliant with this data model. Refresh for new values

Link to the Generator of NGSI-LD keyvalues payloads compliant with this data model. Refresh for new values

Link to the Generator of geojson feature format payloads compliant with this data model. Refresh for new values

PostgreSQL schema

Link to the PostgreSQL schema of this data model

Contribution

If you have any issue on this data model you can raise an issue or contribute with a PR

If you wish to develop your own data model you can start from contribution manual. Several services have been developed to help with:

• Test data model repository including the schema and example payloads, etc
• Generate PostgreSQL schema to help create a table, create type, etc