<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/asterix/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/asterix/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/asterix/feature-requests/</id><updated>2012-12-21T19:56:04Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Category 63 support</title><link href="https://sourceforge.net/p/asterix/feature-requests/2/" rel="alternate"/><published>2012-12-21T19:56:04Z</published><updated>2012-12-21T19:56:04Z</updated><author><name>Jeff Lawson</name><uri>https://sourceforge.net/u/bovineone/</uri></author><id>https://sourceforge.net7da7c0f0bd872747d4158a417d7438416297c7d6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It seems that category 63 support does not yet exist.  It is defined by the following PDF:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.eurocontrol.int/sites/default/files/content/documents/nm/asterix/archives/asterix-cat063-spds-part10-v1.1-042005.pdf" rel="nofollow"&gt;http://www.eurocontrol.int/sites/default/files/content/documents/nm/asterix/archives/asterix-cat063-spds-part10-v1.1-042005.pdf&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Schema enhancement</title><link href="https://sourceforge.net/p/asterix/feature-requests/1/" rel="alternate"/><published>2012-06-10T07:01:33Z</published><updated>2012-06-10T07:01:33Z</updated><author><name>Horst Dehmer</name><uri>https://sourceforge.net/u/dehmer/</uri></author><id>https://sourceforge.net720cc62cfdd8710c5b14ab7b9133e167cf88620e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For data extraction/conversion it would be helpful to add some additional meta data to the XML specification schema.&lt;br /&gt;
Two's complement fields often define a scale (LSB) and a unit of measurement (UOM).&lt;/p&gt;
&lt;p&gt;Examples&lt;br /&gt;
I062/070 (Time of Track): scale = 1/128, UOM = s&lt;br /&gt;
I062/100 (X/Y): scale/LSB = 0.5, UOM = m&lt;br /&gt;
I062/105 (latitude/longitude): scale/LSB = 180/2^25, UOM = degrees/°&lt;br /&gt;
I062/110/#4 (GNSS-derived Altitude): scale/LSB = 25, UOM = ft&lt;br /&gt;
I062/135 (Calculated Track Barometric Altitude): scale/LSB = 1/4, UOM = FL&lt;br /&gt;
062/185 (Vx/Vy): scale/LSB = 0.25, UOM = m/s&lt;/p&gt;
&lt;p&gt;Adding such (optional) information, let's say to the format element, would greatly help data extraction/conversion.&lt;/p&gt;
&lt;p&gt;Proposal&lt;br /&gt;
&amp;lt;dataitem id="I062/070" ...&amp;gt;&lt;br /&gt;
&amp;lt;field ...&amp;gt;&lt;br /&gt;
&amp;lt;format scale="1/128" uom="s"&amp;gt;uint&amp;lt;/format&amp;gt;&lt;br /&gt;
&amp;lt;/field&amp;gt;&lt;br /&gt;
&amp;lt;/dataitem&amp;gt;&lt;/p&gt;
&lt;p&gt;For better readability (and higher accuracy) it probably would be advisable to not evaluate the scale and include it as is, i.e. 180/2^25 instead of 0,0000053644. A simple expression parser could evaluate the scales as needed at runtime.&lt;/p&gt;
&lt;p&gt;If we could find some way or another to include these information, I'd happy to provide some patches (at least for cat. 62)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>