This PR forces one UTM zone number for a given network, so as to avoid issues where deployments span multiple UTM zones. Closes #68 (see that issue for a good example of a multiple-UTM-zone-spanning deployment!).
Also see 0d100ea142fa4200579a21da8169eaeec42b7b20, which was a commit that fixed this for plotting.
This PR forces one UTM zone number for a given network, so as to avoid issues where deployments span multiple UTM zones. Closes #68 (see that issue for a good example of a multiple-UTM-zone-spanning deployment!).
Also see 0d100ea142fa4200579a21da8169eaeec42b7b20, which was a commit that fixed this for plotting.