No more of a loaded footgun than trying to do it manually, I don't think. Geographic points should probably be represented as a labeled structure to prevent co

No more of a loaded footgun than trying to do it manually, I don't think. Geographic points should probably be represented as a labeled structure to prevent confusion and passed into functions as such. Using two separate libraries with mutually incompatible error-prone APIs as described is the real loaded footgun IMO. If you can't find better libraries, write wrappers; if you don't have time to write/maintain wrappers, pray. Anything else is just a bandaid.