Insert a latitude/longitude range check before PP routines

[BecCowley]

When running the magneticDeclinationPP, the geomag70 code failed because I had lat and long in the wrong fields in the database csv files (longitude in latitude field and latitude in longitude field). There is no error message when the geomag70 code fails, the toolbox just hangs forever.

It would be nice to check the logic of the input arguments before the geomag70 code is run.

[ocehugo]

Thanks.

I think the right way is to validate the database when reading but argument validation before a mex function call should also be done to avoid the lock/hang.

Requirements:

• [ ] validate database longitude/latitude entries when reading.
• [ ] validate arguments of geomag70 mex call.