<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 27, 2014 at 3:21 AM, ridgewang <span dir="ltr"><<a href="mailto:ridgewang@gmail.com" target="_blank">ridgewang@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi，<br>
I have 2 suggestions：<br>
1. supply an option that can build the gdal using the static c++ runtime library, so we can use it not depends on the msvcr80.dll and msvcp80.dll.<br>
<br>
2. provide a gdal_merge.exe utility program with the same function as gdal_merge.py.<br></blockquote><div><br></div><div>you can use the gdalwarp utility instead - it works better for me anyway.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
here are the reasons I raise it:<br>
1. I write a COM component using gdal library, but I can not register the component correction, maybe the version in my computer is not right and I donot known how to build a static version not using the vc runtime library.<br>
<br>
2. I do not known how to run the python utility and it always reports cannot find the _gdal module, and I had tried many times and had set the pythonpath environment variance.<br>
<br>
And who can kindly teach me how to solve the first problem. Maybe I can add some switch option to the compile configuration file?<br>
<br>
Ridge<br>
<br>
<br>
<br>
<br>
<br>
<br>
在 2014-3-27，3:00，<a href="mailto:gdal-dev-request@lists.osgeo.org">gdal-dev-request@lists.osgeo.org</a> 写道：<br>
<br>
> Send gdal-dev mailing list submissions to<br>
> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:gdal-dev-request@lists.osgeo.org">gdal-dev-request@lists.osgeo.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:gdal-dev-owner@lists.osgeo.org">gdal-dev-owner@lists.osgeo.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of gdal-dev digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: GDAL 1.11 release plan (Even Rouault)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Wed, 26 Mar 2014 16:16:24 +0100<br>
> From: Even Rouault <<a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>><br>
> To: Olivier BARTHELEMY <<a href="mailto:barthelemy@geovariances.com">barthelemy@geovariances.com</a>><br>
> Cc: <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
> Subject: Re: [gdal-dev] GDAL 1.11 release plan<br>
> Message-ID: <<a href="mailto:1395846984.5332ef48e324c@imp.free.fr">1395846984.5332ef48e324c@imp.free.fr</a>><br>
> Content-Type: text/plain; charset=ISO-8859-15<br>
><br>
> Selon Olivier BARTHELEMY <<a href="mailto:barthelemy@geovariances.com">barthelemy@geovariances.com</a>>:<br>
><br>
> I've fixed the one in adrgdataset.cpp.<br>
> gifalloc.c, degrib18, hdf-eos are third-party code "imported" into GDAL tree. So<br>
> the best way would be to fix the issues upstream (if fix is actually needed) and<br>
> then downstream into GDAL.<br>
> I've analyze errors reported in rasterlitedataset.cpp, ogrdatasource.cpp,<br>
> ogrpgdatasource.cpp and strtod, and they are false positives. So the rate of<br>
> false positives with cppcheck is quite significant.<br>
> I haven't looked at the other files that I'm less familiar with.<br>
><br>
> Even<br>
><br>
>> Here is what cppcheck 1.64 reports as 'errors' in gdal-1.10.1:<br>
>><br>
>> [frmts\adrg\adrgdataset.cpp:1071]: (error) Memory leak: TILEINDEX<br>
>> [frmts\coasp\coasp_dataset.cpp:199]: (error) Undefined behavior: Variable<br>
>> 'pszItemValue' is used as parameter and destination in s[n]printf().<br>
>> [frmts\dted\dted_create.c:181]: (error) Resource leak: fp<br>
>> [frmts\envisat\EnvisatFile.c:286]: (error) Memory leak: self<br>
>> [frmts\envisat\EnvisatFile.c:609]: (error) Memory leak: dsd_text<br>
>> [frmts\envisat\EnvisatFile.c:1776]: (error) Memory leak: entry<br>
>> [frmts\georaster\georaster_dataset.cpp:188]: (error) Possible null pointer<br>
>> dereference: poGRD<br>
>> [frmts\georaster\georaster_dataset.cpp:189]: (error) Possible null pointer<br>
>> dereference: poGRD<br>
>> [frmts\georaster\georaster_dataset.cpp:190]: (error) Possible null pointer<br>
>> dereference: poGRD<br>
>> [frmts\georaster\georaster_dataset.cpp:191]: (error) Possible null pointer<br>
>> dereference: poGRD<br>
>> [frmts\georaster\oci_wrapper.cpp:1590]: (error) Pointer to local array<br>
>> variable returned.<br>
>> [frmts\gif\giflib\gifalloc.c:67]: (error) Memory leak: Object<br>
>> [frmts\grib\degrib18\degrib\clock.c:2071]: (error) Common realloc mistake:<br>
>> 'Stack' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\clock.c:2175]: (error) Common realloc mistake:<br>
>> 'Rel' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\clock.c:2197]: (error) Common realloc mistake:<br>
>> 'Rel' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\clock.c:2209]: (error) Common realloc mistake:<br>
>> 'Rel' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\grib2api.c:594]: (error) Uninitialized<br>
>> variable: igdstmpl<br>
>> [frmts\grib\degrib18\degrib\metaparse.cpp:2628]: (error) Common realloc<br>
>> mistake: 'freq' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:109]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:126]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:132]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:149]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:158]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:187]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:195]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:203]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:211]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:218]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:229]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:241]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:257]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:442]: (error) Common realloc mistake:<br>
>> 'preBuffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myerror.c:534]: (error) Common realloc mistake:<br>
>> 'buff' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myutil.c:85]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myutil.c:92]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myutil.c:99]: (error) Common realloc mistake:<br>
>> 'buffer' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\myutil.c:149]: (error) Common realloc mistake:<br>
>> 'argv' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\tdlpack.cpp:3256]: (error) Common realloc<br>
>> mistake: 'subGroup' nulled but not freed upon failure<br>
>> [frmts\grib\degrib18\degrib\tdlpack.cpp:4179]: (error) Read and write<br>
>> operations without a call to a positioning function (fseek, fsetpos or<br>
>> rewind) or fflush in between result in undefined behaviour.<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\compack.c:159]: (error) Uninitialized<br>
>> variable: ival1<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\comunpack.c:198]: (error) Memory leak:<br>
>> ifld<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\misspack.c:203]: (error) Uninitialized<br>
>> variable: ival1<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\misspack.c:118]: (error) Uninitialized<br>
>> variable: rmisss<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\pngunpack.c:61]: (error) Memory leak: ifld<br>
>> [frmts\grib\degrib18\g2clib-1.0.4\pngunpack.c:61]: (error) Memory leak:<br>
>> ctemp<br>
>> [frmts\hdf4\hdf-eos\EHapi.c:2315]: (error) Common realloc mistake:<br>
>> 'metabuf' nulled but not freed upon failure<br>
>> [frmts\hdf4\hdf-eos\EHapi.c:3665]: (error) Common realloc mistake:<br>
>> 'EHXtypeTable' nulled but not freed upon failure<br>
>> [frmts\hdf4\hdf-eos\EHapi.c:3668]: (error) Common realloc mistake:<br>
>> 'EHXacsTable' nulled but not freed upon failure<br>
>> [frmts\hdf4\hdf-eos\EHapi.c:3671]: (error) Common realloc mistake:<br>
>> 'EHXfidTable' nulled but not freed upon failure<br>
>> [frmts\hdf4\hdf-eos\EHapi.c:3674]: (error) Common realloc mistake:<br>
>> 'EHXsdTable' nulled but not freed upon failure<br>
>> [frmts\hdf4\hdf-eos\GDapi.c:2411]: (error) Array 'HDFcomp[5]' accessed at<br>
>> index 19, which is out of bounds.<br>
>> [frmts\hdf4\hdf-eos\GDapi.c:2177]: (error) Array 'originNames[4]' accessed<br>
>> at index 15, which is out of bounds.<br>
>> [frmts\hdf4\hdf-eos\GDapi.c:2292]: (error) Array 'pixregNames[2]' accessed<br>
>> at index 7, which is out of bounds.<br>
>> [frmts\hdf4\hdf-eos\SWapi.c:4995]: (error) Memory leak: fillbuf<br>
>> [frmts\hdf4\hdf-eos\SWapi.c:5615]: (error) Memory leak: flag<br>
>> [frmts\hdf4\hdf-eos\SWapi.c:6239]: (error) Memory leak: flag<br>
>> [frmts\idrisi\IdrisiDataset.cpp:1886]: (error) syntax error<br>
>> [frmts\ilwis\ilwisdataset.cpp:1425]: (error) syntax error<br>
>> [frmts\msg\msgdataset.cpp:532]: (error) Object pointed by an 'auto_ptr' is<br>
>> destroyed using operator 'delete'. You should not use 'auto_ptr' for<br>
>> pointers obtained with operator 'new[]'.<br>
>> [frmts\netcdf\netcdfdataset.cpp:5997]: (error) Uninitialized variable:<br>
>> strtime<br>
>> [frmts\pcidsk\sdk\core\pcidsk_utils.cpp:644]: (error) Common realloc<br>
>> mistake: 'pszWorkBuffer' nulled but not freed upon failure<br>
>> [frmts\pcidsk\sdk\core\pcidskexception.cpp:170]: (error) Common realloc<br>
>> mistake: 'pszWorkBuffer' nulled but not freed upon failure<br>
>> [frmts\png\libpng\pngrutil.c:996]: (error) Uninitialized variable: igamma<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1179]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1185]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1186]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1187]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1188]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1190]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1191]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1192]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1193]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1194]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1195]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1196]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\rasterlite\rasterlitedataset.cpp:1267]: (error) Possible null<br>
>> pointer dereference: poDS<br>
>> [frmts\raw\atlsci_spheroid.cpp:122]: (error) syntax error<br>
>> [frmts\raw\mffdataset.cpp:1451]: (error) syntax error<br>
>> [frmts\sgi\sgidataset.cpp:523]: (error) Using 'memcpy' on struct that<br>
>> contains a 'std::string'.<br>
>> [ogr\ogrsf_frmts\dgn\dgnhelp.cpp:1379]: (error) syntax error<br>
>> [ogr\ogrsf_frmts\dwg\ogrdwglayer.cpp:323]: (error) Invalid number of<br>
>> character ({) when these macros are defined: 'notdef'.<br>
>> [ogr\ogrsf_frmts\filegdb\FGdbLayer.cpp:1914]: (error) syntax error<br>
>> [ogr\ogrsf_frmts\generic\ogrdatasource.cpp:1425]: (error) Possible null<br>
>> pointer dereference: papoSrcLayers<br>
>> [ogr\ogrsf_frmts\mitab\mitab_coordsys.cpp:747]: (error) Buffer is accessed<br>
>> out of bounds.<br>
>> [ogr\ogrsf_frmts\mitab\mitab_geometry.cpp:223]: (error) Memory leak:<br>
>> xintersect<br>
>> [ogr\ogrsf_frmts\ntf\ntffilereader.cpp:260]: (error) Memory pointed to by<br>
>> 'poRecord' is freed twice.<br>
>> [ogr\ogrsf_frmts\pg\ogrpgdatasource.cpp:1102]: (error) Memory leak: poLayer<br>
>> [ogr\ogrsf_frmts\shape\shptree.c:241]: (error) Memory leak: psTree<br>
>> [port\cpl_minizip_zip.cpp:608]: (error) Memory leak: zi<br>
>> [port\cpl_strtod.cpp:67]: (error) Division by zero.<br>
>><br>
>> I'd be happy to provide fix patches, but i have not much time at the<br>
>> moment, so it won't be before a 1.11 release.<br>
>><br>
>> If you want to see the other 'warnings', and get un updated report on GDAL<br>
>> trunk, maybe you could ask to those who manage<br>
>> <a href="http://debbie.postgis.net:8080/view/GDAL/" target="_blank">http://debbie.postgis.net:8080/view/GDAL/</a> to add the cppcheck plugin to<br>
>> their Jenkins?<br>
>><br>
>><br>
>> 2014-03-26 9:15 GMT+01:00 Even Rouault <<a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>>:<br>
>><br>
>>> Hi Olivier,<br>
>>><br>
>>> If you could share with us the errors that have been reported (and the<br>
>>> options<br>
>>> you have used to pass cppcheck on GDAL source), that would be a good<br>
>>> contribution. Even better if you can submit a patch to fix them ;-)<br>
>>> Not saying they shouldn't be fixed, but I don't see that as a blocker point<br>
>>> however, unless they show up in nominal code paths. They have likely<br>
>>> existed for<br>
>>> years.<br>
>>> We also have registered GDAL to the Coverity scanner, and we try to fix<br>
>>> errors<br>
>>> that are reported in new code.<br>
>>><br>
>>> Even<br>
>>><br>
>>>> I think you should take a look at what cppcheck finds when scanning GDAL<br>
>>>> source before the next release. There are a few tens of small errors.<br>
>>>> Mostly, small leaks in particalr cases. Not very important errors, but<br>
>>> that<br>
>>>> ought to be fixed before doing an release in my opinion<br>
>>>><br>
>>>><br>
>>>> 2014-03-26 8:49 GMT+01:00 Paul Meems <<a href="mailto:bontepaarden@gmail.com">bontepaarden@gmail.com</a>>:<br>
>>>><br>
>>>>> +1 for adding VS2013 binaries in GISInternals<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>><br>
>>>>> Paul<br>
>>>>><br>
>>>>> *Paul Meems *<br>
>>>>> Release manager, configuration manager<br>
>>>>> and forum moderator of MapWindow GIS.<br>
>>>>> <a href="http://www.mapwindow.org" target="_blank">www.mapwindow.org</a><br>
>>>>><br>
>>>>> Owner of MapWindow.nl - Support for<br>
>>>>> Dutch speaking users.<br>
>>>>> <a href="http://www.mapwindow.nl" target="_blank">www.mapwindow.nl</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> *Join us at the MapWindow GIS Conference 2014<br>
>>>>> <<a href="http://geogis.detek.unideb.hu/TKonferencia/2014/" target="_blank">http://geogis.detek.unideb.hu/TKonferencia/2014/</a>>, in Debrecen<br>
>>> Hungary*<br>
>>>>><br>
>>>>><br>
>>>>> 2014-03-26 6:25 GMT+01:00 xavier lhomme <<a href="mailto:lhomme.xavier@gmail.com">lhomme.xavier@gmail.com</a>>:<br>
>>>>><br>
>>>>> Hi<br>
>>>>>> Adding Visual Studio 2012 2013 in GISInternals for Gdal 1.11 should<br>
>>> be<br>
>>>>>> great too.<br>
>>>>>> Xav<br>
>>>>>> Le 25 mars 2014 22:57, "Tamas Szekeres" <<a href="mailto:szekerest@gmail.com">szekerest@gmail.com</a>> a<br>
>>> ?crit :<br>
>>>>>><br>
>>>>>> That sounds good to me.<br>
>>>>>>><br>
>>>>>>> Best regards,<br>
>>>>>>><br>
>>>>>>> Tamas<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> 2014-03-25 22:37 GMT+01:00 Even Rouault <<br>
>>> <a href="mailto:even.rouault@mines-paris.org">even.rouault@mines-paris.org</a>>:<br>
>>>>>>><br>
>>>>>>>> Hi,<br>
>>>>>>>><br>
>>>>>>>> GDAL 1.10 was released about one year ago, so it is time to think<br>
>>> about<br>
>>>>>>>> the next<br>
>>>>>>>> release. I think we should just call it 1.11 given that there are no<br>
>>>>>>>> major<br>
>>>>>>>> architectural changes (although there have been non trivial changes<br>
>>> in<br>
>>>>>>>> RAT<br>
>>>>>>>> management and for multiple geometry field support, but that only<br>
>>>>>>>> impacts core &<br>
>>>>>>>> drivers), and the C API and ABI is still preserved (for those who<br>
>>> have<br>
>>>>>>>> looked at<br>
>>>>>>>> the other thread, my experiments on unification are *not* in trunk).<br>
>>>>>>>> For the<br>
>>>>>>>> details, I have initiated the preliminary NEWS :<br>
>>>>>>>> <a href="http://trac.osgeo.org/gdal/export/27091/trunk/gdal/NEWS" target="_blank">http://trac.osgeo.org/gdal/export/27091/trunk/gdal/NEWS</a> (*)<br>
>>>>>>>> There are some mentions to 2.0 in the documentation of new features,<br>
>>>>>>>> but I'll<br>
>>>>>>>> end up fixing them to reflect the 1.11 numbering.<br>
>>>>>>>><br>
>>>>>>>> I think we are in a good shape to start the beta phase soon. If<br>
>>> people<br>
>>>>>>>> have<br>
>>>>>>>> features or bug fixes almost ready that they'd like to be in 1.11,<br>
>>>>>>>> please speak<br>
>>>>>>>> up now. Otherwise I suggest issuing a beta-1 at the end of next<br>
>>> week,<br>
>>>>>>>> give it a<br>
>>>>>>>> week for testing, and depending on the outcome, issue a beta-2, or<br>
>>> just<br>
>>>>>>>> try<br>
>>>>>>>> RC-1. Unless someone volunteers (the process is fairly well<br>
>>> documented<br>
>>>>>>>> in<br>
>>>>>>>> HOWTO-RELEASE), I can be release manager for 1.11.<br>
>>>>>>>><br>
>>>>>>>> Any opinion about that plan ?<br>
>>>>>>>><br>
>>>>>>>> Best regards,<br>
>>>>>>>><br>
>>>>>>>> Even<br>
>>>>>>>><br>
>>>>>>>> --<br>
>>>>>>>> Geospatial professional services<br>
>>>>>>>> <a href="http://even.rouault.free.fr/services.html" target="_blank">http://even.rouault.free.fr/services.html</a><br>
>>>>>>>> _______________________________________________<br>
>>>>>>>> gdal-dev mailing list<br>
>>>>>>>> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
>>>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> _______________________________________________<br>
>>>>>>> gdal-dev mailing list<br>
>>>>>>> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
>>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> gdal-dev mailing list<br>
>>>>>> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> gdal-dev mailing list<br>
>>>>> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> [image: Geovariances]<br>
>>>><br>
>>>> Olivier BARTHELEMY *Software development engineer*<br>
>>>> Geovariances, 49bis avenue Franklin Roosevelt - 77215 AVON CEDEX - FRANCE<br>
>>>> | <a href="http://www.geovariances.com" target="_blank">www.geovariances.com</a> <<a href="http://link.geovariances.com/eml-home" target="_blank">http://link.geovariances.com/eml-home</a>><br>
>>>> Keep posted about Geovariances <<br>
>>> <a href="http://link.geovariances.com/eml-geowidget" target="_blank">http://link.geovariances.com/eml-geowidget</a>><br>
>>>> <<a href="http://link.geovariances.com/eml-linkedin-gv" target="_blank">http://link.geovariances.com/eml-linkedin-gv</a>><br>
>>>> <<a href="http://link.geovariances.com/eml-linkedin" target="_blank">http://link.geovariances.com/eml-linkedin</a>><br>
>>>> <<a href="http://link.geovariances.com/eml-twitter" target="_blank">http://link.geovariances.com/eml-twitter</a>><br>
>>>> <<a href="http://link.geovariances.com/eml-youtube" target="_blank">http://link.geovariances.com/eml-youtube</a>><br>
>>>> <<a href="http://link.geovariances.com/eml-slideshare" target="_blank">http://link.geovariances.com/eml-slideshare</a>><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> [image: Geovariances]<br>
>><br>
>> Olivier BARTHELEMY *Software development engineer*<br>
>> Geovariances, 49bis avenue Franklin Roosevelt - 77215 AVON CEDEX - FRANCE<br>
>> | <a href="http://www.geovariances.com" target="_blank">www.geovariances.com</a> <<a href="http://link.geovariances.com/eml-home" target="_blank">http://link.geovariances.com/eml-home</a>><br>
>> Keep posted about Geovariances <<a href="http://link.geovariances.com/eml-geowidget" target="_blank">http://link.geovariances.com/eml-geowidget</a>><br>
>> <<a href="http://link.geovariances.com/eml-linkedin-gv" target="_blank">http://link.geovariances.com/eml-linkedin-gv</a>><br>
>> <<a href="http://link.geovariances.com/eml-linkedin" target="_blank">http://link.geovariances.com/eml-linkedin</a>><br>
>> <<a href="http://link.geovariances.com/eml-twitter" target="_blank">http://link.geovariances.com/eml-twitter</a>><br>
>> <<a href="http://link.geovariances.com/eml-youtube" target="_blank">http://link.geovariances.com/eml-youtube</a>><br>
>> <<a href="http://link.geovariances.com/eml-slideshare" target="_blank">http://link.geovariances.com/eml-slideshare</a>><br>
>><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> gdal-dev mailing list<br>
> <a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
><br>
> End of gdal-dev Digest, Vol 118, Issue 58<br>
> *****************************************<br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></blockquote></div><br></div></div>