Notes from discussion about 'How location, mapping, and geo stuff' would be if it were done properly from scratch

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Bdragon, bec, Bevan, arthurf, ultimike (mike anello), and Allie Micka discussed what a mapping platform in drupal would look like, how it would be structured, modularized and extendible, if nothing already existed, and if things were ideal. Here are notes from the discussion. Please add anything I may have missed or not covered. Bevan/

By Module:

  • geo: Storage of lat-lon coordinates (and precision / accuracy data?). Only knows wkt (well known text) geoformat.
    • Extensible by storage engines to store ll-data in other formats / databases (contrib)
    • Includes and defaults to PostGIS, MySQL Spatial, Generic Table
    • might be extensible for metadata by gID?
  • geo_eio: (Geo Translator?): Extends Geo's storage interface to allow input and output of ll data in other formats
    • Extensible by 'format' modules, e.g.:
    • georss
    • kml
    • gml
    • geojson
    • extensible by presentation layers (interface for client-side mapping APIs):
    • gmap
    • ymap
    • openlayers
  • address: Provides API for storing addresses
    • Extensible with locale modules for locale specific operations like:
      • Address form validation
      • Knowing and enforcing that, for example
      • US addresses all have postal codes, and the format of that
      • US states
      • Other country's addresses uniquenesses
      • Example modules:
      • address_us
      • address_uk
      • address_nz
  • address_ui: Provides UIs for address forms and printing text/html strings
    • Dependencies:
      • address
  • geocode: provides an interface to geocode placenames and addresses, and provides an API for geocoding services to hook into, like:
    • geocode_gmap
    • geonames.us
    • local/custom database / server / service
  • reverse_geocode: potential / future module to provide an interface to ungeocode lat-lon data into placenames and/or addresses, and provides an API for reverse geocoding services to hook into.
    • geonames?
  • geo_tables? an interface for managing large external geo resources -- bec
  • geo_node -- allows nodes to have address and lat-lon data
  • geo_user -- allows users to have address and lat-lon data
  • geo_taxonomy -- ...
  • ...

Discuss this document here

Location and Mapping

Group organizers

Group categories

Wiki type

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: