Make rasgeo report wrong command line inputs

[Marcus Sen]

I have found a couple of occasions where I enter the wrong command-line options for rasimport and get either a non-obvious error message or a silent ignore of the erroneous option. I think it would be more helpful to fail and give the usage message if incorrect options are specified on the command line.

Ex. 1

$ rasimport -coll bgs_rs -t RGBImage:RGBSet --crs-uri http://www.opengis.net/def/crs/EPSG/0/27700 -f Landsat_ETM_321_11Sep2002.tif

gives error:

rasimport::main(): Parsing error: Unexpected end of query.

because I mistyped —coll as -coll.

Ex. 2

$ rasimport --coll bgs_rs --coverage bgs_rs --crs-uri  http://www.opengis.net/def/crs/EPSG/0/27700 -t RGBImage:RGBSet -f Landsat_ETM_321_11Sep2002.tif

loaded the data with no error message but made the coverage name in petascope bgs_rs_5134 (i.e. with the oid appended to the collection name) rather than bgs_rs as I had intended because I had just typed —coverage instead of the full option name —coverage-name. If the command isn't going to accept shortened unique option names then it should give an error about an unrecognised option rather than silently ignoring it.

[abeccati]

Just triaging it to rasgeo developer