Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/WebStart.php on line 100
Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/WebStart.php on line 103
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/Setup.php on line 381
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require_once(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/languages/Language.php on line 20
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: require(): Unable to allocate memory for pool. in /usr/local/www/mediawiki/includes/AutoLoader.php on line 1007
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:100) in /usr/local/www/mediawiki/includes/Feed.php on line 229
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:100) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:100) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:100) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38 http://fileformats.archiveteam.org/api.php?action=feedcontributions&feedformat=atom&user=NotpeterJust Solve the File Format Problem - User contributions [en]2025-05-22T01:47:13ZUser contributionsMediaWiki 1.19.2http://fileformats.archiveteam.org/wiki/User:NotpeterUser:Notpeter2021-11-11T22:04:52Z<p>Notpeter: create talk user page</p>
<hr />
<div>Notpeter<br />
<br />
* Twitter: [https://twitter.com/notpeter @notpeter]<br />
* Github: [https://github.com/notpeter @notpeter]<br />
* Email: <code>echo username@username.net | sed 's/username/notpeter/g'</code></div>Notpeterhttp://fileformats.archiveteam.org/wiki/EDIEDI2021-11-11T22:00:21Z<p>Notpeter: Initial page</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Transportation<br />
|extensions={{ext|edi}}, {{ext|x12}}, {{ext|edifact}}<br />
|mimetypes={{mimetype|application/edifact}}, {{mimetype|application/edi-x12}}<br />
}}<br />
'''Electronic Document Interchange ''', or '''EDI''', is a set of text-based data formats for structured communication between business systems.<br />
<br />
== EDI ==<br />
<br />
EDI (Electronic Document Interchange) is an umbrella term for many distinct standards for machine-to-machine communications that has been in continuous use since the 1970s. Despite the existence of numerous detailed standards, an EDI transaction set (e.g. EDI document) will have customer-specific mappings applied before transmission. As a result each EDI integration is often effectively a custom integration to meet specific business requirements. Documents are text or XML and normally transmitted transmitted via FTP / SFTP or with specialized client/server software (e.g. [https://en.wikipedia.org/wiki/AS1_(networking) AS1] (SMTP + SMIME) or [https://en.wikipedia.org/wiki/AS2 AS2] - HTTP + SMIME)).<br />
<br />
=== Parsing EDI ===<br />
<br />
XML-based EDI can be parsed any XML parser and then handled accordingly, but text-based EDI requires EDI-specific tools.<br />
<br />
Text based EDI files consist of a stream of segments. Each segment contains an array of elements. With each element containing data or sub elements themselves which contain data. Generally all data is ASCII characters and any binary data must be encoded in an ASCII safe manor (ie Base64 encoded). Specific implementations may support using UTF-8, UTF-16 or other locale-specific character-sets in place of ASCII. Although EDI tools often display one segment per line, often there are no line-breaks in EDI data file itself. This is because the "Segment Terminator" (the character or characters used as a delimiter between segments) is specified in a header segment (UNA for EDIFACT, ISA for X12). With Edifact traditionally using single quote <code>'</code> and X12 using tilde <code>~</code> instead of a line-break (<code>\n</code> or <code>\r\n</code>) as is common with text files. Each segment begins with a segment tag. In EDIFACT this is three alphabetic characters<br />
{{cite web<br />
|url=https://service.unece.org/trade/untdid/d21a/trsd/trsdi1.htm<br />
|title=EDIFACT Index of segments by alphabetical sequence by tag (revision 21a) <br />
}}<br />
while in ANSI X12 it's two or three alpha-numeric characters<br />
{{cite web<br />
|url=https://www.gs1ca.org/files/4010segs.pdf<br />
|title=ASC X12 Segment Directory<br />
}}<br />
<br />
== Links ==<br />
<br />
* [https://en.wikipedia.org/wiki/ASC_X12 ANSI ASC X12 (Accredited Standards Committee)]<br />
* [https://en.wikipedia.org/wiki/EDIFACT United Nations/Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT)]<br />
* [https://unece.org/trade/uncefact/xml-schemas EDIFACT XML Schemas]<br />
* [https://en.wikipedia.org/wiki/TRADACOMS TRADACOMS] - Largely obsolete. Primarily used for UK retail. <br />
* [https://www.hamburgsud-line.com/liner/media/hamburg_sud_liner_shipping/ecommerce/edi_api/message_implementation_guides/X_4010_315_HSDG_v1.1.1.pdf Hamburg Sud - 315 Message] - Example EDI Implementation Guide for X12 315 (Ocean Status) <br />
* [https://github.com/notpeter/edicat edicat] - Python tool to print and transform EDI.<br />
<br />
<br />
==References==<br />
{{reflist}}</div>Notpeterhttp://fileformats.archiveteam.org/wiki/Fractal_Image_FormatFractal Image Format2021-11-10T20:38:03Z<p>Notpeter: More details about Iterated Systems, FIF. Note MS Encarta usage.</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Graphics<br />
|extensions={{ext|fif}}<br />
|pronom={{PRONOM|x-fmt/320}}<br />
}}<br />
'''FIF''' ('''Fractal Image Format''') is a raster image format that uses lossy [[fractal compression]]. It is apparently a proprietary format developed by Iterated Systems.<br />
<br />
== Identification ==<br />
Some FIF files begin with bytes <code>'F' 'I' 'F' 0x01</code>.<br />
<br />
[http://cd.textfiles.com/wthreepack/wthreepack-1/COMPRESS/FIFDEMO.ZIP This demo] includes FIF files that begin with "{{magic|FTC}}".<br />
<br />
== Software ==<br />
* [[Konvertor]]<br />
* [[XnView]]<br />
* [[Wikipedia:Genuine Fractals|Genuine Fractals]] Photoshop plug-in<br />
* Microsoft Encarta Encyclopedia licensed FIF for image compression.<br />
<br />
== Sample files ==<br />
* http://users.senet.com.au/~mjbone/Fractals.html → [http://users.senet.com.au/~mjbone/River.fif River.fif]<br />
* https://telparia.com/fileFormatSamples/image/fractalImageFormat/<br />
<br />
== Links ==<br />
* [[Wikipedia:Fractal compression|Wikipedia: Fractal compression]]<br />
* [https://web.archive.org/web/19980626190724/http://www.iterated.com/products/fractalviewer.htm Archived web page about discontinued Fractal Imager and Fractal Viewer products]<br />
* [https://www.bizjournals.com/atlanta/stories/1999/04/12/focus11.html Atlanta Journal Article about Iterated Systems] (1999-04-12)<br />
* [https://web.archive.org/web/19971210205745/http://www.sigmaxi.org:80/amsci/issues/Sciobs96/Sciobs96-09image.html Fractal Image Compression, American Scientist] (1996 Sept-Oct issue)<br />
* [https://web.archive.org/web/20160831070652/http://www.mathaware.org/mam/98/articles/theme.essay.html#Fractals Mathematics Awareness Week - April 1998] - High-level explanation of technology behind the format.</div>Notpeterhttp://fileformats.archiveteam.org/wiki/NMEANMEA2019-08-08T20:57:01Z<p>Notpeter: Initial NMEA page.</p>
<hr />
<div>{{FormatInfo<br />
|formattype=electronic<br />
|subcat=Geospatial<br />
|released=1983<br />
}}<br />
<br />
<br />
NMEA 0183 is an ASCII based streaming format supporting both vendor agnostic and vendor-proprietary data type. It was created by the [https://www.nmea.org/ National Marine Electronics Association] for communication of geospatial and marine data between multiple marine avionics devices.<br />
<br />
Persistent logging of NMEA messages to files is done in multiple file formats, often with an additional timestamp when the message was received.<br />
<br />
== Structure ==<br />
<br />
A stream of NMEA data is a series of line-break delimited 7bit safe ASCII "sentences" with comma delimited fields. Each sentences begins with a '$' character followed by five upper-case characters specifying the "data type" of sentence which follows. Each sentence is trailed by a '*' and two characters which comprise a [https://rietman.wordpress.com/2008/09/25/how-to-calculate-the-nmea-checksum/ NMEA 0183 data integrity checksum]. This checksum is calculated simple XOR of all the individual bytes of the sentence excluding the initial character (usually '!' or '$') and the last three characters ('*' and the checksum characters). <br />
<br />
Examples:<br />
<pre><br />
$GPGSV,2,1,08,01,40,083,46,02,17,308,41,12,07,344,39,14,22,228,45*75<br />
!AIVDM,1,1,,B,177KQJ5000G?tO`K>RA1wUbN0TKH,0*5C<br />
</pre><br />
<br />
== Data types ==<br />
<br />
There are hundreds of different data types which have been implemented over NMEA 0183. Official NMEA documentation is only available by purchasing copies of the copyrighted NMEA 0183 standard. (pricing starting $1000). As a result there is a proliferation of reverse engineered documentation for common standard data types (AIS, GPS, etc) but these, even in aggregate, are from comprehensive for the more obscure data types. <br />
<br />
Each data type begins with one of 80+ [https://www.nmea.org/Assets/20190303%20nmea%200183%20talker%20identifier%20mnemonics.pdf two-letter talker identifier mnemonics]. For example GPS information begin with 'GP' such as the GPGSV (satellites in view) while mobile AIS device messages begin with the 'AI' prefix (e.g. AIVDM 'Received Data from other vessel') with examples above.<br />
<br />
== Link layer ==<br />
<br />
Each NMEA bus supports one or multiple listeners subscribed to data streams from a single "talker" sending data. NMEA 0183 uses a serial data link layer traditionally done at at 4800bps (RS232 4800 baud 1 start bit, 1 stop bit and No Parity) while NMEA 0183 added NMEA 0183-HS (High Speed) supports 38400baud as well. NMEA 2000 uses Ethernet connected devices instead of Serial.<br />
<br />
Modern network/internet implementations providing streaming NMEA data support sending over TCP and/or UDP connections, usually with each sentence sentence sent as a single TCP or UDP packet.<br />
<br />
== Links ==<br />
* [https://web.archive.org/web/20060312045429/http://vancouver-webpages.com/peter/nmeafaq.txt NMEA FAQ]<br />
* [https://web.archive.org/web/20060117162246/http://vancouver-webpages.com/pub/peter/nmeatype.txt NMEA Types]<br />
* [https://gpsd.gitlab.io/gpsd/AIVDM.html Eric S Raymonds AIS Documention]<br />
* [http://aprs.gids.nl/nmea/ http://aprs.gids.nl/nmea/]<br />
* [https://en.wikipedia.org/wiki/NMEA_0183 Wikipedia NMEA 0183]<br />
* [https://en.wikipedia.org/wiki/NMEA_2000 Wikipedia NMEA 2000]<br />
* [https://www.gpsinformation.org/dale/nmea.htm Dale DePriest's GPS Data]<br />
<br />
[[Category:Geospatial]]</div>Notpeter Warning: Cannot modify header information - headers already sent by (output started at /usr/local/www/mediawiki/includes/WebStart.php:100) in /usr/local/www/mediawiki/includes/WebResponse.php on line 38