-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathCITATION.cff
More file actions
49 lines (44 loc) · 1.46 KB
/
CITATION.cff
File metadata and controls
49 lines (44 loc) · 1.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
cff-version: 1.2.0
title: MobilityAPI
type: software
message: "If you use MobilityAPI in academic or technical work, please cite it using the metadata below."
abstract: >-
MobilityAPI is an OGC API – Moving Features Standard reference
implementation for MEOS-stored mobility data. It provides REST
endpoints (GET / POST / PUT / DELETE) over collections of moving
features, suitable for HTTP-driven clients consuming MobilityDB
trajectories.
authors:
- family-names: Meraoui
given-names: Sirine
affiliation: Université libre de Bruxelles (ULB)
repository-code: "https://github.com/MobilityDB/MobilityAPI"
url: "https://libmeos.org/bindings/mobilityapi/"
keywords:
- mobility
- trajectory
- ogc-api
- moving-features
- mobilitydb
- meos
- rest-api
license: PostgreSQL
references:
- type: software
title: pg_mfserv
abstract: >-
Founding OGC API – Moving Features Python server for
MobilityDB. The initial implementation that MobilityAPI
extends.
authors:
- family-names: Schoemans
given-names: Maxime
affiliation: Université libre de Bruxelles (ULB)
- family-names: Morabito
given-names: Victor
affiliation: Université libre de Bruxelles (ULB)
repository-code: "https://github.com/MobilityDB/pg_mfserv"
notes: >-
Predecessor implementation; archived at
MobilityDB/pg_mfserv. MobilityAPI builds on its OGC endpoint
design and PyMEOS integration pattern.