Micro Applications

To get access to source code for any of the applications below just click “contact us” and we’ll send you a zip file with the project assets.

What Makes a Map

A map is made up of the base CMapsAnalytics map, along with any number, and type(s) of layers. For example,
one can be display and have interaction setup between an ESRI shapefile layer, a CMaps points layer,a CartoDB layer, and a Google Places layer.

There are currently over 24 pre-canned layer types. All layers inherit from the same base layer class (centigon.mapping.Layer), where most of the
functionality and all of the common functionlaity among layers is contained. What this means, is that while coding with the API, common code can be written
to handle all layers, with more specific code being written to handle any layer-type-specifics. Further, as a developer, you can follow our custom layer development example
to inject anything from D3 JavaScript-powered visualzations, to a layer from a 3rd party mapping provider.

Map Cfg + API Concept

*MapCfg’s are NOT required to use the map

A Map Configration file is a file that’s generated by CMapsAnalytics Designer,
which contains all of the map design metadata in either an XML or JSON format. A config file is not required,
although it’s recommended to use one when creating a map
due to the fact that it saves you from writing more code. Things like your api key, zoom options, and the layer(s) you’ve defined, are included in
the configuration file.

Create a single layer map, using the map cfg vs using the api

For all maps, either be sure you have a div present, with the id of “mapDiv” (the default id),
or simply pass the div id you want to use along to the MapView constructor, e.g.

Create a multi-layer map, using the map cfg vs using the api

For all maps, either be sure you have a div present, with the id of “mapDiv” (the default id),
or simply pass the div id you want to use along to the MapView constructor, e.g.