From scattered files to connected information
Bring plans, spreadsheets and burial records into one map instead of switching between sources.
SKYLENS · CEMETERY MAPPING
Every grave located. Every record connected.
A digital cemetery map connecting grave locations, headstone images and burial records — helping your team find information, update records and keep knowledge in one place.
For cemetery managers, burial societies, religious councils and municipal operators. Not a public grave-search service.
Scattered records turn every search into a task.
From a record to a place on the ground
Connect burial details to a location and grave image so your team can find and review the right record.
From personal memory to shared knowledge
Keep information in the interface and update it over time, making knowledge accessible as team members change.
What do you receive?
A digital cemetery map
Grave locations on aerial imagery, alongside a 3D view of the headstones.
A searchable interface and database
Records connected to locations, with tools to search, review and update information.
An exportable data table
Names, locations and grave images for continued use and further work.
See the grave. Understand its surroundings.
The cemetery mapping process
From existing plans and records to a digital map and a database connecting each name with a location and a grave image.
- Review existing plans and records
- Define the mapping area
- Survey the site by drone
- Process the imagery
- Outline grave boundaries on the map — polygon extraction
- Build the software interface and database
- Update the database from the survey within the interface
- Export a data table with names, locations and grave images
Three service areas. One defined pilot.
Mapping
Capture and orthophoto, sections and rows, grave locations, paths and boundaries — within an agreed scope and quality review.
Digitization
Import registers, map fields, review duplicates, link locations and prepare an exceptions report for customer approval.
Software
Viewing, search and editing; local or cloud deployment at the customer’s choice, with training as specified for the pilot.
Start with one section. Build a foundation for the rest.
Start with a selected section, connect records to the map and agree on the deliverables and scope together. The pilot is a paid service with a tailored proposal.
What do we agree before starting?
Boundaries and sources
A defined area, grave-location and deceased-record limits counted separately; source files, coordinate system and permissions.
Deliverables and operation
A deliverable list with formats and transfer method; deployment, hardware requirements, licensing and training.
Approval and acceptance
A named authorized reviewer, review method, coverage, acceptance thresholds, review date and revision rounds — agreed before ordering.
Exceptions and continuity
Unresolved records and conflicts with a decision owner; backup, update and support terms. Full-site expansion is quoted separately.
A workspace that fits your organization.
Local or cloud deployment, with export, update and backup options.
Local or cloud deployment
Choose local or cloud deployment to suit your organization. Hosting, backup and support terms are defined for the selected plan.
Who handles backups and updates?
An optional data backup service can be added. Storage location, backup frequency, retention period, restore testing and cost are defined in the proposal for the local or cloud plan.
How often is the data updated?
Update frequency is agreed according to the cemetery’s needs. For periodic updates, the cemetery provides burial records and locations, and we document them and add the information to the database and interface. Update scope and delivery dates are agreed as part of the service.
Match the data model to the burial type
Dense burial also needs building, floor, wall, row and cell identifiers. One grave location may link to several deceased records, so these are counted separately. An apparently empty space does not prove availability. Public maps, navigation and payments are not part of this launch offer.
Questions before you start
What source material is needed?
We review the available imagery, maps and registers and identify gaps. Do not submit burial databases through this form; project data will use an authorized transfer channel.
Who approves a record-to-grave association?
An authorized cemetery representative, named before verification begins. Visual or automated matching does not replace that approval.
How do we choose local or cloud deployment and export data?
The customer chooses local or cloud deployment. The specification defines the working environment, license, deliverables and export formats.
Who handles backups and updates?
An optional data backup service can be added. Storage location, backup frequency, retention period, restore testing and cost are defined in the proposal for the local or cloud plan.
How often is the data updated?
Update frequency is agreed according to the cemetery’s needs. For periodic updates, the cemetery provides burial records and locations, and we document them and add the information to the database and interface. Update scope and delivery dates are agreed as part of the service.
What remains after the service ends?
Rights, continued software operation, support and export options are defined in the agreement for the selected plan.
Ownership, export and handover
Records, layers, formats and usage rights are agreed before ordering.
Licensing and continuity
Software licensing is separate from data ownership. Continued use, support, backup, restore testing and updates require explicit terms.
Choose your next step
We will get in touch to learn about your cemetery, existing records and needs, and arrange a suitable demo. You can also share details to request a pilot proposal.