Kirk, I have no strong objection, but I'm not sure what the advantage is. Could you explain the rationale for it ? As far as I can see, MrSID and MG4Lidar drivers don't share any common code. And I have the feeling that trying to fold them can potentially lead to issues with the build system due to their dependency on separate libraries.
The MrSID and JP2MrSID drivers are indeed folded in the same "driver", but they share a lot of code and both depend on the same third-party lib. With the MG4Lidar driver, it is different since it links with another lib. Or is this move done in the context of the GeoExpress v8.0 SDK that if I understand well can read both raster and lidar files ? If so, will the MG4Lidar driver require GeoExpress v8.0 SDK or could it be used with the separate LiDAR SDK 1.1 ? /me a bit confused by all those libraries ;-) Ah, and what is the timetable objective ? For GDAL 1.8.0 or 1.9.0 ? If for GDAL 1.8.0, the move should be done pretty quickly as the plan was to cut off a first beta very soon. Best regards, Even _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev