05NUMBER
FIVE.
DE/ENContact
Menu ＋
Number Five /

06 / PROJECT

Charts for existing plotters

Converting our own vector data into other chart formats. A path is open; the work continues.

Interoperability research · unfinishedUpdated: 1 November 2026
A closer chart view
Detailed view after a native zoom step in MAP 110. NOAA S57 Boston dataset; current app capture, not a current nautical chart service or a speed measurement.MAP110 ·0.5.42-memory-budget-v8 · Lumina K706 · Android10 ·2000×1200

01 / STARTING POINT

What we wanted to solve.

Must a chart source be limited to our own app? We investigated whether legally usable vector data can also be prepared for existing plotters and their chart paths.

WHAT THIS COMPONENT MAKES POSSIBLE

The practical difference.

Our chart work can also become useful for existing equipment. Each target plotter needs its specific format or an interface it actually supports.

RX5/Lighthouse and Navionics are explored as separate conversion paths. Existing writers and examples solve parts of the problem. Complete portrayal, target-device testing and rights to each input dataset remain separate tasks.

Read the decision in the story

02 / DEVELOPMENT

Our path to getting there.

Our intermediate representation keeps geometry, attributes and provenance together. Supported target structures are generated from it and independently read back.

For Lighthouse/RX5 we developed conversion, regional export and inspection tools. For Navionics we investigated self-authored small containers, geometries and later broader adapters.

Each step distinguishes file generation, reader acceptance, actual portrayal and use on a plotter. Those are different kinds of evidence and are not interchangeable.

03 / RESULTS

What exists today.

  • The conversion work has its own source tools, a documented intermediate representation and checks for supported target structures.
  • Genuine reader admission and geometry readback are documented for specific self-authored Navionics test containers.
  • This is a technical foundation for further adapters, not a finished universal-format product.

Images show the development revisions identified in their captions. Today’s source may be newer than an existing image.

CURRENT PHYSICAL DEVICE CAPTURES

The controls today.

Direct captures of the installed apps. Captions identify device, version and data source; a displayed measurement is only as strong as the source described there.

Boston Harbour on MAP 110
Current device capture on 1 November: NOAA Boston charts rendered locally on the Lumina. The chart dataset was accessed on 3 October; position outside the chart area, other header data simulated or unavailable.MAP110 ·0.5.42-memory-budget-v8 · Lumina K706 · Android10 ·2000×1200
Earlier development revisions and designs ＋

These images explain the development journey. Historical test views and designs are separate from current device captures.

Custom chart rendering · Cream
Boston from NOAA ENC data, rendered for chart study revision 05. Experimental rendering on the development host; not a completed navigation acceptance.

04 / REPRODUCE

What you will need.

  • Own or appropriately licensed vector data with provenance
  • Python tools and a clear understanding of supported feature and portrayal paths
  • A separate, lawfully accessible target environment for device testing
See sources and downloads

05 / KEEP BUILDING

What comes next.

Lighthouse/RX5 and Navionics remain unfinished. A general promise of any vector format on any plotter is not established.

Data rights, target-software terms and technical prerequisites belong to each use case. Third-party charts, keys and proprietary libraries are not distributed as our own sources.

Here is where you can help.

Help with open test data, reproducible format descriptions and specific device experiments.

Write to me

The foundations we build on

OpenCPN IHO Standards
← All projectsOur own sonar