How the tragic fire at Notre Dame will accelerate the adoption of laser scanning of historic architecture
On April 15th, 2019 the tragic fire at Notre Dame in Paris caused devastating damage to the famous 856-year-old cathedral. It’s a terrible loss to the cultural heritage of France and the entire world.
As France prepares to reconstruct the cathedral, the eyes of the entire world are looking in the direction of 3D laser scans of the building created back in 2015 by (now deceased) architectural historian, Andrew Tallon. The news, that this fascinating technology and it’s jaw-dropping 3D point clouds, will be most likely used for the potential reconstruction of Notre Dame has been mentioned in hundreds of newspapers, portals and blogs around the world.
None of the dozens of articles I’ve read says the obvious truth, that Light Detection and Ranging technology has been around for a few decades and instant scanning of complex structures is what it was made for. In fact, I’ve been doing an exercise of 3D mapping of the historic building interior at university as part of my land surveying classes nearly 15 years ago.
What strikes me is that the world has been very lucky to have enthusiasts such as Andrew Tallon (who was one of the initiators of Mapping Gotic France project), or Ben and Barbara Kacyra who founded non-profit organization CyArk. Disasters happen. Fires, floods, earthquakes, extremists blowing up ancient treasures… Without passion and effort of these people, the exact reconstruction of Notre Dame might have been much harder or impossible. Imagine how many historic sites have been lost forever…
As laser scanning plays a crucial role in the capture of 3D data critical to the preservation of historically important works of architecture and archaeology, why is the adoption of the technology still so low? Why LiDAR-based techniques and workflows aren’t pushed jointly by the academic communities in the history, architecture, archaeology and geodesy space? Why isn’t it widely funded by governments in the developed countries? Why isn’t it promoted or even required by UNESCO?
I hope that policy and decision makers had at least a slight concern when reading about Notre Dame fire… “Do our cathedrals have 3D scans available in the case of a similar accident?”. Perhaps this tragedy will be a key milestone in the acceleration of the adoption of laser scanning of historic architecture…
Building a Location Data Platform: Opportunities, Challenges and the Road Ahead in 2019
We’re in an incredibly exciting time in the location space, and in a critical moment for setting a course for this technology that avoids pitfalls and maximizes the potential for human benefit.
We’re approaching an inflection point in both in technological advancement and market demand. Technologies such as 5G and edge computing are promising better positioning accuracy and faster data processing. More industries and companies are relying on location to answer critical questions from where to open a new retail location, to how to predict real estate prices using traffic, to where your friends are and what the pulse of your city is.
Our lives and the ways in which we engage with the world are inherently local, and the more we can connect our digital lives to the real world, the more we can build personalized, engaging experiences that uncover new insights.
At Mapbox, this means 2019 will see continued investment into industries such as Social, Automotive, Augmented Reality, and Business Intelligence, working with partners from Samsung, to Porsche, to Facebook, and Uber as we continue to push the boundaries of innovation across location.
However, as a location data platform for developers, Mapbox takes seriously our guidance position in thinking about future product development — we need to keep in mind both the interests of businesses looking to harness location, in addition to the interests of their end users. As consumers are increasingly demanding more when it comes to ethical data collection from the products they use everyday, this means it’s more important than ever to maintain our orientation toward our north star of privacy for our customers and users. Location data is personal and sensitive, so it’s important that questions about user privacy continue to be debated, discussed and scaled as the location industry increases. Getting this right is crucial to making sure location moves in the right direction, and avoiding some of the mistakes we’re seeing today in tech.
What Data We Collect and Why
Device-collected location data is critical to constantly improving the mapping products we depend on every day. Mapbox SDKs collect encrypted, anonymous, and aggregated data about the map and device location so that we can help developers build better location-based applications. Anonymous sensor data helps find missing roads, determine road speeds and traffic, and classify biking and walking transit routes in cities. This data contributes to a better map of our world for users.
Minimal viable data footprint
We start by only collecting the minimal amount of data needed to improve our products. Nothing more. This includes information such as latitude, longitude, and elevation and we intentionally do not collect information that is personally identifiable. We specifically do not record advertising identifiers (IDFA on iOS, AAID on Android), so the data cannot be employed for advertising.
Encryption, Anonymization, and Aggregation
For the data that we do collect, we segment trips into 2-3 minute long traces, discarding the beginning and end of each trace, as well as data that looks like it’s from residential dwellings. This leaves us with many short segments that we then only use in the aggregate, meaning the resulting data is useful for detecting traffic conditions, but useless for identifying individuals.
We also ensure all data collected is double encrypted, both as it’s transmitted and also when it’s stored. We ensure this is done using widely adopted libraries that have been independently audited for security.
Honest Data Collection and Consumer Opt-out
Trust is at the forefront of conversations related to user privacy and users should feel they can trust the application developers and 3rd party services that collect their data. We believe that the reason for collecting user location data should be disclosed in a clear and unambiguous way to those providing that location information. This allows users to make informed decisions about whether to opt in or out of data collection, and developers who use Mapbox SDKs are required to provide their users with the ability to opt out of location collection.
We also believe that companies should provide value to their end users for the location data they collect. This is why Mapbox maintains a minimal viable data footprint when it comes to the data we collect, only collecting the data we need to improve our and users’ products.
Implementing the principle of least privilege – where staff are given access only to the resources they need to carry out their roles – is a priority for any world-class security team. Having a security team in place is a prerequisite to handling location data responsibly. Carefully designed access control limits risk. We carry the principle of least privilege through our onboarding and offboarding processes, and include instrumentation to deter unexpected attempts at access or privilege escalation. We believe this type of risk-management process will be increasingly adopted by more companies using location data in 2019.
How data is used matters just as much as how it’s collected, and the future of location promises exciting use cases, as long as companies continue to prioritize building with empathy, preventing misuse, and adding value for customer, end users, and the world.