Report a bug
Wrong rendering, a crash, a regression against the original CARTO SDK. Include the platform, the SDK version and a style or tile source that reproduces it.
Open an issueAsk for a feature
Feature requests are issues too. The ones that get the roadmap label show up on the roadmap page, so this is also how you influence what comes next.
Ask a question
Not sure whether something is a bug or a usage question? Discussions is the low-stakes place for it — no template, no triage.
Open a discussionThe repositories
One fork, two submodules. Work in a submodule needs its own branch, commit and PR — the pointer bump in the main repo comes second.
MassifMaps
base branch master
The SDK itself — C++ core, SWIG bindings, platform glue, build scripts and this site.
massif-maps-libs
base branch develop
Submodule: the GL vector-tile renderer (vt), the Mapnik/CartoCSS pipeline, geocoding and the SGRE/OSRM routing engines. Most renderer work lands here.
massif-external-libs
base branch develop
Submodule: vendored third-party dependencies (cglib, freetype, harfbuzz, MLT decoder…).
Contributing
Pull requests are welcome, including on the platforms marked unmaintained on the platforms page. Three things to know before the first one:
Read BUILDING.md first
The SDK is a large C++ project — a full build takes an hour and needs a SWIG fork and a boost symlink. The Android demo under scripts/android-dev is the fast loop.
Conventional Commits
feat:, fix:, chore: — no commitlint enforces it, the discipline is on us. One PR per repo, submodule PR first, then the pointer bump.
Document in the same change
Anything that changes render behaviour ships with its docs/internals/rendering/ edit in the same commit — including what was ruled out, not only the fix.
Licence
BSD 3-Clause, like the original CARTO SDK. No licence key, no registration, no online service to sign up for — see Migrating to Massif Maps if you are coming from the CARTO 4.x API.