Changes between Version 109 and Version 110 of GeoDjango


Ignore:
Timestamp:
03/09/2008 10:41:55 PM (7 years ago)
Author:
springmeyer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeoDjango

    v109 v110  
    6262 * Mapping Framework (generating custom tiles, layers, labels, etc.)
    6363   * [http://www.mapnik.org/ Mapnik] is modern, but very early on in development and ''completely'' lacks documentation.  However, the code is elegant and clean, and it was designed for integration with Python.  First to use AGG rendering.
    64    * [http://mapserver.gis.umn.edu/ Mapserver] is the leading open source map renderer. !MapServer is documented and has a strong and has strong community support.  Uses text-based configuration files, which may be difficult to set up.  AGG rendering and dynamic loading of configuration files (''e.g.'', from a string) has been added to version 5.0.
     64   * [http://mapserver.gis.umn.edu/ Mapserver] is the leading open source map renderer. !MapServer is well documented and has strong community support.  Uses text-based configuration files, which may be difficult to set up.  AGG rendering and dynamic loading of configuration files (''e.g.'', from a string) has been added to version 5.0.
    6565 * WMS Server
    6666   * I'm not satisfied with any of the current WMS/WFS implementations.   One implemented in Django would be desirable, ''e.g.'', {{{django.contrib.gis.wms}}}.  Thoughts anyone?  (OWSLib looks good, see below)
Back to Top