Service · WebGIS
Angular and OpenLayers: map applications built on reusable layers
A map is rarely the product. The product is the task around it: find a parcel, compare two records, draw a boundary, print a page with the right scale. I build map applications in Angular where OpenLayers is one layer in a structure that also holds forms, tables, documents and reports, so the map works with the rest of the application instead of beside it.
Discuss your project ↗- Start with
- A user task, data sources and map interactions.
- You receive
- An integrated workflow with clear state ownership and tests.
- Example
- GeoAtlas: my own Angular and OpenLayers product.
What I build
- Map composition. Views, layers, sources, styles and interactions as Angular components with inputs and outputs, over a map library with twelve entry points: geometry, file formats, drawing, printing and service clients.
- Data integrations. WMS, WMTS and vector services, cadastral and planning data, routing and isochrones from existing engines behind a same-origin API.
- Editing workflows. Drawing, snapping, validation and permissions as one complete path from loading the data to saving a valid change, with an editable draft kept apart from confirmed server data.
- Attribute tables, reports and printing. The shared data grid over map features, reports built from several public sources, a print editor with a live page preview.
- Phones and accessibility. Phone layouts and wizards beside the desktop workbench, touch-friendly controls and keyboard paths for the agreed workflows, checked in the actual interface.
Why a library underneath
A clear map boundary makes ownership and lifecycle testing easier to reason about. That boundary can start inside one application; extraction into a library is useful when the API and reuse justify it. In GeoAtlas, the map library has a neutral API while the application adds language, domain integrations and product decisions.
Evidence
GeoAtlas is my own map portal for Poland, with parcel search, reports, printing and a documented feature inventory informed by the national geoportal. The case study includes screenshots, dated test evidence, deliberate differences and scope limits; it does not claim to replace the official service. the OpenLayers article explains the decisions behind the integration.
Ways to work together
- A review of an existing map integration: Angular version, data sources, interactions, where the map logic should live.
- Delivery of one stage: a map integration, an editing workflow or a data-heavy screen around the map.
- A second map product on the same foundations, for example a municipal geoportal.
How it starts
Describe the application, the data and the task your users need to complete on the map: contact@clearcraft.dev.