Resources
Technology and map sources
Credits and source links for the tools behind Ferrum’s maps and models.
Your location choices
The initial location prompt requests one device position and its accuracy only after you choose Continue. You can choose Not now and define the site yourself. A device fix does not establish a surveyed plot boundary.
- Place name: the lookup is ticked by default and you can untick it. While the box stays ticked, each coordinate you choose on this page during this visit is sent (latitude and longitude to 5 decimals) to OpenStreetMap Nominatim to fill locality, city, state and PIN code; unticking it stops this, and choosing Not now sends nothing. Nothing is sent before you tap Continue, and nothing is stored beyond this page visit. Your unticking is remembered for the page session only.
- Nearby buildings and roads: for a device-fix site, this context remains off until you separately enable it. The request sends the coordinate to OpenStreetMap through the Overpass API; your context choice is remembered in the browser.
- Maps: map providers receive the requests needed to display the area you view. Data-provider credits remain attached to the relevant map or context view.
OpenStreetMap data is provided by its contributors under the Open Database License (ODbL). The source explains its attribution requirements and service policies.
© OpenStreetMap contributors — copyright and licenceSoftware credits
Selected libraries used for maps, model viewing and rendering. Each project’s licence file contains its terms and notices.
Three.js
Interactive building and terrain views.
MIT licence and noticesthree-gpu-pathtracer
Progressive rendering for the Beauty view, where supported by the device.
MIT licence and noticesLeaflet
Interactive site maps.
BSD 2-Clause licence and noticesMapLibre GL JS
Map rendering.
BSD 3-Clause; additional bundled notices in the licence file licence and noticesweb-ifc
Reading IFC model files.
Mozilla Public License 2.0 licence and notices
Data and engineering evidence
Source availability, reuse terms and connection status are maintained in the data catalogue. Project requirements and engineering checks need their own evidence; a rendered model does not establish accuracy or compliance.
Read data sources and licences