Skip to content
Octo × Web maps PT Request an assessment

Octo for web maps and tiles

The whole map in a single file. What it claims, you decide.

Municipal boundaries, indicators, orthophotos and cadastral data can become tiles from the command line: tippecanoe and GDAL generate them, PMTiles stores everything in one static file, MapLibre draws in the browser from a JSON style and PostGIS serves same-day tiles through Martin. Octo writes the scripts, checks tile size and style against the data and delivers to staging. Classification, generalization, what can be published and the move to production stay with qualified people.

Request an assessment See what it does
A terminal generates a PMTiles file with tippecanoe; Octo, at the center, takes the file to a tile pyramid at three zoom levels and to a browser window showing a fictitious choropleth map, with the staging badge $ tippecanoe -o mun_41.pmtiles -Z4 -z12 -l municipios mun.fgb features and drops in the log $ pmtiles verify mun_41.pmtiles ok · header 127 bytes tile over 500 KB → review HEADER · 127 B ROOT DIRECTORY (16 KiB) JSON METADATA TILES · READ BY RANGE PYRAMID · Z4 / Z5 / Z6 TILE > 500 KB → REVIEWER staging / map.html fictitious data STAGING "url": "pmtiles://…/mun_41.pmtiles" OCTO × TILES WEB MAPS C-07
MapLibre GL JS6.16from October 25, 2026; ES module and WebGL 2 only
GDAL3.13gdal2tiles deprecated; use gdal raster tile
PMTiles v3 header127 Broot in the first 16 KiB
Sources16listed at the end of the page
01

What Octo does with web maps and tiles.

Six possible deliverables, drawn from the research. All start from a copy of the data, with read access to the official database, and all go to review by whoever is accountable for the map.

A whole dataset in one PMTiles

Boundaries, hydrography or an indicator become a single file with tippecanoe or ogr2ogr -f PMTiles, read by the browser through range requests, with no map server.

Deliverable: file checked with pmtiles verify and a drop log

Versioned MapLibre style

Writes the JSON style with the approved classes, zoom expressions, labels and attribution, and checks each layer against the tileset metadata before publishing.

Deliverable: style reviewable line by line and an audit report

Orthophoto as raster tiles

Virtual mosaic of the sheets and gdal raster tile in WEBP, with tile counts per zoom and a sample to look at; migrates old gdal2tiles routines.

Deliverable: WMTS-compatible folder and per-zoom report

Same-day tiles, straight from PostGIS

A public view with no personal data and an ST_AsMVT function served by Martin, for layers that change every day, such as cadastral records and public works.

Deliverable: SQL function with checks and rollback

Migration to MapLibre 6

Finds pages that load the library through <script src>, old style expressions and WebGL 1 dependencies, and proposes the switch to an ES module.

Deliverable: list of affected pages and proposed change

OGC services for those who require them

When the consumer is a government agency or a desktop client, sets up WMS/WMTS in GeoServer, QGIS Server or MapProxy, and reads the GetCapabilities of official services such as IBGE's.

Deliverable: service in staging and a test script
02

Eight arms, one map on the web.

The same Octo cycle, applied to tiles and web maps. Each arm has a narrow role; the ones who decide classes, approve what goes public and publish to production are people.

  1. Discovery

    Surveys what already exists

    Pages with maps, MapLibre or Leaflet version, tile folders (XYZ or TMS), OGC servers, gdal2tiles routines and where each piece of data comes from.

  2. Data

    Pins down references

    Reference system of the dataset, key fields (IBGE code, parcel number), zoom ranges per layer, and which one is the official dataset and which one is the working copy.

  3. Security

    Takes care of what goes public

    No personal data in the tile, restricted CORS, bucket credentials outside the script, base map key locked to the domain. Cadastral records with owner data go through LGPD review with the client.

  4. Architecture

    Picks the path

    Static file, tile server or OGC service, based on update frequency and who consumes it; tippecanoe or GDAL; vector or raster.

  5. Development

    Writes scripts and style

    Generation with simulation and a log, JSON style with the approved classes, SQL function with rollback and the map page, with the source of each syntax noted.

  6. Review

    Checks on the map

    Feature counts, tile sizes, style against metadata and the map opened in the browser, looking at the content, not just the absence of errors.

  7. Release

    Delivers to staging

    Only with your OK, it sends the file and the style to the staging environment. The switch in production is done by a person.

  8. Documentation

    Records what applies to your project

    Tool versions, generation parameters, approved classes, date and origin of each publication. What worked for one dataset is not assumed ready for another.

Octo works with read access and as support. It does not change the official database, does not publish to production and does not sign cartographic products: that belongs to qualified people.

03

Each task, its own path.

The criteria Octo uses to choose, with the documentation for the version installed in your environment.

TaskPathNote
Data that rarely changes, heavy traffictippecanoe → PMTiles in a bucketServer needs Range and CORS
Data that changes every dayST_AsMVT + MartinPublic view with no personal data
Source in several formatsogr2ogr -f PMTiles or -f MVTLess control over dropping
QGIS project already set upqgis_process run native:writevectortiles_xyz or native:tilesxyzdirectoryRaster keeps the QGIS rendering
Orthophotogdal raster tile (GDAL 3.11+)gdal2tiles deprecated in 3.13
New indicator on existing geometrytile-join -cNo geometry regeneration
Clip of a large tilesetpmtiles extract --bbox --maxzoomWorks with a remote file
Consumer requires WMS/WMTSGeoServer, QGIS Server or MapProxyCommon in government agencies
Old page with MapLibre 5Migrate to <script type="module">WebGL 2 required in v6
04

From a one-off map to a dataset published every night.

Three steps. Each one only makes sense after the previous one has shown results on your team.

A proposal, not a promise

1 Today

One map per request

You point to the dataset and the indicator; Octo generates the PMTiles, writes the style and delivers to staging for review.

  • Dataset becomes a single checked file
  • Style with the classes you approved
  • Inventory of pages affected by MapLibre 6
Benefit: a map with no map server to maintain
2 Next

Audit before each publication

Style and tiles always go through the same check, and the new orthophoto is tiled with counts and a sample.

  • Style audit against metadata
  • Tile size heat map
  • gdal2tiles routines migrated
Benefit: the blank map is caught before the user sees it
3 Later

Live layers and scheduled datasets

Cadastral records and public works served from PostGIS the same day, and reference datasets regenerated on a schedule, with a summary read by Octo in the morning.

  • ST_AsMVT functions with a public view
  • Scheduled regeneration that stops on drops
  • Log of version and date for each publication
Benefit: the map keeps up with the data without anyone having to remember
05

Confirmed by sources.

Every point below has a source published by the responsible body (Planalto, IBGE, the Brazilian Army, CONCAR), by the project or by the standards organization. The sources are in the next section.

4

points with a published source, each with its reference alongside.

ConfirmedMapLibre 6 changed how it loads
In v6.0.0 (July 22, 2026) the distribution became ES module only, WebGL 1 was dropped and the maplibre-gl-style-spec package moved to version 25 (the style's version field is still 8), which warns on old expressions. The current version is v6.16.0, from October 25, 2026.Source: maplibre-gl-js releases (GitHub)
Confirmedgdal2tiles deprecated
In GDAL 3.13, gdal2tiles runs through gdal raster tile by default (available since 3.11); --legacy forces the old code and is expected to be removed in 3.15. Without --xyz, the order is TMS.Source: gdal2tiles and gdal raster tile documentation (gdal.org)
ConfirmedPMTiles and tile limits
PMTiles v3: 127-byte header, root directory in the first 16 KiB, MIME type application/vnd.pmtiles. tippecanoe limits tiles to 500K bytes and 200,000 features by default; the GDAL MVT driver uses a MAX_SIZE of 500000.Source: PMTiles v3 specification; tippecanoe repository; MVT driver (gdal.org)
ConfirmedOSM is not a free base map for everything
The tile.openstreetmap.org policy requires visible attribution and a proper User-Agent and prohibits bulk downloading, prefetching and offline use, with no availability guarantee. For offline or heavy use, the way to go is self-hosting or a provider that allows offline use.Source: OSMF Tile Usage Policy
06

What Octo does and what stays with you.

Octo prepares everything, but does not sign. The document of record stays with whoever is accountable for it.

Octo prepares

Surveys, calculates, organizes and produces the documents: spreadsheets, reports, sheets, maps and drafts.

Deliverable: material ready to check

Your team checks

The licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.

Step: review by the signer

Who signs

Octo does not sign. Designs, technical reports, ART/RRT (Brazil's professional responsibility records), accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the cartographic engineer or another licensed professional, with an ART; official data goes into the INDE only after approval by the competent authority.

Sign-off: licensed professional, with ART
07

Sources.

Project documentation and release pages, and IBGE services, accessed on October 31, 2026.

Your map on the web, with no server to look after.

The assessment starts with a map your team already publishes or wants to publish, without touching the official database. You get a proposal for what can be generated and checked by script, with a trial on a known dataset, and decide with it in hand.

Request an assessment