Changeset 108
- Timestamp:
- 11/19/05 13:25:23
- Files:
-
- PCL/tags/rel-0.9.1/CHANGES.txt (modified) (2 diffs)
- PCL/tags/rel-0.9.1/HISTORY.txt (modified) (1 diff)
- PCL/tags/rel-0.9.1/referencing/README.txt (modified) (2 diffs)
- PCL/tags/rel-0.9.1/VERSION.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
PCL/tags/rel-0.9.1/CHANGES.txt
r107 r108 2 2 ======= 3 3 4 All issues refer to the PCL/ZCO/PrimaGIStracker4 All tickets refer to the new tracker 5 5 6 http:// zcologia.org:8900/primagis/6 http://trac.gispython.org/projects/PCL/ 7 7 8 8 9 0.9.0: 24 August 2005 10 --------------------- 11 - Initial implementation of PgFeatureStore. Works much like the 12 DiskFeatureStore in that the connection string can be handed off to the 13 MapServer engine for efficient backend rendering, or we can use the PCL 14 filter feature iterator (issue 36). 15 - Finer output format control, including 24-bit PNG (issue 51). 16 - Added type() to IGeometry and datatype() to IDataStore, and all 17 implementations. 18 - Simplified testing framework and the testing process. Tests can be run in 19 place without using the distutils setup script. 20 - Configuration of local raster and feature data spatial referencing is now 21 done in the filesystem, not within Zope, with the use of XML files for GDAL 22 and OGR. For PostGIS, spatial reference is determined from the database 23 (issue 69). 24 - Reorganized the PCL data module, turning it into a sub-package of 25 cartography with disk, OWS, and PostGIS modules (issue 69). 26 - Preliminary WFS data store and source (issue 74). 27 - shpconfig.py tool under utils/ for configuring unprojected shapefiles (issue 28 72). 29 - Requiring ElementTree, cElementTree, or lxml for XML parsing 30 - New documentation of filesystem backends for GIS data at 31 doc/filesystem_backend.txt 32 33 0.9.1: ? 34 ------------------------- 9 0.9.1: 19 November 2005 10 ----------------------- 35 11 - Fixed typo in PostGIS LineString type, patch by jdenisgiguere (issue 81). 36 12 - Auto label angle is now the default for text symbolizers (issue 83). … … 39 15 duplicate labels, and padding between labels can also now be controlled 40 16 (issue 90). 41 17 - New cartography.referencing module can be installed and used independently 18 of the rest of PCL. It depends *only* on the PROJ.4 library (ticket:20). 19 PCL/tags/rel-0.9.1/HISTORY.txt
r107 r108 1 1 HISTORY 2 2 ======= 3 4 0.9.0: 24 August 2005 5 --------------------- 6 - Initial implementation of PgFeatureStore. Works much like the 7 DiskFeatureStore in that the connection string can be handed off to the 8 MapServer engine for efficient backend rendering, or we can use the PCL 9 filter feature iterator (issue 36). 10 - Finer output format control, including 24-bit PNG (issue 51). 11 - Added type() to IGeometry and datatype() to IDataStore, and all 12 implementations. 13 - Simplified testing framework and the testing process. Tests can be run in 14 place without using the distutils setup script. 15 - Configuration of local raster and feature data spatial referencing is now 16 done in the filesystem, not within Zope, with the use of XML files for GDAL 17 and OGR. For PostGIS, spatial reference is determined from the database 18 (issue 69). 19 - Reorganized the PCL data module, turning it into a sub-package of 20 cartography with disk, OWS, and PostGIS modules (issue 69). 21 - Preliminary WFS data store and source (issue 74). 22 - shpconfig.py tool under utils/ for configuring unprojected shapefiles (issue 23 72). 24 - Requiring ElementTree, cElementTree, or lxml for XML parsing 25 - New documentation of filesystem backends for GIS data at 26 doc/filesystem_backend.txt 3 27 4 28 0.8.3: 24 May 2005 PCL/tags/rel-0.9.1/referencing/README.txt
r107 r108 24 24 # =========================================================================== 25 25 26 Installation 27 ------------ 28 26 29 This is the new geo-referencing module from gispython.org. It is a sub-package 27 of PCL, but is also useful on its own . It's only external dependency is on the28 PROJ.4 library30 of PCL, but is also useful on its own as an independent package. It's only 31 external dependency is on the PROJ.4 library 29 32 30 33 http://proj.maptools.org/ 34 35 PROJ.4 is easy to build from source, and is also available in many binary 36 packages. 31 37 32 38 For stand-alone use, follow these instructions … … 36 42 $ sudo python setup.py install 37 43 44 Usage 45 ----- 46 47 The referencing.transform.proj4 module has a ProjTransform class, initialized 48 from two instances of referencing.srs.SpatialReference. One is the source SRS, 49 the other is the destination SRS:: 50 51 t = ProjTransform(destination_srs, source_srs) 52 53 This class has a transform() method which takes a list of X,Y coordinate 54 tuples (see above) and returns another such list:: 55 56 transformed_coords = t.transform(source_coords) 57 58 The order of the parameters goes a bit against the grain if you're accustomed 59 to mapscript and OGR, but I think it makes more sense. Chain it all out like:: 60 61 out_coords = ProjTransform(out_srs, source_srs).transform(source_coords) 62 63 and you see that on the right we have all the sources, and on the left all the 64 outputs. I see it as a built-in hint. 65 66 Here is a working example. Two long/lat points from the WGS84 SRS (EPSG:4326) 67 are transformed to UTM zone 13 coordinates:: 68 69 from cartography.referencing.srs import SpatialReference 70 from cartography.referencing.transform.proj4 import ProjTransform 71 utm13 = SpatialReference(epsg=26913) 72 wgs84 = SpatialReference(epsg=4326) 73 74 # transform _to_ UTM zone 13 _from_ WGS84 75 t = ProjTransform(utm13, wgs84) 76 new_coords = t.transform([(-105, 39), (-106, 40)]) 77 78 # new_coords is 79 # [(499999.99999999889, 4316776.5830979366), 80 # (414639.53815663763, 4428236.0645195534)] 81 82 PCL/tags/rel-0.9.1/VERSION.txt
r107 r108 1 PCL 0.9 1 PCL 0.9.1
