<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Paul - <br>
</p>
<p>It's maybe not pertinent to case but I tried to export a
Postgres-based layer to both the MapInfo MIF and Tab file-formats
and showing the layers afterwards in QGIS - but using QGIS v. <b>3.22</b>
on Windows 10. It worked perfectly. <br>
</p>
<p>I checked the first part of the generated MIF text file. It
looked fine and contained all the necessary parts in the header :
version info, projection info and data structure info.<br>
</p>
<p>Regarding your MapInfo error when reading MIF/MID: It is
probably caused by the MIF-file is missing "Version 300" as the
first line - causing the MapInfo interpreter to look after it
until it find the first "Region" definition in the file (MapInfo
speak for polygon). Why, I don't know... But QGIS v. 3.16 is a
strange beast. <br>
</p>
<p>Did you check if the projection was correctly set in the "Save
features as" dialog before exporting the data ? <br>
</p>
<p> <br>
</p>
<pre class="moz-signature" cols="72">Med venlig hilsen / Kind regards
Bo Victor Thomsen</pre>
<div class="moz-cite-prefix">Den 01-12-2021 kl. 18:04 skrev Paul
Wittle:<br>
</div>
<blockquote type="cite"
cite="mid:LO2P265MB32314DFE3532DB04371F9B46C1689@LO2P265MB3231.GBRP265.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve tried exporting to MIF instead of a
tab file and it generates an error of “Found [region] while
searching for [version]” when you try to load it into the
MapInfo. The output is also creating an error when QGIS tries
to load the data as well although I’m not sure if QGIS could
ever directly load MIF files. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The main issue is that if you save to TAB
and select “Add saved file to map” it draws in a different
place. This feels a bit wrong to me.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In any case we are trying to get people to
upgrade to the latest version of MapInfo so GeoPackage is
supported. I will just advise our users to export to
GeoPackage instead and use that as the main data sharing
format instead.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for all the tips and suggestions
though.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Paul<o:p></o:p></p>
</div>
This e-mail and any files transmitted with it are intended solely
for the use of the individual or entity to whom they are
addressed. It may contain unclassified but sensitive or
protectively marked material and should be handled accordingly.
Unless you are the named addressee (or authorised to receive it
for the addressee) you may not copy or use it, or disclose it to
anyone else. If you have received this transmission in error
please notify the sender immediately. All traffic may be subject
to recording and/or monitoring in accordance with relevant
legislation. Any views expressed in this message are those of the
individual sender, except where the sender specifies and with
authority, states them to be the views of Dorset Council. Dorset
Council does not accept service of documents by fax or other
electronic means. Virus checking: Whilst all reasonable steps have
been taken to ensure that this electronic communication and its
attachments whether encoded, encrypted or otherwise supplied are
free from computer viruses, Dorset Council accepts no liability in
respect of any loss, cost, damage or expense suffered as a result
of accessing this message or any of its attachments. For
information on how Dorset Council processes your information,
please see <a class="moz-txt-link-abbreviated" href="http://www.dorsetcouncil.gov.uk/data-protection">www.dorsetcouncil.gov.uk/data-protection</a>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
</pre>
</blockquote>
</body>
</html>