BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.staging.osgeo.org//foss4g-asia-2023//speaker//EC7E
 XA
BEGIN:VTIMEZONE
TZID:KST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1
TZNAME:KST
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-foss4g-asia-2023-WEAGWW@talks.staging.osgeo.org
DTSTART;TZID=KST:20231128T140000
DTEND;TZID=KST:20231128T180000
DESCRIPTION:Moving feature data can represent various phenomena\, including
  vehicles\, people\, animals\, weather patterns\, and more. Conceptually\,
  Moving Features are dynamic geospatial data that change location and poss
 ibly other characteristics over time. \n\nOGC API – Moving Features (OGC
  API – MF) provides a standard and interoperable way to manage such data
 \, with valuable applications in transportation management\, disaster resp
 onse\, environmental monitoring\, and beyond. OGC API – MF also includes
  operations for filtering\, sorting\, and aggregating moving feature data 
 based on location\, time\, and other properties. \n\nThis workshop will ge
 t you started with OGC API – MF and its implementation in MF-API Server 
 that is based on pygeoapi and MobilityDB\, covering the following question
 s:\n- What is the core concept of OGC API – MF (and OGC MF-JSON format)?
 \n- How to implement OGC API – MF with pygeoapi and MobilityDB?\n- How c
 an we visualize its results with STINUUM (with CesiumJS)?\n- How can we im
 plement a new feature that hasn't been implemented yet?\n\nThe below open 
 sources will be used in this workshop:\n- MF-API Server based on pygeoapi:
  https://github.com/aistairc/mf-api \n- OGC API – Moving Features offici
 al GitHub repository: https://github.com/opengeospatial/ogcapi-movingfeatu
 res\n- MobilityDB (and its Python driver\, PyMEOS\, and MEOS): https://git
 hub.com/MobilityDB \n- STINUUM: https://github.com/aistairc/mf-cesium \nTh
 e installation of each program will use a Docker file.\n\nLastly\, you can
  check many helpful information about OGC API – MF here: https://ogcapi.
 ogc.org/movingfeatures/
DTSTAMP:20260517T210644Z
LOCATION:Taepyeong Hall
SUMMARY:OGC API – Moving Features\, an introduction with MF-API Server ba
 sed on pygeoapi and MobilityDB - Wijae Cho\, Taehoon Kim\, Hirofumi Hayash
 i\, Tsubasa Shimizu\, Tran Thuan Bang\, Kyoungsook Kim
URL:https://talks.staging.osgeo.org/foss4g-asia-2023/talk/WEAGWW/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-foss4g-asia-2023-MV3H9R@talks.staging.osgeo.org
DTSTART;TZID=KST:20231129T141000
DTEND;TZID=KST:20231129T143000
DESCRIPTION:We created a REST API to register\, search\, and delete spatio-
 temporal data based on OGC API-Features\, an international standard specif
 ication of the Open Geospatial Consortium (OGC)\, an international standar
 dization organization for geospatial information\, and the Moving Feature 
 Encoding Extension-JSON (MF-JSON) specification\, an international OGC sta
 ndard specification developed mainly by AIST. \nTo create the API\, we bui
 lt an OGC-API server using pygeoapi and PyMEOS.PostgreSQL was used as the 
 DB\, and mobilityDB was used as an extension library for storing spatio-te
 mporal data.For spatio-temporal data were stored using MobilityDB-specific
  type formats (TBool\, TText\, TInt\, and TFloat).When converting MF-JSON 
 for spatio-temporal data using PyMEOS functions\, some tag names were not 
 supported for conversion.Therefore\, we implemented an additional process 
 to convert the tag name to one that can be successfully registered before 
 executing the PyMEOS function.\nAlso\, at the time of this implementation\
 , there were no source code modification guidelines for pygeoapi\, so the 
 API implementation was realized by directly modifying the source code of t
 he lib directory that handles the API request processing.
DTSTAMP:20260517T210644Z
LOCATION:Taepyeong Hall
SUMMARY:API Implementation of the OGC API Moving Feature - Taehoon Kim\, Hi
 rofumi Hayashi\, Tsubasa Shimizu\, Tran Thuan Bang\, Kyoungsook Kim
URL:https://talks.staging.osgeo.org/foss4g-asia-2023/talk/MV3H9R/
END:VEVENT
END:VCALENDAR