About this plugin
Cartaveo Maps is the WordPress plugin for Cartaveo,
the collaborative mapping service. It embeds a map collection from Cartaveo
into any post or page, via a Gutenberg block or the
[cartaveo collection=”your-slug”] shortcode. On collections with open contribution, your readers can submit
new places — submissions are captcha-protected and held for your
moderation on Cartaveo. Beneath the map, the plugin renders a crawlable list of the collection’s
entries — each one a link to its page, with its category and a description
org ItemList / Place structured data. The embedded
map itself is served noindex, so this list is what search engines actually
read about your map.
The shortcode takes style ( classic, guide, atlas, gallery,
ledger or compact — six designs for the widget, from a list beside the
map to a map alone); the block keeps the same choice as its design
attribute, set in the sidebar under Style. Both accept theme ( light,
dark or auto, which follows each reader’s own setting), basemap ( minimal, streets,
midnight or tinted — the map drawn under the pins) and accent (a hex
colour that
tints the map’s links and its selected pin), so the map can be made to sit
with your theme rather than against it. An accent that would be unreadable
on the map’s background is ignored for text and kept only for the pin.
This plugin relies on the Cartaveo service to work — see the “External
services” section below for exactly what is sent, when, and under which
terms.
External services
com), the collaborative
mapping service the embedded collections live on. It is needed to render the
map itself and to fetch the collection’s entries for the crawlable list
under it. If you run your own Cartaveo instance, the plugin talks to your
configured base URL instead; everything below then applies to your instance
rather than the hosted service.
What is sent, and when:
- When a post containing the block or shortcode is rendered, your web
server requests the collection’s public entries from the Cartaveo API to
build the entry list. Only the collection’s identifier is sent, and the
response is cached for an hour, so this is not a per-visit request.
- In your visitors’ browsers, the embed loader script and the map iframe
load from Cartaveo. Those requests include your site’s hostname and the
plugin’s version, which Cartaveo uses for aggregate embed-usage
statistics; as with any web request, Cartaveo’s server also sees the
visitor’s IP address and user agent.
- The plugin sends no visitor personal data, no account data and no
cookies. If a visitor chooses to submit a place on an open collection,
they do so inside the map iframe, directly with Cartaveo.
This service is provided by Cartaveo:
com/terms),
com/privacy).
The map inside the iframe draws its basemap tiles from OpenFreeMap
org), a free tile service run by Hyperknot Software Kft.
Cartaveo does not proxy them, so your visitors’ browsers request the map
style and its tiles from OpenFreeMap directly as they pan and zoom. Those
requests carry the visitor’s IP address and user agent, as any web request
does, and the referring page. OpenFreeMap needs no API key and states that it
keeps no user accounts, sets no cookies and does not store IP addresses in
its regular logs.
:
org/tos/),
org/privacy/).