Skip to content

Commit

Permalink
revised_20190805
Browse files Browse the repository at this point in the history
  • Loading branch information
Kyoungsook Kim committed Aug 5, 2019
1 parent f4d3b96 commit 7439e50
Show file tree
Hide file tree
Showing 109 changed files with 9,802 additions and 9,804 deletions.
112 changes: 56 additions & 56 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,56 +1,56 @@
![OGC Logo](http://portal.opengeospatial.org/files/?artifact_id=11976&format=gif "OGC Logo")
<img src="https://github.com/opengeospatial/mf-json/blob/master/logo.png" width="200">

# Moving Features JSON Encodings

This draft proposes a JSON encoding representation of movement of geographic features specified by OGC Moving Features ([OGC 14 083r2](http://docs.opengeospatial.org/is/14-083r2/14-083r2.html) and [OGC 14 084r2](http://docs.opengeospatial.org/is/14-084r2/14-084r2.html)).
A moving feature can be express as a dynamic geomtry whose location continouly changes over time. Also it can contain dynamic non-spatial attributes of features whose value varies with time.
The data format in this draft is extended from **GeoJSON terms** (type, geomtery, properties, etc.) in order to take the compatibility of GeoJSON.

## About

This GitHub repository tracks the latest version of the Moving Features JSON Encoding draft, which is not an OGC Stardard but will be publishied as an OGC Best Practice Paper. Therefore, it is not an official postion of the OGC memebership.
With this repository the OGC invites collaboration and comments directed at the development and enhancement of this candidate encoding format.
Pull requests for fixes are appreciated, and new functionality will still be considered until fixing the encoding format.
The specification is done in asciidoc a format supported by GitHub, similar to markdown but with some features that make it better for specifications, like automatic section numbering.

**Editor: Kyoung-Sook KIM, Nobuhiro ISHIMARU**

## Contributing

The contributor understands that any contributions, if accepted by the OGC Membership, shall
be incorporated into the formal OGC Moving Features standards document and that all copyright and
intellectual property shall be vested to the OGC.

The Moving Features Standards Working Group (SWG) is the group at OGC responsible for the stewardship
of the standard.

The Moving Features SWG currently has the following email list:
- [email protected] -- [sign up here](https://lists.opengeospatial.org/mailman/listinfo/moving-features.swg)
- Private List
- Access controlled archives
- Requires OGC membership and Observer Agreement to protect IPR (intellectual property rights)


**SWG Chair:**
+ Nobuhiro ISHIMARU(Hitachi, Ltd., Defense Systems Company)
+ Kyoung-Sook KIM(National Institute of Advanced Industrial Science & Technology (AIST))

## Editing and commenting
The Moving Features SWG is accepting public comments and suggested revisions to this document via GitHub.
To suggest changes to the document please fork the repository and submit a pull request with the desired changes.
Please make one pull request per logical requested change and be sure to include a comment in the PR with any justification or reasoning on why the change is needed.

For more general comments (that don't include actual text changes to the specification) please create a GitHub [issue](https://github.com/opengeospatial/geopackage/issues) for that topic.

Complex changes and feature requests must go throught the [change request](http://portal.opengeospatial.org/public_ogc/change_request.php) process. The details entered
in the change request form will help the SWG adjudicate and prioritize the request.

## Usages
1. Install [asciidoctor](http://asciidoctor.org)
2. On command line: asciidoctor -a stylesheet=./example.css index.adoc

**asciidoctor-pdf -r asciidoctor-mathematical -a pdf-stylesdir=. -a pdf-style=asciidoctor -o output.pdf index.adoc


[Document rendering example](https://ksookim.github.io/mf-json)
![OGC Logo](http://portal.opengeospatial.org/files/?artifact_id=11976&format=gif "OGC Logo")
<img src="https://github.com/opengeospatial/mf-json/blob/master/logo.png" width="200">

# Moving Features JSON Encodings

This draft proposes a JSON encoding representation of movement of geographic features specified by OGC Moving Features ([OGC 14 083r2](http://docs.opengeospatial.org/is/14-083r2/14-083r2.html) and [OGC 14 084r2](http://docs.opengeospatial.org/is/14-084r2/14-084r2.html)).
A moving feature can be express as a dynamic geomtry whose location continouly changes over time. Also it can contain dynamic non-spatial attributes of features whose value varies with time.
The data format in this draft is extended from **GeoJSON terms** (type, geomtery, properties, etc.) in order to take the compatibility of GeoJSON.

## About

This GitHub repository tracks the latest version of the Moving Features JSON Encoding draft, which is not an OGC Stardard but will be publishied as an OGC Best Practice Paper. Therefore, it is not an official postion of the OGC memebership.
With this repository the OGC invites collaboration and comments directed at the development and enhancement of this candidate encoding format.
Pull requests for fixes are appreciated, and new functionality will still be considered until fixing the encoding format.
The specification is done in asciidoc a format supported by GitHub, similar to markdown but with some features that make it better for specifications, like automatic section numbering.

**Editor: Kyoung-Sook KIM, Nobuhiro ISHIMARU**

## Contributing

The contributor understands that any contributions, if accepted by the OGC Membership, shall
be incorporated into the formal OGC Moving Features standards document and that all copyright and
intellectual property shall be vested to the OGC.

The Moving Features Standards Working Group (SWG) is the group at OGC responsible for the stewardship
of the standard.

The Moving Features SWG currently has the following email list:
- [email protected] -- [sign up here](https://lists.opengeospatial.org/mailman/listinfo/moving-features.swg)
- Private List
- Access controlled archives
- Requires OGC membership and Observer Agreement to protect IPR (intellectual property rights)


**SWG Chair:**
+ Nobuhiro ISHIMARU(Hitachi, Ltd., Defense Systems Company)
+ Kyoung-Sook KIM(National Institute of Advanced Industrial Science & Technology (AIST))

## Editing and commenting
The Moving Features SWG is accepting public comments and suggested revisions to this document via GitHub.
To suggest changes to the document please fork the repository and submit a pull request with the desired changes.
Please make one pull request per logical requested change and be sure to include a comment in the PR with any justification or reasoning on why the change is needed.

For more general comments (that don't include actual text changes to the specification) please create a GitHub [issue](https://github.com/opengeospatial/geopackage/issues) for that topic.

Complex changes and feature requests must go throught the [change request](http://portal.opengeospatial.org/public_ogc/change_request.php) process. The details entered
in the change request form will help the SWG adjudicate and prioritize the request.

## Usages
1. Install [asciidoctor](http://asciidoctor.org)
2. On command line: asciidoctor -a stylesheet=./example.css index.adoc

**asciidoctor-pdf -r asciidoctor-mathematical -a pdf-stylesdir=. -a pdf-style=asciidoctor -o output.pdf index.adoc


[Document rendering example](https://ksookim.github.io/mf-json)
108 changes: 54 additions & 54 deletions bp/0_preface.adoc
View file
Original file line number Diff line number Diff line change
@@ -1,54 +1,54 @@
[big]*i. Abstract*

This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]).
A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time.
This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures).
In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web.


[big]*ii. Keywords*

The following are keywords to be used by search engines and document catalogues.

ogcdoc, OGC document, moving features, encoding, JSON, REST


[big]*iii. Preface*

This Best Practice document follows the abstract data model defined in ISO 19141:2008 [ISO 19141:2008] with
the encoding method referring to the IETF GeoJSON Format [IETF RFC 7946].
OGC Moving Features Encoding standards XML Core [OGC 14 083r2] and Simple CSV [OGC 14 084r2] have focused on the movement of 0-dimensional geometric primitives (Points), called trajectories.
However, this document covers the movements of 0-dimensional Points, 1-dimensional curve LineStrings, and 2-dimensional surface Polygons to support application requirements such as disaster risk management, traffic information services, and geo-fencing services.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights.
The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

_Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation._

[big]*iv. Submitting organizations*

The following organization has submitted this Document to the Open GeoSpatial Consortium, Inc.:

* Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
[big]*v. Submitters*

All questions regarding this submission should be directed to the editor or the submitters:

{set:cellbgcolor!}
[width="99%", cols="3,7"]
|===========================================================
|*Name* |*Organization*
|Kyoung-Sook KIM |Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
|Hirotaka OGAWA |Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
|===========================================================


[big]*vi. Future Work*

Among the topics for future development are the following items:

- Testing RESTful API implementation;
- Moving features in an indoor space; and
- Representation of three-dimensional moving features.
[big]*i. Abstract*

This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]).
A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time.
This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures).
In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web.


[big]*ii. Keywords*

The following are keywords to be used by search engines and document catalogues.

ogcdoc, OGC document, moving features, encoding, JSON, REST


[big]*iii. Preface*

This Best Practice document follows the abstract data model defined in ISO 19141:2008 [ISO 19141:2008] with
the encoding method referring to the IETF GeoJSON Format [IETF RFC 7946].
OGC Moving Features Encoding standards XML Core [OGC 14 083r2] and Simple CSV [OGC 14 084r2] have focused on the movement of 0-dimensional geometric primitives (Points), called trajectories.
However, this document covers the movements of 0-dimensional Points, 1-dimensional curve LineStrings, and 2-dimensional surface Polygons to support application requirements such as disaster risk management, traffic information services, and geo-fencing services.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights.
The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

_Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation._

[big]*iv. Submitting organizations*

The following organization has submitted this Document to the Open GeoSpatial Consortium, Inc.:

* Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
[big]*v. Submitters*

All questions regarding this submission should be directed to the editor or the submitters:

{set:cellbgcolor!}
[width="99%", cols="3,7"]
|===========================================================
|*Name* |*Organization*
|Kyoung-Sook KIM |Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
|Hirotaka OGAWA |Artificial Intelligence Research Center, National Institute of Advanced Industrial Science and Technology
|===========================================================


[big]*vi. Future Work*

Among the topics for future development are the following items:

- Testing RESTful API implementation;
- Moving features in an indoor space; and
- Representation of three-dimensional moving features.
Loading

0 comments on commit 7439e50

Please sign in to comment.