Changes between Version 74 and Version 75 of GeoDjango

06/02/2007 06:17:34 PM (11 years ago)

moved background info to separate page


  • GeoDjango

    v74 v75  
    11= Contents =
    22The [ GIS] branch intends to be a world-class geographic web framework.  Our goal is to make it as easy as possible to build GIS web applications and harness the power of spatially enabled data.
    3  * [GeoDjango#Background Background]
    4    * [GeoDjango#WhatsGIS What's GIS?]
    5    * [GeoDjango#UsefulCode Useful Code]
    6    * [GeoDjango#UsefulData Useful Data]
    73 * [GeoDjango#FAQ FAQ]
    84 * [GeoDjango#Implementation Implementation]
    3026   * [GeoDjango#PostGISGEOSFunctionFieldLookupTypes PostGIS GEOS Function Field Lookup Types]
    3127   * [GeoDjango#ExtraInstanceMethods Extra Instance Methods]
    33 = Background =
    34 '''Note:''' The content herein is a loosely structured collection of notes and links that we have found useful, not necessarily what will be supported in the future.
    36 == What's GIS? ==
    37  * [ Series of blog posts] giving intro to GIS; choice quote from [ an early post]: "If you feel like ending a conversation with a developer then simply bring up the topic of character encodings ... [o]r ... coordinate systems. ... So in the spirit of Tim Bray's and Joel Spolsky's wonderful writeups of character encodings, I thought I'd put together a basic survival guide to coordinate systems over my next few posts and then tie it back to Google Maps."
    38  * More on [ map projections], including why people can't agree on just one (utf-8).
    39  * [ geodesy] the field of science for this stuff.
    41 == Useful Code ==
    42  * [ PostGIS], the [ OpenGIS SQL Types (pdf)] implementation for Postgresql
    43  * [ GEOS], low-level C++ port of [ Jave Topology Suite], used by PostGIS
    44    * [ PyGEOS, now outdated due to PCL, below], and shedloads more stuff on "python, geospatial, and the web"
    45    * [ Python Cartographic Library] - [ actively maintained], huge GIS package, GPL.
    46    * There are direct SWIG Python bindings in GEOS 3.0.0RC1 and above.  In other words, the entire GEOS API may be called directly from Python.
    47  * [ GeoTypes] is a type (and conversion) library for PostGIS via psycopg.
    48  * [ Geopy]
    49    * Calculates distances using (very accurate) [ Vincenty], and uses the [ WGS 84] datum by default.
    50    * Has utility functions for unit of measurement (UOM) conversions (e.g. meters -> kilometers, kilometers -> miles, etc.)
    51    * Excellent GeoCoding capabilites.  Has interfaces for Google, Yahoo, Microsoft Live, MediaWiki, and [].
    52  * [ GDAL/OGR], a library for fiddling with raster geo images.
    53    * Has a Python interface.  A SWIG interface is in development, but not yet stable (no access to ''full'' API).
    54    * [ shapelib] and [ ogr2ogr] are useful for ESRI shapefile manipulations.  [ ESRI shapefiles] are a lingua frana GIS format.
    55  * [ Geo::Coder::US] An excellent ''Perl'' library for GeoCoding that powers [].  Users can create their own Geographic databases using the Census Bureau's TIGER/Line data (see below).
    56  * [ GeoRosetta], CC-BY-SA licensed, quality-controlled, collection of geocoding data.  Not yet released to public(?).
    57  * [ MapServer]: University of Minnesota (UMN) "open source development environment for building spatially-enabled internet applications."
    58  * [ Mapnik]: C++ and Python toolkit for developing mapping applications.  Claimed benefits over MapServer: "It uses the AGG library and offers world class anti-aliasing rendering with subpixel accuracy for geographic data. It is written from scratch in modern C++ and doesn't suffer from design decisions made a decade ago." ''See'' [ MapNik FAQ].
    59  * [ pyproj]: Pyrex generated python interface to PROJ.4 library.
    60  * Ruby on Rails
    61    * [ GeoRuby]: Interface for PostGIS and MySQL spatial extensions, but not sure about spatial querying.
    62    * [ IvyGIS]: Google-maps type displays with RoR and UMN's MapServer
    63    * [ Spatial Adapter for Rails]: A plugin for Rails which manages the MySql Spatial and PostGIS geometric columns in a transparent way (that is like the other base data type columns).  This might have some useful techniques for when we try to support other spatial extensions other than PostGIS.
    64    * [ Cartographer] GMaps plugin
    66 == Useful Data ==
    67  * [ TIGER/Line]: "The TIGER/Line files are extracts of selected geographic and cartographic information from the [ Census Bureau's] TIGER®  (Topologically Integrated Geographic Encoding and Referencing) database."  This data is useful in creating your own geocoding database service.  Currently 2006 Second Edition is the latest.  Note: The Census Bureau will be [ providing SHP files] in Fall, 2007. 
    6929= FAQ =
Back to Top