Creating a Geolocating Congressional District Map with Mapbox

A branded map with geolocation, geocoding, and a custom tileset built from Senate redistricting data to help potential voters answer the question, "Am I even in this new district?"

For the 2022 midterms, two interesting things happened: Texas redistricted in a way that unified much of Central and West Austin into a new consolidated district and a good friend of mine decided to enter the Primaries to represent that district.

Campaign launch event

I produced a few pieces during the campaign, the most interesting for me was an interactive district map. As we spoke to potential voters, many — myself included — wondered, “am I even in this district?”

Map of Austin, TX and the 37th Congressional District

I even got to watch as a well-informed friend used the map on her phone to realize, “Oh wow, I thought I was still in the 25th. And if I didn’t know…” Our collective confusion is warranted; the last time our legislature picked their own voters, they divvied up Austin this way:

Outdated Districts of Austin, TX

Finding the Data

Texas posted the new maps on its redistricting website. Senate Bill 6, designated “PlanC2193,” is available as a map and a collection of downloads. One of those is a Shapefile, a vector geography format for GIS software.

Having recently done another deep dive on interactive mapping, this seemed like a simple job for Mapbox. Here’s the overview:

Flowchart of data from senate files through Mapbox tooling to create the static images and interactive map

Making a Tileset of Districts

Mapbox Studio can import a Shapefile as a custom Tileset.

Custom Tileset in Mapbox Studio

This let me do two things:

  • Add and style district boundaries on the map
  • Look up the district for a given location using the Tilequery API

Designing a Branded Map

I started with one of the Mapbox Gallery examples then customized it to better match the campaign’s visual style and simplify some unneeded details.

I added the tileset in four different ways, as seen in the selected layers. From top to bottom:

Custom Map in Mapbox Studio

  • Text layer to print all districts’ numbers on the map.
  • Line layer to draw a bright white border around only the 37th.
  • Line layer to draw a blue border around all districts.
  • Fill layer to put a bright blue background under only the 37th.

Printed Output

From there, Mapbox allows a limited number of extremely high-resolution raster exports, which we used for social media and print pieces like door hangers.

From one of the door-to-door canvassing days:

Holding door hangers we used for door-to-door canvassing

Creating the Map Site

I discovered Parcel.js while looking for an easy build tool that would help me collect and transpile the Mapbox JS/CSS, my TypeScript, light SCSS, and some repetitive HTML. On build, it generates a static site that users could either access directly or as an embed on the official campaign website on Wix.

The Base Map

Loading a map into an HTML element is easy: just add <div id='map'></div> to a page and make it big. This goes one step further to disable the 3D tilt and rotation because my map style is flat.

  import { Map } from 'mapbox-gl';
  const accessToken = '...';
  const mapStyleId = '...';

  const map = new Map({
    container: 'map',
    style: `mapbox://styles/tsmith512/${mapStyleId}`,
    center: [-97.74, 30.27],
    zoom: 10,

    // Disable mapbox 3D tilt and rotation
    pitch: 0,
    minPitch: 0,
    maxPitch: 0,
    pitchWithRotate: false,
    touchPitch: false,
    dragRotate: false,

But what did we want users to do?

Showing the district map on a handheld device

“Am I even in this district?”

Not everyone is a map nerd. We needed users potential voters to find their district quickly and easily. I expected the bulk of traffic to be mobile, so I wanted to allow three methods:

  1. Tap the map
  2. Search for an address
  3. Use device geolocation

Tap: mapbox-gl fires a click event when someone clicks or taps a point on the map. That’s easy to handle and the Event passed to the callback will have a lngLat object.

  map.on('click', (e) => {

Search: Mapbox provides a great geocoder search control in another library. It adds a simple search box in the top right corner that offers autocompletion of street addresses and handles all the API interaction out-of-the-box. When a result is selected, the results payload includes a center.

  import MapboxGeocoder from '@mapbox/mapbox-gl-geocoder';
  const map = new Map({ /* ... */ });
  const accessToken = '...';

  const geocoder = new MapboxGeocoder({
    marker: false,
    placeholder: 'Search by Address',


  geocoder.on('result', (results) => {
    const point = results.result?.center || false;
    if (point) {
      getTxDistrict({ lng: point[0], lat: point[1] });

Geolocation: Implementation was straightforward but UX got a bit tricky. The campaign site on Wix wouldn’t allow geolocation permission to be passed to the embedded iframe, among other problems. I didn’t want to show a broken locate button — or worse — a clickable button that would error out.

Deep in mapbox-gl’s own GeolocateControl, there is a function to determine if a browser or current viewport context allows access to the Geolocation Web API. I adapted this check from their checkGeolocationSupport().

  const ifGeoSupported = (callback: (x: boolean) => void): void => {
    let supportsGeolocation = false;

    if (window.navigator.permissions !== undefined) {
      // navigator.permissions has incomplete browser support
      // Test for the case where a browser disables Geolocation because of an
      // insecure origin
      window.navigator.permissions.query({ name: 'geolocation' }).then((p) => {
        supportsGeolocation = p.state !== 'denied';
    } else {
      supportsGeolocation = !!window.navigator.geolocation;

From there, when a user loads the page, if geolocation is supported by the browser and device and also the site isn’t being accessed through the Wix embed, it initializes the GeolocationControl and adds it to the map. When geolocation is requested by the user and they give their permission, the data payload will have a coords pair, if successful.

  import { Map, GeolocateControl } from 'mapbox-gl';
  const map = new Map({ /* ... */ });
  const accessToken = '...';

  const setupGeolocator = (supported: boolean): void => {
    if (!supported) {

    const locator = new GeolocateControl({
      positionOptions: {
        enableHighAccuracy: true,
      fitBoundsOptions: {
        maxZoom: 12,
      trackUserLocation: false,
      showUserLocation: false,
      showAccuracyCircle: false,


    /* eslint-disable  @typescript-eslint/no-explicit-any */
    locator.on('geolocate', (data: any) => {
      if (data &&, 'coords')) {
        const latLng = {
          lat: data.coords.latitude,
          lng: data.coords.longitude,



Showing the district map on a handheld device

LatLng Marks the Spot

Each of these event handlers passes the coordinates to a simple function that makes a Tilequery API request to ask, essentially, “what shapes in the tileset contain this point?”

For example, what district is the Texas Capitol in? (Ours!)

    "type": "FeatureCollection",
    "features": [
            "type": "Feature",
            "id": 37,             // <-- The answer
            "geometry": {
              "type": "Point",
                "coordinates": [
            "properties": {
              "District": 37,     // <-- The answer also *
                "tilequery": {
                    "distance": 0,
                    "geometry": "polygon",
                    "layer": "planc2193-b0e2m6"

*The district number is included both as the numeric ID of the polygon and also as the value for its “District” property.

After receiving the district information, getTxDistrict moves a Marker and a Popup to the search location and adds a message explaining if the search is in our district, a different district, or if there was an error (likely the search location was outside of Texas).

  import { Map, Marker, Popup } from 'mapbox-gl';
  const map = new Map({ /* ... */ });
  const accessToken = '...';
  const tilesetId = '...';

  const marker = new Marker({
    color: '#D96523',

  const popup = new Popup({
    className: 'district-popup',

   * Look up a given position with Mapbox's Tilequery API to see what TX district
   * the position falls into and raise a popup on the map with the info.
   * @param position (SimpleLngLat) position to query for
  const getTxDistrict = (position: SimpleLngLat): void => {
      .then((res) => res.json())
      .then((payload) => {
        const district = payload?.features[0]?.id || false;
        if (district == 37) {
          popup.setHTML(`You're with us in <strong>District 37!</strong>`);
        } else if (district) {
          popup.setHTML(`You're in <strong>District ${district}.</strong>`);
        } else {
            `We could not determine which Texas Congressional District this is.`

Static Site Hosting

I hooked up my repository to Cloudflare Pages so that updates would be built automatically and we wouldn’t need additional hosting infrastructure. Then I added as a custom domain and turned on Web Analytics to get some basic stats.

Cloudflare Pages Dashboard

Was it useful?

Throughout February, over seven thousand users visited the map, overwhelmingly mobile, largely seeing the embedded map on Wix, and referred from Facebook. According to Mapbox, in that same period, the Tilequery API served just over four thousand lookups.

Cloudflare Web Analytics Report

Anecdotally, the Casar campaign for East Austin’s 35th District reached out to say that they were using our map with their voters, too. Also, within days of us publicizing our map, the incumbent campaign added a screenshot of the Senate’s PLANC2193 (difficult to read) to their website and linked to the Texas Tribune’s interactive article on all Texas redistricting — which, while very informative, was both verbose and difficult to use on a mobile device.

I think that measures in at “well worth the effort” both as a campaign tool and an experiment. From my point of view, that can be expanded to my experience with the campaign generally. I was disappointed by the extent of the gatekeeping we experienced, but that only reinforced my opinion that more involvement from more people will yield more representative ideas. And everyone has something to offer.

Test it for yourself:

Printed material and static images use map data from Mapbox and OpenStreetMap and their data sources. © Mapbox © OpenStreetMap. Improve this map.

Other tooling and campaign material paid for by Chris Jones for Congress Committee.

Check out the code for the Chris Jones for Congress Map on GitHub.

Disclaimer: I am a Cloudflare employee, but our use of Cloudflare Pages and Cloudflare Web Analytics both fell within the limits of the free tier. The company neither endorses this candidate nor my work on this project specifically.