|Version 11 (modified by 8 years ago) (diff),|
This document is to outline the roadmap for the features and fixes that will go into GeoDjango as a part of the 1.1 release. This is meant to be a living document, so feel free to edit -- but please no vandalization or flaming.
gis-1.1 mercurial branch is deprecated as all features spanning multiple tickets and/or branches have now been merged into trunk. Please use SVN trunk to get the latest features for GeoDjango in 1.1.
All development will be taking place in the
gis-1.1 repository hosted at the GeoDjango Mercurial page. The
gis-1.1 repository is synchronized with SVN trunk, as well as, Russell Keith Magee's aggregation git repository, and may also include various patches from tickets before they are checked into trunk (e.g., for SpatiaLite support). Because of the dynamic nature of this repository, it is not recommended for production use.
Informal discussion will take place on IRC (in the
#geodjango channel on FreeNode network), and more lengthy discussion (like any feature proposals) should take place on the newly created GeoDjango mailing list.
- Now in trunk as of r9748.
- Add new PostGIS aggregates:
- Done: Add
- Done: Add support for
- #10159: Fix
F()expressions to work on geographic fields.
SQLite (SpatiaLite) Support
- Contacts: Hobu, Chris Schmidt
- The start of the module is already in mercurial repo (serializers.py).
- Related tickets?
- Have operation performed on geo field instead of new attribute
- Related Tickets: #9745
geojson()(Hobu implemented at one point..)
Contact: Dane Springmeyer
- #8972: Add ability to delete selected vector features
- #9278: Geographic Admin doesn't show vector overlay when LANGUAGE_BIDI is set
- #9299: Zoom too far in with
PointFields in the admin
- #9694: Fix admin bug for Ubuntu 8.10/Apache 2.2.9
- #9806: Fix
GeometryColumnsmodels (to be seen in admin)
Refactor GEOS and GDAL interfaces
- Goals: clean up cruft, modularize better, move tests into modules, docstring & comment cleanup
- Already modularized
- #9557: no error message when using old GDAL and trying to get GEOJSON
- #9877: Pythonic, list-like interface to GEOS geometries.
- #10222: Add support for
#9806: (for fixing
- #9855: Simplify
SetFromUserInput(already fixed in mercurial)
- #10368: Add expand_to_include method to gdal Envelope
- #10380: Envelope should allow min_x == max_x and/or min_y == max_y
- #9204: Add
- #9955: Support for multiple maps.
- #10072: Add
General code cleanup; may trim up template path (
- #9794: SQL works on 10 but not on 11 -- bug in Oracle or GeoDjango?
- #9858: Add
- #9437: Database connection is closed prior to first HTTP request when deploying via FastCGI
Fortunately, you will only need to learn a subset of Mercurial's features to participate -- and most of them are very similar to what you would do in SVN. This section is a brief guide of the mercurial commands you'll need to work with the
For those with setup tools and a command-line:
$ easy_install mercurial
However, there are also Mercurial binary packages for Windows and Mac OS X.
Getting a Copy
Here's how to get a copy of the repository -- unlike SVN, you get every changeset when you "clone" a repository:
$ hg clone http://geodjango.org/hg/gis-1.1/
After cloning, work with the code as necessary. Once modified, you create a patch as follows:
$ hg diff > my_patch.diff
However, if you've made your own changes (e.g., checked in your own local revisions with
hg ci) then you will need to send me a diff to the latest pulled revision from the repository. In other words, something like:
$ hg diff -r 49
To get the latest changes (analagous to
svn update), you pull the new changesets and then update the repository with the following commands:
$ hg pull $ hg update
Or, if you're lazy you can do it in one command:
$ hg pull -u