Archaeology community
An archaeology community platform mapping Britain's finds with member dashboards and LiDAR-backed discovery tools.
01 / Project story
Finds, geographic context and LiDAR evidence are often scattered across specialist sources.
A map-centered community platform brings discoveries, member tools and LiDAR-backed exploration into one research experience.
02 / Product capabilities
Designed as part of a cohesive archaeology community experience, with clarity, reliability and practical use in mind.
Designed as part of a cohesive archaeology community experience, with clarity, reliability and practical use in mind.
Designed as part of a cohesive archaeology community experience, with clarity, reliability and practical use in mind.
Designed as part of a cohesive archaeology community experience, with clarity, reliability and practical use in mind.
03 / Benefits
Connects data with place
Supports community knowledge
Improves research discovery
04 / Trade-offs
Large map layers require optimization
Sensitive site locations may require protection
05 / Technology
The architecture for Relic Atlas was shaped around the product workflow, integration boundaries and long-term maintainability. Technologies are used for specific responsibilities rather than added only to make the stack appear larger.
Builds reusable, state-driven interfaces and keeps complex user journeys organized into maintainable components.
Runs the server-side JavaScript services, integration logic and non-blocking application workflows.
Presents location-aware data and spatial interactions in an understandable visual workflow.
Adds terrain and elevation context to geographic research experiences.
Interface, business logic, persistence and external services remain separated so changes are easier to reason about.
Validation and predictable contracts protect downstream workflows from incomplete or unexpected input.
Runtime limits, secrets, external dependencies and failure paths are considered as part of the implementation.
06 / Delivery approach
Understand the users, business objective and constraints.
Map the core journey and reduce unnecessary interaction.
Implement maintainable interfaces, services and data flows.
Test behavior, responsiveness and failure paths before release.
Project by Sandipan Das