Diese Seite ist noch nicht übersetzt. Sie lesen die englische Version.

Connect QGIS and ArcGIS

Add MapDove foot traffic, demographics and your saved analyses to QGIS, ArcGIS Pro and ArcGIS Online as live layers through the OGC API – Features service.

MapDove publishes the data your plan includes as an OGC API – Features service, the open standard that desktop and web GIS read natively. Add it once and the layers stay live: every time QGIS or ArcGIS draws them, they come straight from MapDove.

GIS connections are included on Pro, Business and Enterprise, the plans with API access. In the app, Settings → GIS connections shows your service URL, creates a key and lists every layer.

Service URL and sign-in

Service URL https://api.mapdove.com/ogc
User name mapdove (any value works)
Password an API key, ms_live_…

The service accepts the key in three ways, so it works in any client:

  • HTTP Basic: any user name, with the key as the password. QGIS and ArcGIS Pro ask for these when you connect.
  • Bearer token: Authorization: Bearer ms_live_…, for scripts and custom tools.
  • Query parameter: https://api.mapdove.com/ogc?api_key=ms_live_…, for ArcGIS Online, which can’t send credentials to OGC services. Every link the service returns carries the key, so the client keeps authenticating as it pages through features.

Use a dedicated key for GIS (for example “QGIS – planning team”), so you can revoke it without breaking other integrations. Revoking the key, removing the member who created it, or moving to the Free plan stops access right away.

QGIS

Works in QGIS 3.16 and later.

  1. Open Layer → Data Source Manager → WFS / OGC API – Features.
  2. Either click Load and import the connection file from Settings → GIS connections (it includes the key if you created one on that page), or click New and enter:
    • Name: MapDove
    • URL: https://api.mapdove.com/ogc
    • Version: OGC API – Features
    • Authentication: Basic, user name mapdove, password your API key. If you leave this empty, QGIS asks when you connect.
  3. Click Connect, select layers such as austin-places and austin-hexes, and click Add.

Tip: in the connection dialog, turn off Only request features overlapping the view extent. QGIS then loads each layer once (a whole city fits in one request) instead of fetching again every time you pan, which also saves API calls.

ArcGIS Pro

Works in ArcGIS Pro 3.0 and later.

  1. On the Insert tab, click Connections → Server → New OGC API Server.
  2. Enter https://api.mapdove.com/ogc as the Server URL.
  3. Under Authentication, enter user name mapdove and your API key as the password, then click OK.
  4. In the Catalog pane, expand Servers → MapDove and drag a collection onto the map.

ArcGIS Online and ArcGIS Enterprise

  1. In Map Viewer, click Add → Add layer from URL.
  2. Paste https://api.mapdove.com/ogc?api_key=ms_live_…. If the type isn’t detected, choose OGC API – Features.
  3. Pick a collection, click Add to map, and save the map.

Anyone who can open that map, or who sees the URL, can read your MapDove data and spend your API quota. Share such maps only inside your organization, and revoke the key if the URL travels further than intended. If your organization runs its own ArcGIS Enterprise portal, ask us to allow its address. MapDove allows arcgis.com by default.

Layers

Every city has four layers. Replace austin with any city slug (houston, phoenix, miami, dubai).

Collection Geometry Attributes
austin-places Points name, address, category, brand, neighborhood, square footage, visits, previous-period visits, change %, average daily visits, rank in category, period start and end
austin-footprints Polygons building outline per place, with name, category, brand, neighborhood and square footage
austin-hexes Polygons population, households, median income and age, daytime population, density, % college, % family, rent and traffic indexes, growth rate, segment, neighborhood
austin-neighborhoods Polygons name, population, median income, number of places

Saved analyses

Every project your workspace saves with results also becomes one or more layers, named project-<id>-<layer>:

Analysis Layers
Site suitability scores (scored hexagons), top_sites (ranked points)
Huff forecast candidate (the site, with its forecast), trade_area (polygons with visitor share), impacted (stores that lose visits)
Catchment rings rings (one polygon per ring, with its demographics)
Site comparison sites (points with scores), catchments (each site’s ring)
Trade area trade_area (polygons with visitor share)
Area analysis area (the drawn polygon, with its demographics and visits), top_places (the busiest places inside)

Nested values are flattened into ordinary columns (for example criteria_income), and lists such as segment mixes are stored as JSON text, so the attribute table works in any GIS.

Choosing the period

The places layer shows visits for the last 90 days by default. To pick another period, add datetime to the layer URL as a date or an interval:

https://api.mapdove.com/ogc/collections/austin-places/items?datetime=2026-09-01/2026-09-30

Open ends use .., as in datetime=2026-06-01/... Periods are clamped to your plan’s history, like everywhere else in MapDove. You can also filter places and footprints with category and brand (slugs), and any layer with bbox=minLon,minLat,maxLon,maxLat.

Usage and limits

  • Each page of features counts as one API call, up to 10,000 features per page. Connecting, and listing or describing layers, is free.
  • When the monthly quota runs out, layers stop loading and the service answers 402 plan_limit until the next month or an upgrade.
  • Coordinates are WGS 84 longitude/latitude (CRS84). The service returns JSON and GeoJSON.
  • Places are © OpenStreetMap contributors (ODbL) and, in the US, © Overture Maps Foundation (CDLA-Permissive 2.0); visit figures are modeled estimates (Data sources). Keep the attribution when you publish maps made from these layers.

For developers

The service follows OGC API – Features Part 1 (Core and GeoJSON). Any client that supports the standard can use it, including GDAL/OGR (ogrinfo OAPIF:https://api.mapdove.com/ogc --config GDAL_HTTP_HEADERS "Authorization: Bearer ms_live_…"), Python’s OWSLib, and Leaflet and OpenLayers plugins. Endpoints: /ogc, /ogc/conformance, /ogc/collections, /ogc/collections/{id}, /ogc/collections/{id}/items and /ogc/collections/{id}/items/{featureId}.