ZMapServer is a Zope Product that provides a clean interface to theMapServer (http://mapserver.gis.umn.edu) web mapping application.
Be the first to post a text review of ZMapServer. Rate and review a project by clicking thumbs up or thumbs down in the right column.
CHANGES ======= All issues refer to the PCL/ZCO/PrimaGIS tracker http://zcologia.org:8900/primagis/ 0.6.0: 24 August 2005 --------------------- - New ZCO WMS object provides a WMS interface to the MapRenderer. - PostGIS DataStore available. See ZCO/DataStore.py (issue 41). - Implementing specific classes for different types of datastores (issue 69). - New constructors and creation/edit forms for datastores and layers. These provide more detailed instructions and better user feedback. - Factored data store classes into data store and data source classes. A data source is essentially a single shapefile, PostGIS feature table, or WMS layer. Zope users do not manipulate data sources, except through a layer. A data store is a directory of shapefiles, a PostGIS database, or a WMS service (issue 69). We are now longer using implicit acquisition for Data Stores or Layers (issue 53). - Configuration of local raster and feature data spatial referencing is now done in the filesystem, not within Zope, with the use of XML files for GDAL and OGR. For PostGIS, spatial reference is determined from the database (issue 69). - Layers are now more like a DataSource, and in the case of WMS requests are adapted to a new request interface. - Symbolizer creation is improved, and a new edit view has been written, with a nice color picker by Kai (issue 14). - Requires PCL 0.9.
CHANGES ======= All issues refer to the PCL/ZCO/PrimaGIS tracker http://zcologia.org:8900/primagis/ 0.9.0: 24 August 2005 --------------------- - Initial implementation of PgFeatureStore. Works much like the DiskFeatureStore in that the connection string can be handed off to the MapServer engine for efficient backend rendering, or we can use the PCL filter feature iterator (issue 36). - Finer output format control, including 24-bit PNG (issue 51). - Added type() to IGeometry and datatype() to IDataStore, and all implementations. - Simplified testing framework and the testing process. Tests can be run in place without using the distutils setup script. - Configuration of local raster and feature data spatial referencing is now done in the filesystem, not within Zope, with the use of XML files for GDAL and OGR. For PostGIS, spatial reference is determined from the database (issue 69). - Reorganized the PCL data module, turning it into a sub-package of cartography with disk, OWS, and PostGIS modules (issue 69). - Preliminary WFS data store and source (issue 74). - shpconfig.py tool under utils/ for configuring unprojected shapefiles (issue 72). - Requiring ElementTree, cElementTree, or lxml for XML parsing - New documentation of filesystem backends for GIS data at doc/filesystem_backend.txt
CHANGES ======= All issues refer to the PCL/ZCO/PrimaGIS tracker http://zcologia.org:8900/primagis/ 0.9.0: 24 August 2005 --------------------- - Initial implementation of PgFeatureStore. Works much like the DiskFeatureStore in that the connection string can be handed off to the MapServer engine for efficient backend rendering, or we can use the PCL filter feature iterator (issue 36). - Finer output format control, including 24-bit PNG (issue 51). - Added type() to IGeometry and datatype() to IDataStore, and all implementations. - Simplified testing framework and the testing process. Tests can be run in place without using the distutils setup script. - Configuration of local raster and feature data spatial referencing is now done in the filesystem, not within Zope, with the use of XML files for GDAL and OGR. For PostGIS, spatial reference is determined from the database (issue 69). - Reorganized the PCL data module, turning it into a sub-package of cartography with disk, OWS, and PostGIS modules (issue 69). - Preliminary WFS data store and source (issue 74). - shpconfig.py tool under utils/ for configuring unprojected shapefiles (issue 72). - Requiring ElementTree, cElementTree, or lxml for XML parsing - New documentation of filesystem backends for GIS data at doc/filesystem_backend.txt
CHANGES ======= 0.8.3: 24 May 2005 ------------------ - ESRI Shapefile .prj files may cause OGR segfault and hanging Zope. Turning off the spatial reference within the info tabs of these data stores.
CHANGES ======= 0.8.3: 24 May 2005 ------------------ - ESRI Shapefile .prj files may cause OGR segfault and hanging Zope. Turning off the spatial reference within the info tabs of these data stores.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?