jkalias

@Ralle why do you say that we need offset for vectors? The offset (or origin) is only relevant for points. The updated line is this https://github.com/mathnet/mathnet-spatial/blob/master/src/Spatial/Euclidean/CoordinateSystem.cs#L378. Do you agree?

I understand your objection. However, since this would be a breaking change, we have to postpone it for a major release update.

Hi @cdrnet , Could you please create a todo list similar to [Numerics](https://numerics.mathdotnet.com/Build.html#Creating-a-Release) which someone else than you can process? I'd love to keep the library up to date

Hi, I think this is a good idea. My approach would be to find the best matching plane in terms of least-squares, as described [here](https://math.stackexchange.com/questions/99299/best-fitting-plane-given-a-set-of-points). The condition that we need...

Relates to #216

> I could submit a pull request for this if it sounds like a good idea? Are you still interested in this? Would you like to submit a PR?

@Sockenfresser can you please check the current state of the library? At the time of [writing](https://github.com/mathnet/mathnet-spatial/commit/83ecc8e32afc032356ef94d61968f995b9c64666) the CoordinateSystem type has been refactored and you should see an effect on its...

Unfortunately the changes had to be reverted due to community backlash

You can't translate or scale a `Matrix2D`, this was used for rotations. A better name would be `RotationMatrix2D`.

@rsinnig @JohanLarsson any progress on this?