<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I love FWTools. Still use it quite often. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I wish it was still actively maintained.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Shayne</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> gdal-dev <gdal-dev-bounces@lists.osgeo.org> on behalf of jratike80 <jukka.rahkonen@maanmittauslaitos.fi><br>
<b>Sent:</b> Monday, January 11, 2021 11:55 AM<br>
<b>To:</b> gdal-dev@lists.osgeo.org <gdal-dev@lists.osgeo.org><br>
<b>Subject:</b> [Non-DoD Source] Re: [gdal-dev] Considering drivers removal ?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi,<br>
<br>
The joy of being a Windows user is that it is so easy to use old GDAL<br>
versions if the binaries still happen to be on some dusty backup disk. Even<br>
the FWTools including GDAL 1.7.0 from 2010 seemed to work fine and include<br>
quite a many later removed drivers.<br>
<br>
A few comments about the driver list:<br>
<br>
- There are indeed questions about SVG in gis.stackexchange every now and<br>
then.<br>
- I used LAN a lot when FWTools was young and ERDAS wrote bad GeoTIFFs.<br>
Things are probably changed since that. <br>
- GMT is an active project and some GMT developers appear on this list as<br>
well. Maybe some of them happend to read this and say if GMT ASCII vectors<br>
are still important for GMT. Or otherwise I can ask from the GMT forum.<br>
- GPS Track Maker, as far as I know, is quite popular in Brazil. However,<br>
when I used the software I just used GPX format for data transfer. Are there<br>
any Brazilian GDAL user here to comment?<br>
<br>
When it comes to Windows binaries, there is a very valuable archive in<br>
<a href="https://gisinternals.com/archive.php">https://gisinternals.com/archive.php</a>. It would be pity if it would get lost<br>
some day.<br>
<br>
-Jukka Rahkonen-<br>
<br>
<br>
<br>
Even Rouault-2 wrote<br>
> Hi,<br>
> <br>
> It's not spring yet, but I'm in a mood lately of axing useless things, and<br>
> we <br>
> probably have tons of candidate for that in GDAL, especially in drivers.<br>
> I was going to just axe the DB2 driver<br>
> (<a href="https://github.com/OSGeo/gdal/pull/3366">https://github.com/OSGeo/gdal/pull/3366</a>) but the issue is more general.<br>
> <br>
> Any idea how we can know what is used and what isn't ? A "call-home" <br>
> functionality where we would track driver usage would only be acceptable<br>
> if <br>
> people enable it and have network connectivity, so we won't probably get<br>
> lots <br>
> of feedback. Having a spreadsheet with the driver list and asking people<br>
> to <br>
> fill it would probably also receive little feedback. So the idea I had was<br>
> to <br>
> do something like the following in the Open() method of a candidate for <br>
> removal:<br>
> <br>
> GDALDataset* FooDriver::Open( .... )<br>
> {<br>
> if( !Identify(poOpenInfo) )<br>
> return nullptr;<br>
> <br>
> if( !CPLTestBool(CPLGetConfigOption("GDAL_ENABLE_DRIVER_FOO", "NO") )<br>
> {<br>
> CPLError(CE_Failure, CPLE_AppDefined,<br>
> "Driver FOO is considered for removal in GDAL 3.5. You are invited "<br>
> "to convert any dataset in that format to another more common one ."<br>
> "If you need this driver in future GDAL versions, create a ticket at "<br>
> "<a href=""></a>https://github.com/OSGeo/gdal (look first for an existing one first)<br>
> to "<br>
> "explain how critical it is for you (but the GDAL project may still "<br>
> "remove it), and to enable it now, set the GDAL_ENABLE_DRIVER_FOO "<br>
> "configuration option / environment variable to YES");<br>
> return nullptr;<br>
> }<br>
> ...<br>
> }<br>
> <br>
> That is, when we detect a file to be handled by the driver, emit the above <br>
> error message and do not open the dataset, unless the user defines the <br>
> environment variable.<br>
> Similarly in the Create()/CreateCopy() methods.<br>
> If we ship this in 3.3, with a 3.5 milestone for removal, this would offer<br>
> a <br>
> feedback period of one year / 2 feature versions.<br>
> <br>
> Here's my own list of candidates for retirement (probably<br>
> over-conservative). <br>
> Mostly based on gut feeling. None of them are particularly bad citizens,<br>
> but I <br>
> have no indication that they are still used, which doesn't mean they<br>
> aren't.<br>
> <br>
> * Raster side:<br>
> BPG<br>
> DB2Raster<br>
> DOQ1<br>
> DOQ2<br>
> E00GRID<br>
> Epsilon<br>
> FujiBAS<br>
> GS7BG<br>
> GSAG<br>
> IDA<br>
> JDEM<br>
> JPEG2000 (Jasper): JP2OpenJPEG is a better replacement<br>
> JPEGLS<br>
> LAN<br>
> MFF<br>
> MG4Lidar ?<br>
> NDF<br>
> NTv1<br>
> SDTS Raster<br>
> SGI<br>
> XPM<br>
> ZMap<br>
> <br>
> * Vector side:<br>
> AERONAVFAA<br>
> ESRI ArcObjects<br>
> ARCGEN<br>
> BNA<br>
> Cloudant<br>
> CouchDB<br>
> DB2<br>
> DODS<br>
> FMEObjects Gateway<br>
> Geomedia MDB<br>
> GMT ASCII Vectors<br>
> GTM<br>
> HTF<br>
> INGRES<br>
> MongoDB (the old one, superseded by MongoDBv3)<br>
> OpenAIR<br>
> REC<br>
> SDTS<br>
> SUA<br>
> SVG<br>
> TIGER<br>
> WALK<br>
> <br>
> <br>
> Anything you'd add / remove ?<br>
> <br>
> What is not obvious is what would be the criterion for keeping a driver:<br>
> 1, <br>
> 10, 100 users asking for the driver to be kept ?<br>
> If a GDAL developer contributing to the overall good of the project needs<br>
> the <br>
> preservation of a driver to be able to justify its continued involvement,<br>
> I'd <br>
> tend to think it to be enough to keep it.<br>
> <br>
> <br>
> Even<br>
> <br>
> -- <br>
> Spatialys - Geospatial professional services<br>
> <a href="http://www.spatialys.com">http://www.spatialys.com</a><br>
> _______________________________________________<br>
> gdal-dev mailing list<br>
<br>
> gdal-dev@.osgeo<br>
<br>
> <a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a href="http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html">http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html</a><br>
_______________________________________________<br>
gdal-dev mailing list<br>
gdal-dev@lists.osgeo.org<br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</div>
</span></font></div>
</body>
</html>