https://wiki.xiph.org/api.php?action=feedcontributions&user=Spomky&feedformat=atomXiphWiki - User contributions [en]2024-03-29T09:49:14ZUser contributionsMediaWiki 1.40.1https://wiki.xiph.org/index.php?title=Tracking&diff=12949Tracking2011-08-09T11:03:45Z<p>Spomky: /* Tracking mapping into Ogg */</p>
<hr />
<div>'''Tracking''' is a timed text codec. It allows to localize a time-continuously sampled data file by providing geolocalisation from a GPS device. This geolocalisation is NMEA sentences and multimedia players have to parse them to extract informations (position, speed, orientation, satellites informations, ...).<br />
<br />
Tracking is appropriate for use with all [[Ogg]] media formats. This description explains how to map Tracking into Ogg.<br />
<br />
<br />
== Tracking specification ==<br />
<br />
Before describing the actual data that goes into a logical Ogg bitstream, we need to understand what the stand-alone "codec" packets contains.<br />
<br />
Tracking basically consists of <b>data</b> elements which contains NMEA sentences<br />
<br />
An example Tracking file looks like this:<br />
<br />
<pre><br />
<?xml version="1.0"?><br />
<track xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="track.xsd"><br />
<metadata key="key1">value1</metadata><br />
<metadata key="key2"><![CDATA[value2]]></metadata><br />
<data position="0"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
<data position="1"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
</track><br />
</pre><br />
<br />
The <b>track</b> element (root element) have no required property:<br />
This root element contains metadata and data elements.<br />
<br />
The <b>metadata</b> elements have one required property:<br />
* key: the key name<br />
Metadata gives informations about the track: device, weather, date, links, email address, ...<br />
<br />
The <b>data</b> elements have one required property:<br />
* position: the position of the data in the video (in seconds)<br />
<br />
A Tracking file must be valid. Here is the XML Schema "track.xsd":<br />
<pre><br />
<?xml version="1.0"?><br />
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br />
<xsd:element name="metadata" type="typeMetadata" /><br />
<xsd:element name="data" type="typeData" /><br />
<xsd:element name="track" type="typeTrack" /><br />
<br />
<xsd:complexType name="typeMetadata"><br />
<xsd:simpleContent><br />
<xsd:extension base="xsd:string"><br />
<xsd:attribute name="key" type="xsd:string" use="required" /><br />
</xsd:extension><br />
</xsd:simpleContent><br />
</xsd:complexType><br />
<br />
<xsd:complexType name="typeData"><br />
<xsd:simpleContent><br />
<xsd:extension base="xsd:string"><br />
<xsd:attribute name="position" type="xsd:string" use="required" /><br />
</xsd:extension><br />
</xsd:simpleContent><br />
</xsd:complexType><br />
<br />
<xsd:complexType name="typeTrack"><br />
<xsd:sequence><br />
<xsd:element ref="metadata" minOccurs="0" maxOccurs="unbounded" /><br />
<xsd:element ref="data" minOccurs="1" maxOccurs="unbounded" /><br />
</xsd:sequence><br />
</xsd:complexType><br />
</xsd:schema><br />
</pre><br />
<br />
== Tracking mapping into Ogg ==<br />
<br />
When Tracking is mapped into an Ogg logical bitstream it needs to be serialised first. XML is a hierarchical file format, so is not generally serialisable. However, Tracking has been designed to be serialised easily.<br />
<br />
All of the Tracking bitstream information is text. As it gets encoded into a binary bitstream, an encoding format has to be specified. To simplify things, UTF-8 is defined as the mandatory encoding format for all data in a Tracking binary bitstream. <br />
<br />
The media mapping for Tracking into Ogg is as follows:<br />
* The bos page contains a Tracking ident packet.<br />
* The next page contains all metadata each encoded in their own packet.<br />
* The content or data packets contain the "data" tags each encoded in their own packet and inserted at the accurate time.<br />
* The eos page contains a packet with an empty data tag.<br />
<br />
<br />
=== The Tracking ident header packet ===<br />
<br />
The Tracking logical bitstream starts with an ident header which is encapsulated into the Tracking bos page. The ident header contains all information required to identify the Tracking bitstream and to set up a Tracking decoder. It has the following format:<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Identifier 'TRCK\0\0\0\0' | 0-3<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| | 4-7<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Version major | Version minor | 8-11<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ...<br />
<br />
The Tracking<i>version</i> as described here is major=0 minor=1.<br />
<br />
=== The Tracking data packets ===<br />
<br />
The data packets of the Tracking bitstream contain the Tracking <b>data</b> elements. Their <b>position</b> attributes however only exist for authoring purposes and are not copied into the bitstream (to avoid contradictory information), but are rather represented through the time mapping of the encapsulation format that interleaves Tracking data with data from other time-continuous bitstreams. Generally the time mapping is done through some timestamp representation and through the position in the stream.<br />
<br />
A <b>data</b> tag is encoded with all tags (except for the <b>position</b> attribute) as a string printed into a clip packet. The <b>data</b> tag's <b>position</b> attribute tells the encapsulator at what time to insert the clip packet into the bitstream. It duration is one second.<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| <data ... | 0-<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ... |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| </data> |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
<br />
== Development ==<br />
<br />
<br />
== External links ==<br />
<br />
* NMEA sentences: [http://www.gpsinformation.org/dale/nmea.htm]<br />
<br />
[[Category:Ogg Mappings]]</div>Spomkyhttps://wiki.xiph.org/index.php?title=Tracking&diff=12948Tracking2011-08-09T10:47:56Z<p>Spomky: /* Tracking specification */</p>
<hr />
<div>'''Tracking''' is a timed text codec. It allows to localize a time-continuously sampled data file by providing geolocalisation from a GPS device. This geolocalisation is NMEA sentences and multimedia players have to parse them to extract informations (position, speed, orientation, satellites informations, ...).<br />
<br />
Tracking is appropriate for use with all [[Ogg]] media formats. This description explains how to map Tracking into Ogg.<br />
<br />
<br />
== Tracking specification ==<br />
<br />
Before describing the actual data that goes into a logical Ogg bitstream, we need to understand what the stand-alone "codec" packets contains.<br />
<br />
Tracking basically consists of <b>data</b> elements which contains NMEA sentences<br />
<br />
An example Tracking file looks like this:<br />
<br />
<pre><br />
<?xml version="1.0"?><br />
<track xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="track.xsd"><br />
<metadata key="key1">value1</metadata><br />
<metadata key="key2"><![CDATA[value2]]></metadata><br />
<data position="0"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
<data position="1"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
</track><br />
</pre><br />
<br />
The <b>track</b> element (root element) have no required property:<br />
This root element contains metadata and data elements.<br />
<br />
The <b>metadata</b> elements have one required property:<br />
* key: the key name<br />
Metadata gives informations about the track: device, weather, date, links, email address, ...<br />
<br />
The <b>data</b> elements have one required property:<br />
* position: the position of the data in the video (in seconds)<br />
<br />
A Tracking file must be valid. Here is the XML Schema "track.xsd":<br />
<pre><br />
<?xml version="1.0"?><br />
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><br />
<xsd:element name="metadata" type="typeMetadata" /><br />
<xsd:element name="data" type="typeData" /><br />
<xsd:element name="track" type="typeTrack" /><br />
<br />
<xsd:complexType name="typeMetadata"><br />
<xsd:simpleContent><br />
<xsd:extension base="xsd:string"><br />
<xsd:attribute name="key" type="xsd:string" use="required" /><br />
</xsd:extension><br />
</xsd:simpleContent><br />
</xsd:complexType><br />
<br />
<xsd:complexType name="typeData"><br />
<xsd:simpleContent><br />
<xsd:extension base="xsd:string"><br />
<xsd:attribute name="position" type="xsd:string" use="required" /><br />
</xsd:extension><br />
</xsd:simpleContent><br />
</xsd:complexType><br />
<br />
<xsd:complexType name="typeTrack"><br />
<xsd:sequence><br />
<xsd:element ref="metadata" minOccurs="0" maxOccurs="unbounded" /><br />
<xsd:element ref="data" minOccurs="1" maxOccurs="unbounded" /><br />
</xsd:sequence><br />
</xsd:complexType><br />
</xsd:schema><br />
</pre><br />
<br />
== Tracking mapping into Ogg ==<br />
<br />
When Tracking is mapped into an Ogg logical bitstream it needs to be serialised first. XML is a hierarchical file format, so is not generally serialisable. However, Tracking has been designed to be serialised easily.<br />
<br />
All of the Tracking bitstream information is text. As it gets encoded into a binary bitstream, an encoding format has to be specified. To simplify things, UTF-8 is defined as the mandatory encoding format for all data in a Tracking binary bitstream. <br />
<br />
The media mapping for Tracking into Ogg is as follows:<br />
* The bos page contains a Tracking ident packet.<br />
* The content or data packets contain the "data" tags each encoded in their own packet and inserted at the accurate time.<br />
* The eos page contains a packet with an empty data tag.<br />
<br />
<br />
=== The Tracking ident header packet ===<br />
<br />
The Tracking logical bitstream starts with an ident header which is encapsulated into the Tracking bos page. The ident header contains all information required to identify the Tracking bitstream and to set up a Tracking decoder. It has the following format:<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Identifier 'TRCK\0\0\0\0' | 0-3<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| | 4-7<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Version major | Version minor | 8-11<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ...<br />
<br />
The Tracking<i>version</i> as described here is major=0 minor=1.<br />
<br />
=== The Tracking data packets ===<br />
<br />
The data packets of the Tracking bitstream contain the Tracking <b>data</b> elements. Their <b>position</b> attributes however only exist for authoring purposes and are not copied into the bitstream (to avoid contradictory information), but are rather represented through the time mapping of the encapsulation format that interleaves Tracking data with data from other time-continuous bitstreams. Generally the time mapping is done through some timestamp representation and through the position in the stream.<br />
<br />
A <b>data</b> tag is encoded with all tags (except for the <b>position</b> attribute) as a string printed into a clip packet. The <b>data</b> tag's <b>position</b> attribute tells the encapsulator at what time to insert the clip packet into the bitstream. It duration is one second.<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| <data ... | 0-<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ... |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| </data> |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
<br />
<br />
== Development ==<br />
<br />
<br />
== External links ==<br />
<br />
* NMEA sentences: [http://www.gpsinformation.org/dale/nmea.htm]<br />
<br />
[[Category:Ogg Mappings]]</div>Spomkyhttps://wiki.xiph.org/index.php?title=Tracking&diff=12943Tracking2011-08-08T11:19:47Z<p>Spomky: Page creation. Please consider as a draft</p>
<hr />
<div>'''Tracking''' is a timed text codec. It allows to localize a time-continuously sampled data file by providing geolocalisation from a GPS device. This geolocalisation is NMEA sentences and multimedia players have to parse them to extract informations (position, speed, orientation, satellites informations, ...).<br />
<br />
Tracking is appropriate for use with all [[Ogg]] media formats. This description explains how to map Tracking into Ogg.<br />
<br />
<br />
== Tracking specification ==<br />
<br />
Before describing the actual data that goes into a logical Ogg bitstream, we need to understand what the stand-alone "codec" packets contains.<br />
<br />
Tracking basically consists of <b>data</b> elements which contains NMEA sentences<br />
<br />
An example Tracking file looks like this:<br />
<br />
<pre><br />
<?xml version="1.0"?><br />
<track xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="track.xsd"><br />
<data type="NMEA" position="0"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
<data type="NMEA" position="1"><br />
$GPRMC,162254.00,A,3723.02837,N,12159.39853,W,0.820,188.36,110706,,,A*74<br />
$GPVTG,188.36,T,,M,0.820,N,1.519,K,A*3F<br />
$GPGGA,162254.00,3723.02837,N,12159.39853,W,1,03,2.36,525.6,M,-25.6,M,,*65<br />
$GPGSA,A,2,25,01,22,,,,,,,,,,2.56,2.36,1.00*02<br />
$GPGSV,4,1,14,25,15,175,30,14,80,041,,19,38,259,14,01,52,223,18*76<br />
$GPGSV,4,2,14,18,16,079,,11,19,312,,14,80,041,,21,04,135,25*7D<br />
$GPGSV,4,3,14,15,27,134,18,03,25,222,,22,51,057,16,09,07,036,*79<br />
$GPGSV,4,4,14,07,01,181,,15,25,135,*76<br />
$GPGLL,3723.02837,N,12159.39853,W,162254.00,A,A*7C<br />
$GPZDA,162254.00,11,07,2006,00,00*63<br />
</data><br />
<data><br />
...<br />
</data><br />
</track><br />
</pre><br />
<br />
The <b>data</b> elements have two required properties:<br />
* type: the type of data stored (only NMEA is supported yet)<br />
* position: the position of the data in the video (in seconds)<br />
<br />
== Tracking mapping into Ogg ==<br />
<br />
When Tracking is mapped into an Ogg logical bitstream it needs to be serialised first. XML is a hierarchical file format, so is not generally serialisable. However, Tracking has been designed to be serialised easily.<br />
<br />
All of the Tracking bitstream information is text. As it gets encoded into a binary bitstream, an encoding format has to be specified. To simplify things, UTF-8 is defined as the mandatory encoding format for all data in a Tracking binary bitstream. <br />
<br />
The media mapping for Tracking into Ogg is as follows:<br />
* The bos page contains a Tracking ident packet.<br />
* The content or data packets contain the "data" tags each encoded in their own packet and inserted at the accurate time.<br />
* The eos page contains a packet with an empty data tag.<br />
<br />
<br />
=== The Tracking ident header packet ===<br />
<br />
The Tracking logical bitstream starts with an ident header which is encapsulated into the Tracking bos page. The ident header contains all information required to identify the Tracking bitstream and to set up a Tracking decoder. It has the following format:<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Identifier 'TRCK\0\0\0\0' | 0-3<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| | 4-7<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| Version major | Version minor | 8-11<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ...<br />
<br />
The Tracking<i>version</i> as described here is major=0 minor=1.<br />
<br />
=== The Tracking data packets ===<br />
<br />
The data packets of the Tracking bitstream contain the Tracking <b>data</b> elements. Their <b>position</b> attributes however only exist for authoring purposes and are not copied into the bitstream (to avoid contradictory information), but are rather represented through the time mapping of the encapsulation format that interleaves Tracking data with data from other time-continuous bitstreams. Generally the time mapping is done through some timestamp representation and through the position in the stream.<br />
<br />
A <b>data</b> tag is encoded with all tags (except for the <b>position</b> attribute) as a string printed into a clip packet. The <b>data</b> tag's <b>position</b> attribute tells the encapsulator at what time to insert the clip packet into the bitstream. It duration is one second.<br />
<br />
0 1 2 3<br />
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| Byte<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| <data ... | 0-<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| ... |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
| </data> |<br />
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br />
<br />
<br />
== Development ==<br />
<br />
<br />
== External links ==<br />
<br />
* NMEA sentences: [http://www.gpsinformation.org/dale/nmea.htm]<br />
<br />
[[Category:Ogg Mappings]]</div>Spomky