CMaps Analytics was designed with embedded Location Analytics in mind, which grants a lot of flexibility for integrating CMaps Analytics JS APIs, meta data templates, cloud maps services, and even our point and click designer. This document is intended to streamline the learning curve and provide you with some basic best practices for integrating CMaps Analytics into your enterprise or commercial application or platform.
Before diving into CMaps Analytics integration strategies, we recommend learning about how CMaps Analytics works.
Developer Introduction
CMaps Analytics JS API Component
KEY COMPONENTS:
CMaps Analytics JS API & Cloud Services
HOW THIS APPROACH WORKS
This appraoch is similar to building maps with any 3rd party Web maps API like Google Maps, Leaflet, ESRI, HERE, etc. The difference, is CMaps Analytics provides a large collection of pre-built visualization layers, functions, properties, and widgets that can be rapidly assembled into a complete geospatial analysis component. There is no specific CMaps Analytics branding or requirements.
PROPERTYÂ SHEET
Because this appraoch does not utilize or license CMaps Analytics Designer to customers, it requires your organization to create configuration screens or a property sheet to modify the behavior and appearnce of the map. CMaps ANalytics Designer provides a great benchmark for the kinds of properties, behaviors, layers, and widgets that can be configured by your end users.
CLOUD API OR EMBEDDED
Because CMaps Analytics JS API is web maps service agnostic (Google, Leaflet, ESRI, etc), it can be accessed from CMaps Analytics cloud API (this is preferred approach), or the JS API can be embedded inside of your software application (with proper commercial licensing in place).
WHO SHOULD USE THIS APPROACH
This is a perfect solution for any organization seeking to use web maps APIs like Google or Leaflet for enterprise software solutions. For software vendors like BI / analytics who need a generic, yet highly configurable mapping component. This appraoch is also applicable to vertical solution providers who need very specific advanced mapping solutions inside of their application.
JS API Component with 50 Lines of Code Example
BENEFITS TO THIS APPROACH
The primary benefit to using CMaps Analytics JS API is time savings and reduced code (up to 80%). CMaps Analytics streamlines important features and functions saving hundreds or thousands of lines of code. With CMaps Analytics integrations with Google Maps, HERE, Leaflet / MapBox, and GIS solutions like ESRI, this option also provides a single gateway into the map vendor of your choice without learning another web API.
REQUIRED LICENSE AND PARTNERSHIP
This integration approach for internal use requires a standard CMaps Analytics license  which includes web maps services. If you are planning to embed CMaps Analytics JS API into a commercial app that is re-sold or sub-licensed to your customers, you will require a commercial use license (OEM), along with proper commercial licensing from the map vendor of choice (Google, Mapbox, HERE, ESRI, etc). We can work with you to secure the proper licensing from any map vendor.
This integration approach for internal use requires a standard CMaps Analytics license which includes web maps services. If you are planning to embed CMaps Analytics JS API into a commercial app that is re-sold or sub-licensed to your customers, you will require a commercial use license (OEM), along with proper commercial licensing from the map vendor of choice (Google, Mapbox, HERE, ESRI, etc). We can work with you to secure the proper licensing from any map vendor.
CMaps Analytics Designer Integration Kits
KEY COMPONENTS:
CMaps Analytics JS API & Cloud Services
CMaps Analytics Designer
CMaps Analytics Templates
HOW THIS APPROACH WORKS
This appraoch is similar to componentizing CMaps Analytics, but alleviates the need to create all mapping properties inside of your application. Your application / platform will require either an import mechanism to load CMaps Analytics template files or your platform will need a webhook service that CMaps Analytics can stream map template metadata to. This approach requires some collaboration with CMaps Analytics team.
WHO SHOULD USE THIS APPROACH
This integration strategy is best applicable for an organization that desires a simple, lean integration point to embed customized maps AND will resell or license the complete CMaps Analytics Designer solution along with a native integration.
BENEFITS TO THIS APPROACH
This is the simplest integration point, requiring the fewest lines of code, because a bulk share of the map configuration occurs inside of CMaps Analytics Designer. The benefit is a native embedded export from within CMaps Analytics Designer.
REQUIRED LICENSE AND PARTNERSHIP
This integration approach requires an OEM / Reseller agreement with CMaps Analytics, and is usually initiated through a collaborative integration and native export feature.
EXAMPLE IMPLEMENTATION:
Antivia DecisionPoint
CMaps Analytics integration kits for SAP BusienssObjects
How to Get Started
To get started, you need access to CMaps Analytics Designer, where you can access API Docs, Code Examples, and CMaps Designer.
Sign Up for a Test DriveVIEW DEVELOPER INTRODUCTION
Additionally, for custom HTML5 apps, you can always schedule a call with one of our API advisors who can ensure you have everything you need to succeed.
SIGN UP FOR A CONSULTATION