MapD Charting High Level Explanation


1 comment

  • Avatar
    Jonathan Rajavuori

    Hi Dominic!

    Mapd-charting is originally a fork of dc and very close to its interface, yes. Like dc, it is meant to bridge the gap between d3 and crossfilter. There are two main, high-level differences between mapd-charting and its predecessor:

    • mapd-crossfilter integration. mapd-crossfilter provides a similar interface to the original crossfilter, but it sends SQL requests to OmniSciDB to do the filtering and retrieve data instead. This means you can make charts to visualize way larger amounts of data than you could do client-side only - and with nearly instant crossfiltering on it, too - using the speed of OmniSciDB behind the scenes.
    • Mapbox-based charts using the backend rendering of OmniSciDB. There are examples of each of these in the mapd-charting documentation page. Similarly, this allows rendering very large amounts of geospatial data (points, linestrings, or polygons) with OmniSciDB and showing the result on a map, with crossfiltering features as well.

    Hope this was what you were looking for. Don't hesitate with any further questions!

    Comment actions Permalink

Please sign in to leave a comment.