But probably implies local adjustments?  That would explain some
  discrepancies in scale I am seeing.  In theory I should have 5 meters
  per pixel but end up having to say 7 for a better match.

  All these local adjustments will render my automation quite difficult.
  Ideally, I would like to cover an area that is roughly 250km x

So probably viking converts lat/lon to UTM, and then just uses the
georef map as if it is the right zone.

I think what you need to do is to find the upper left pixel in WGS84

Check out the following program - probably viking should use it at some
point, but it's the standard approach to coordinate conversion in the
open source world:


Attachment: pgphE0QtBmJ7G.pgp
Description: PGP signature

What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
Viking-devel mailing list
Viking home page: http://viking.sf.net/

Reply via email to