#22274: better tutorial for geodjango
-----------------------------+------------------------------------
     Reporter:  digi_c@…     |                    Owner:  nobody
         Type:  New feature  |                   Status:  new
    Component:  GIS          |                  Version:  1.6
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Accepted
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+------------------------------------

Comment (by sephii):

 I would be happy to work on this.

 Here are the things I think could be improved:

 * Create an easier tutorial that doesn't require extensive comprehension
 of world borders, ogrinfo etc that are quite specific. We could go on
 creating an application that defines models with simple coordinates or
 shapes and calculates distances between objects. We could make a tutorial
 that looks like the Django tutorial (1. creating models, 2. the geo admin,
 3. using geo data in views/templates/forms).
 * Simplify GIS installation of GIS libraries (see #24942)
 * Make a better explanation of what GDAL and GEOS are (if the docs are
 aimed to lambda users, we can assume that the following could be explained
 better: "GEOS stands for Geometry Engine - Open Source, and is a C++
 library, ported from the Java Topology Suite. GEOS implements the OpenGIS
 Simple Features for SQL spatial predicate functions and spatial operators.
 GEOS, now an OSGeo project, was initially developed and maintained by
 Refractions Research of Victoria, Canada.")
 * Reorganize/simplify the TOC (GeoDjango installation is placed after the
 GeoDjango tutorial, although you first need to go through the installation
 process to proceed with the tutorial). Also this long list of topics is
 far from being as clear as Django's docs TOC
 * This one might be more of a detail but I would use native types (eg.
 Point) instead of the GEOSGeometry constructor, and try to be consistent
 along the tutorial

--
Ticket URL: <https://code.djangoproject.com/ticket/22274#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.4b8423cc1118c4d6f5e4eb5dadfbdf69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to