Add LCC parameter reference to pyproj page.

diff --git a/posts/pyproj.mdwn b/posts/pyproj.mdwn
index 5c1ebb537c50b9cab21ee7264d780a65bd2beed1..592baaff33f85069f90b95b8e7318f6956f3dd0f 100644 (file)
--- a/posts/pyproj.mdwn
+++ b/posts/pyproj.mdwn
@@ -64,7 +64,8 @@ reference ellipsoid for the lat/lng coordinates.  The other
 coordinates are LCC parameters that select the [AWIPS 221][awips221]
 and [AWIPS 226][awips226] projections respectively (`lat_1`
 corresponds to `Latin1`, `lat_2` corresponds to `Latin2`, and `lon_0`
-corresponds to `Lov`).
+corresponds to `Lov`; see [this description][lcc-param] of the
+two-standard-parallel LCC and its PROJ.4 parameters).
 
 Convert our lat/lng pairs into grid points:
 
@@ -150,6 +151,7 @@ conversions, [GeographicLib][] looks promising.
 [LCC]: http://en.wikipedia.org/wiki/Lambert_conformal_conic_projection
 [awips221]: http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html#GRID221
 [awips226]: http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html#GRID218
+[lcc-param]: http://www.remotesensing.org/geotiff/proj_list/lambert_conic_conformal_2sp.html
 [UTM]: http://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system
 [zone]: http://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system#UTM_zone
 [geopy]: http://code.google.com/p/geopy/