Entity-based mapping framework

Overview

Entity based mapping infrastructure. Leverages the Entity API CRUD to assemble maps, but provides only text-rendering capability out of the box. Supports plugin architecture for any rendering engine to supply rendered map layer classes, and has a table for storage of the configurations for these rendered displays. Will define an API for access to Maps and initial development is focusing on sub-modules for plugin integration with various rendering libraries such as Leaflet, Mapserver and d3.

Requirements:

• Ctools - provides plugin framework for introducing new sources, layers, maps, and rendering engine displays.
• Entity - provides basic object model CRUD.
• Entity Reference - provides the linkage between maps, layers and sources.
• Views (optional) - Advanced UI.
• Editable Views (optional) - Advanced UI.

Data Model

eMapping defines the basic primitives of a GeoSpatial map dataset:

• Map - The base object that defines a self-contained map. Bundled by emapping_map_type.
• Layer - Defines a layer to display in a map object. Bundled by emapping_layer_type.
• Source - the data set definition for a layer. Bundled by emapping_source_type.
• Display - Render-engine specific configuration for all map components: maps, layers,controls, and others for render-engine plugins.

Render-Engine Sub-Modules (in development - not yet released)

• eMapping Leaflet - exposes eMapping maps with supported layer types to Leaflet module (using Leaflet hooks, similar to Leaflet More Maps).
• eMapping Archive - renders eMapping maps as a tar.gz file archive. Currently capable of rendering SQL sources and WKT sources as ESRI shapefiles.
• eMapping Mapserver - renders eMapping maps as mapserver ".map" files (in development).