Andy Ferris

So phi is "backwards", more or less? Is this pretty much universal, or just the convention wikipedia has chosen?

Yes, it might be a mistake.

I just checked; all my physics and maths textbooks use what wikipedia calls the "ISO" standard. I'd suggest we change to that and add a picture to the README. :)...

I'm wondering if our earlier attempt at having `AbstactAffineTransformation` as an interface and a set of abstract types (or perhaps traits?) would let us resolve this.

Hmmm... interesting. The `call` function can be achieved as a `ComposedTransformation` already - the trick here is the `compose` implementation. `IntermediateType` is rather interesting... it doesn't _necessarily_ have to be...

Sorry... how does `PointCoord` work? Is this like `PointCoord{UTM}` or something? Or ``` julia immutable PointCoord{T

Ah, yes, *CoordinateTransformations.jl* is **definitely** designed to be one piece of the puzzle for people doing calibrations, SLAM, etc. (This was precisely the kind of problem we were thinking of...

Can you put methods on (instances of) abstract types now? I thought that was a no-go? Generally yes we should probably only support `AbstractVector` out of the box for `LinearMap`...

Oh right - I had forgotten! Well, adding call overloads to `Transform`s was definitely a wanted feature since in the first version of this package. I’d say tighten our built-in...

My favourite way to deal with such approximations is to avoid them by making such transforms lazy, and you can still determine predicates like `point in transform(object)` by dispatching that...