$ head -1 ~/ocssw/scripts/mk_matchup.py
For macports, the subprocess module should be part of the base python-3.7 installation. You can set
python3to use macports python3.7 by running "
sudo port select python3 python37".
bash-3.2$ head -1 mk_matchup.py
bash-3.2$ python3 --version
bash-3.2$ which python3
In fact, before doing the anaconda installation, I had done exactly what you suggested for the MacPorts install. Before that, python-2.7 (I think) was my default. I don't know enough about python or its installation details to have gotten very far in checking if the subprocess module was there. Now that things are working with the anaconda python, I guess I won't worry about it.
mk_matchup.pydidn't work with macports' python3.7 installed, but then using
mk_matchup.pyis a hack so maybe not worth investigating unless the problem comes up in the future.
As for missing
out_track, at BIO we used SeaDAS 6 to create "along track" images (e.g., storm tracks) which relies heavily on SeaDAS 6 IDL functions. In the long run, ocean colour users will benefit from tools that rely on open GIS tools that are maintained outside the ocean colour community. Extracting values from a georeferenced image along a path is a common problem, so there are many partial solutions, but in the past these suffered from lack of standards for representing paths and/or requirements that images be in a particular format, and were often implemented in proprietary GIS systems. I'm searching for existing open GIS tools that can provide the low-level functions needed for "along track" images or "out_track" extractions. ESRI How to Extract Raster Values at Point Locations describes some use cases in a way that applies to generic GIS systems. The "Simple Feature Access Standard (ISO 19125)" should become widely supported. A couple years ago I experimented with this in R (the first entry in the Wikipedia list of implementations), but ran into space and performance problems because each point was stored as a structure much larger than needed for a (lon,lat) value. Implementations should improve in time.
I am doing very well in retirement, particularly with not having to limit outdoor activities to evenings and weekends -- with weather radar I get to time bike rides and dog walks between showers.
I couldn't agree more with you about open-source solutions. I'm not much of a GIS person, but I was planning on trying to duplicate out_track in R. I definitely will be checking the ISO19125 document.
Glad to hear that retirement is going well. I'm sort of half-retired and do seem to spend a lot of time walking the dogs and, given the wet spring/summer we've had here in the midwest, dodging the rain. As always, thanks very much for sharing your experience and insights.