a few of you have inquired over the past weeks whatever happened to my
bid for the ASPRS LAS Validation Suite. It's been ... aehhhm ...
funny. I received a serious and professional looking letter marked
"business confidential" that said that I was selected to do the work
... but only on the precondition that I sign a document that more or
less said that I would only be able to talk about the development via
an official ASPRS channel. Why was that funny? Well, if you read my
bid then you know that at its very core was the intention to do the
entire development in an open and transparent manner that would invite
early and frequent community feedback. So it is still a mystery to me
why my bid was selected in the first place. Zähneknirschend (fig.
German) I decided to sign the "silencer" ... I was worried that the
alternative might be worse. The next funny thing was that the ASPRS
LAS committee members did not seem informed about all this. Instead a
"secret" technical review panel was deciding things. But the funniest
thing was that a couple of weeks after me signing the dreaded
"silencer" I was told that the ASPRS was canning whole project.
Shortly thereafter the ASPRS Executive Director announced his
retirement and I personally like to think - just because it makes it
even funnier - that this was somehow related to the LAS Validation
Suite contract fiasko ... (-;
Okay. Enough funny. Now serious. I have sunk many hours into this
project and would like to complete its development in open souce. The
main thing that is lacking for completion is the CRSscan library for
the GeoTIFF versus OCG WKT validation. I was thinking just calling the
right functions of GTIFF and GDAL could do this. I looked through
Frank Wanderdam's code and it seems fairly straight forward. To keep
the tool nice and small - like the original ASPRS LVS tender was
calling for - it would be nice to "rip" only those parts out of GTIFF
and GDAL that are needed to read the Geokey projection tags and the
OCG WKT string. We would then initialize a projection once from the
Geokey tags and once from the OGC WKT string and make sure they are
the same. For the time being I'd be happy if we support 98% (?!?) of
all cases by focusing on the most common projections such as UTM,
generic TM, generic LCC, generic OM, stateplanes, and latlong.
I just updated the github repository with all the necessary source
code to compile the current version of lasvalidate.exe (the LINUX
Makefile are untested and may still have a few errors).
PS: Would be great to have some agency / company / institute funding the effort.
- fast tools for all you LiDARs