- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
OGC calls for comment on candidate Moving Feature Encoding standard
The OGC seeks public comment on a candidate OGC® Moving Feature Encoding Standard. Part I of this candidate standard provides a standard way of encoding moving feature data in an XML encoding in the form of an OGC Geography Markup Language (GML) application schema. Part II provides a standard way of encoding moving feature data in a simple CSV (comma-separated value) format.
The candidate OGC® Moving Feature Encoding Standard is available below. Comments are due by 23 August 2014.
The advance of mobile computing and internet-connected sensors (including sensors and GPS transponders in cell phones and notebook computers) brings with it a rapid rise in applications for moving feature data, typically representing vehicles or pedestrians. Many innovative moving feature applications will require the overlay and integration of moving feature data from different sources. Examples can easily be imagined for disaster risk management, traffic information services, security services, navigation for robots, aviation or maritime traffic monitoring, and wildlife tracking and conservation. Most current applications, however, are limited to single-source moving feature data.
More efficient moving feature data exchange will result in a requirement for massive data handling. The CSV style encoding provides an efficient and easily understood standard for encoding lightweight data records, which will be important for many applications involving large data volumes and real-time response. The GML application schema style encoding for Moving Features provides for the encoding of more complex spatial information.
This standard addresses only “rigid” moving features, such as vehicles, as opposed to those that deform, such as flood water, and it does not address moving features whose descriptions contain other moving features that must be updated as the feature moves, such as control surfaces on an unmanned aerial vehicle (UAV). It also is for archived Moving Feature data only, and not for live feeds from sensors.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists [dot] opengeospatial [dot] org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template