- need a set and increment to load points

- multiple conversions require temporary output storage!
	- handling of UTM to UTM conversion

- giskit improvements
	- CoordTranslator class to handle MathCoord to MapCoord
		- only one instance per CoordTranslator class/subclass required
	- add constants support to MathConverter
		- read pose matrix stuff
	- I could hash the methods somehow so I could go straight to the
	  applicable ones rather than first trying self and then searching
	  the subcontractor list. Would be a considerable speedup.
	- if a transform fails, should another one be selected and tried?
		- this could get very AI'ish!
		- what if multiple transforms are available?
		- what if a set of transforms could handle a job
		  for which there is no single one available?
			- GPS-like goal seeking behavior?
	- could new services be added to existing classes at runtime?
	- pattern match might require another standard class type, very much
	  on the order of a description of each service that can be provided
	  and that relates to information extracted for a job description
		- the sameConstants check belongs here
		- dimensions could be part pattern match
			- can we handle src and dst with different dimensions?
			- starts looking like my research at QUB!
		- npoints could be part of match
			- large npoints changes economics, could send to a
			  supercomputer or network of machines
			- could do image warping, ie photo to globe, to plane.
			- cost/unit and transaction overhead costs could be
			  way to prevent the first match from always getting 
			  the job

Note by Don:  I Misc-ized the code, but as I went through I noticed that
lots of things should be cleaned up.  In particular, +initialize methods
should be checking the [self class] before doing their thing, etc.