On Feb 17, 2009, at 4:44 PM, Hamish wrote:
Howard Butler wrote:
One problem I would like some ideas on is how to describe
what is available. Because the SRS handling can be so
different depending on what is available, I think it would
be good for us to allow the user to ask what was activated
at compile time?
like some sort of gdal-config app or just a lib function that
returns an
int "level" code? (or both?) Part of (eg) 'las2las --help' text?
I am just thinking about end-users who had nothing to do with the
compile
and so are at the mercy of READMEs being accurate & aware. e.g. I hope
that the DebianGIS team (or anybody) can officially package liblas for
Debian & Ubuntu users who wouldn't know to check.
fwiw, IMO consistent methodology is the only path to software sanity.
but you can't make everyone happy that way :)
Yes I agree. Debian has the luxury of using GDAL by default, which is
the only sane way this should go. But I can't make GDAL a hard
requirement for libLAS. Another complication is likely to arise when
GDAL in turn starts linking against libLAS, but we'll burn that bridge
when we need to :)
liblas-config is one place you can get this information, but it
doesn't help the person who's coding to decide how to treat the srs.
Thanks for your input.... still chewing on this chewy one.
Howard
_______________________________________________
Liblas-devel mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/liblas-devel
