Using with ofVec3d and ofVec2d causes issues

[a2hill]

I'm using this on a project which makes use of the ofVec3d, ofVec2d, etc. classes that you wrote for ofxGeo (I'm not actually using the whole addon, just those classes). Line 37 and 38 of Types.h cause a redefinition error for ofVec3d and ofVec2d as a result.

I went ahead and commented out the typedefs, included the respective headers, and patched bit's of the code that were giving me issues. I haven't made extensive use of the addon yet so I can't say how effective my patch is, but it seems to be working. I was going to make a pull request in case you were interested, but I'd have to also include ofVec4d, ofVec3d and ofVec2d from your other repo and I wasn't sure if you really wanted two different copies of those floating around.

If you want the patch I'd be happy to make a pull request with the needed files, if not I just figured I'd give you a heads up.

[bakercp]

Hey there, thanks for checking this out. The reason I had to use double instead of float (ofVec2f) is because a float is not precise enough for very precise global positioning ... it might work for your application though, depending on what resolution you need.

[a2hill]

I'm trying to do meter accuracy (GPS is only so accurate) and so far everything seems to be working fine using the ofVec2d, ofVec3d, and ofVec4d classes from your ofxGeo repo.