Rasql_removes /tmp/rasdaman.*.aux.xml after encoding result is done

[Bang Pham Huu]

When encoding to PNG, TIFF,…it creates the file .aux.xml in /tmp folder, e.g with this query

SELECT encode(c, "png" , 
"{\"metadata\":{\"resolution\":\"1\"},\"nilValues\":[{\"value\":\"119\"},{\"value\":\"208\"},
{\"value\":\"248\"}],\"nodata\":[119,208,248]}") 
FROM test_rgb AS c

and a file in /tmp/rasdaman.Ix3L0K.aux.xml is created with this content:

<PAMDataset>
  <Metadata>
    <MDI key="NODATA_VALUES">119 208 248</MDI>
    <MDI key="resolution">1</MDI>
  </Metadata>
  <Metadata domain="IMAGE_STRUCTURE">
    <MDI key="INTERLEAVE">PIXEL</MDI>
  </Metadata>
</PAMDataset>

# Also need to clean up
In case of encoding big collection in netCDF and server is crashed, it will leave a binary file (e.g: /tmp/rasdaman.4dA5yA with 466 MB). To reproduce, encode a big collection in netCDF from WCPS and when it is running, stop_rasdaman.sh.

[Peter Baumann]

further, file .aux.xml should (i) not be hidden and (ii) have a name indicating that rasdaman is originator. This eases housekeeping by the machine's admin.