Saving WREGISTER database?
aoxsic wrote on Sep 16, 2008
Hello,
is it possible to save the transformations database that wregister creates while it runs? It seems to unnecessarily clean up after itself but I need that database to apply it on coordinate lists with geoxytran. So, how do I save the database?
Thank you for your time and help.
is it possible to save the transformations database that wregister creates while it runs? It seems to unnecessarily clean up after itself but I need that database to apply it on coordinate lists with geoxytran. So, how do I save the database?
Thank you for your time and help.
aoxsic wrote on Sep 16, 2008
Ok, I found where in the source code this is actually done:
# Delete the database file.
delete (tdatabase, go_ahead+, verify-, default_action+,
allversions+, subfiles+, > "dev$null")
It's this "tdatabase" that I want. Why would you delete it on purpose? How do I get around that if I don't have root rights to edit the file? Is there any procedure that transforms xy pixel coordinate lists using the wcs in the header?
Thanks.
# Delete the database file.
delete (tdatabase, go_ahead+, verify-, default_action+,
allversions+, subfiles+, > "dev$null")
It's this "tdatabase" that I want. Why would you delete it on purpose? How do I get around that if I don't have root rights to edit the file? Is there any procedure that transforms xy pixel coordinate lists using the wcs in the header?
Thanks.
Mike Fitzpatrick wrote on Sep 16, 2008
As written, there is no way in the task to save the database (it was viewed as being only temporary). If you want to keep it you'll need to create a modified version of the script, e.g.
When you run the new MYWREGISTER task it will be the version with your changes. Note that if you plan to re-use the same file you may need to set the 'clobber' environment variable so the file will be overwritten, otherwise a good strategy is to make the database name a parameter you can reset.
Cheers,
-Mike
cl> copy immatch$wregister.cl home$mywregister.cl
cl> edit home$mywregister.cl
.....comment out/delete the line that removes the database file
cl> task mywregister = home$mywregister.cl
When you run the new MYWREGISTER task it will be the version with your changes. Note that if you plan to re-use the same file you may need to set the 'clobber' environment variable so the file will be overwritten, otherwise a good strategy is to make the database name a parameter you can reset.
Cheers,
-Mike
Last post on Sep 16, 2008