<p dir="ltr">Hi,</p>
<p dir="ltr">The problem with gdal_merge seems to be with the input parameters I used to deflate the file. Locks at 4GB file size.<br>
Cheers</p>
<p dir="ltr">Nicolas Cadieux M.Sc.<br>
Les Entreprises Archéotec inc. <br>
8548, rue Saint-Denis Montréal H2P 2H2<br>
Téléphone: 514.381.5112 Fax: 514.381.4995<br>
www.archeotec.ca</p>
<div class="gmail_quote">On May 19, 2015 12:01, "Even Rouault-2 [via OSGeo.org] " <<a href="/user/SendEmail.jtp?type=node&node=5206669&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>> wrote:<br type='attribution'><blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le mardi 19 mai 2015 17:58:33, <a href="/user/SendEmail.jtp?type=node&node=5206474&i=0">[hidden email]</a> a écrit :
<br />> Hi,
<br />> It seems that both gdal_contour and gdal_merge in QGIS 2.6 and 2.8 (both
<br />> 64bit windows installs on Windows 7_64) are still in 32 bit. Both stop
<br />> when output files hit 4 194 304KB (.tiff or .shp) Is there a way around
<br />> those limitations?
<br /><br />32 or 64-bit builds should have no influence on the limitation of output files.
<br />A 32-bit build can certainly handle files > 4 GB.
<br /><br />.shp are limited to 2GB due to the format anyway.
<br />.tif might be limited to 4 GB with libtiff 3, but are no longer limited with
<br />libtiff 4 with BIGTIFF enabled.
<br /><br />> Thanks
<br />> Nicolas
<br />> _______________________________________________
<br />> Qgis-user mailing list
<br />> <a href="/user/SendEmail.jtp?type=node&node=5206474&i=1">[hidden email]</a>
<br />> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_top" rel="nofollow" link="external">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br /><br />--
<br />Spatialys - Geospatial professional services
<br /><a href="http://www.spatialys.com" target="_top" rel="nofollow" link="external">http://www.spatialys.com</a><br />_______________________________________________
<br />Qgis-user mailing list
<br /><a href="/user/SendEmail.jtp?type=node&node=5206474&i=2">[hidden email]</a>
<br /><a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_top" rel="nofollow" link="external">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br />
<br />
<br />
<hr noshade="noshade" size="1" />
<div style="color:#444;font:12px 'tahoma' , 'geneva' , 'helvetica' , 'arial' , sans-serif">
<div style="font-weight:bold">If you reply to this email, your message will be added to the discussion below:</div>
<a href="http://osgeo-org.1560.x6.nabble.com/32bit-gdal-gdal-modules-tp5206472p5206474.html" target="_top" rel="nofollow" link="external">http://osgeo-org.1560.x6.nabble.com/32bit-gdal-gdal-modules-tp5206472p5206474.html</a>
</div>
<div style="color:#666;font:11px 'tahoma' , 'geneva' , 'helvetica' , 'arial' , sans-serif;margin-top:0.4em;line-height:1.5em">
To start a new topic under Quantum GIS - User, email ml-node+s1560n4125267h38@n6.nabble.com <br />
To unsubscribe from Quantum GIS - User, <a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4125267&code=bmljb2xhcy5jYWRpZXV4QGFyY2hlb3RlYy5jYXw0MTI1MjY3fDYzNDQ4MjQxNg==">click here</a>.<br />
<a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" style="font:9px serif">NAML</a>
</div></blockquote></div>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/32bit-gdal-gdal-modules-tp5206472p5206669.html">Re: 32bit gdal gdal modules</a><br/>
Sent from the <a href="http://osgeo-org.1560.x6.nabble.com/Quantum-GIS-User-f4125267.html">Quantum GIS - User mailing list archive</a> at Nabble.com.<br/>