🎉 New features

• We've added automatic room detection to the platform 🤖💪. You can use it in the mapper to create polygon assets by enabling the "One click rooms" option. It will soon be added to Smplr.js for programmatic use in your apps.

• The polygon data layer now supports polygons with holes. See "coordinates" in the polygon layer docs for details.

• We've added a new GeoJSON export to the mapper, similar to the CSV option but where each asset includes a valid GeoJSON feature. This option is usable only for geo-referenced spaces, i.e. spaces that have been located on the map.

• We've added doors and windows to the GeoJSON exported files.

• We are now supporting IMDF export, making our spaces compatible with Apple Maps and a range of other solutions.

💅 Improvements

• The app's domain is now automatically considered an authorized domain, making it easier to use the mapper.

• It is now possible to set a space to be loaded using the experimental performance mode by default. Get in touch if you have a large space you'd like to test this on.

🐛 Bug fixes

• We now make sure point and icon data layers are rendered above furniture in 2D mode.

• We've fixed an issue where the hover state of data layers using named colors was broken. And we've taken the chance to improve safety in color usage across the whole codebase.

• We've fixed the render of railing poles that were missing.

📚 Documentation

• We've added dead link detection to the docs, so no more broken links ;).

⚙️ Groundwork

• Under the hood, we've reworked a lot of how the application state is stored to allow for more flexibility around authenticated and unauthenticated sessions. This will enable the possibility for embedded editor usage in the near future.

• We've upgraded our backend integration to our authentication provider and our login related dependencies to ensure security best practices are up to date.

• We've upgraded our rendering engine to the latest version, paving the way for performance improvements.

💅 Improvements

• Numeric color scales now have an option to treat zero as missing data. More details in the docs.

• We've improved the sample space for future accounts so that it works better with the furniture in 2D mode.

• Report stat groups can now have their own title.

• The reports leaderboard component now support both top and bottom sections.

• We've improved the cross-tables alignment in the level explorer report template.

⚙️ Groundwork

• Usage metering has been updated according to the new pricing.

🐛 Bug fixes

• We've fixed onClick handlers for mobile viewers.

🐛 Bug fixes

• We've fixed the onDrag and onDrop handlers on data layers, which stopped working after yesterday's release.

• We've improved the reliability and consistency of hover and click states on data layers.

🚧 WARNING 🚧
We're now enforcing clientToken match for all requests, finalizing an upgrade to the security of your data.

🎉 New features

• We've started work to support furniture in 2d mode, at last 🎉! This has been a highly requested feature for a while and we're happy to put up the first wall, so to speak. Currently supported: tables of all shapes, chairs, desks of all configurations, shelves, and cubes. Your existing furniture data layers are 100% compatible with the 2D mode out of the box.

• The first (alpha) version of our map viewer built on top of Mapbox is out and available through smplr.js. Render your geo-referenced buildings on a 3D map in 15 lines of code, including worldwide 3D cities created from OpenStreetMap data. Welcome to the new era of Smplrspace 🌆. Check out the docs and contact us to try it.

• We've added a QueryClient API to retrieve the automatic ground of levels programmatically. See the docs.

• You can now extract all floor plates in a single click in the mapper, using that new API 👆. Just create a polygon group and click the "..." button to try it.

• We've added APIs to QueryClient to programmatically extract doors (docs) and windows (docs) with all their details from the space.

• We've added automated doors and windows extraction in the mapper, using these new APIs 👆. Just create a polyline group and click the "..." button to try it.

• The level explorer template for reports now supports a slider filter when using numeric statistics.

• You can now choose to hide the level picker via smplr.js. See hideLevelPicker in the docs.

💅 Improvements

• The onClick, onHover, and onHoverOut handlers now include the triggering Javascript event as argument, to allow for custom integrations. More details in the docs.

• We've improved the detection of features not supported by browsers, and their associated error messages.

🐛 Bug fixes

• We've fixed an edge case where the full preview button would fail if the preview was not already opened.

• We've fixed an issue where the getElementPositionOnScreen function could return a slightly offset position in 2d mode.

• We've fixed an issue where the hover and click handlers of data layers could be called unintentionally while moving the camera.

This version adds a number of new capabilities to the reporting feature that was first introduced in v2.10.0.

🎊 New reports features

• You can now aggregate data from multiple sources, making it possible to configure all-in-one management reports.

• We've added new statistic options: average, weighted sum, and weighted average.

• We've added a new template displaying a list of stats.

• The level explorer template now support multiple stats with in-page selection of the active stat by users.

• We've added support for on-the-fly stat selection for the data visualization in reports.

• We now support multiple data layers on a single report page.

• It is now possible to use point data layers.

• We've added support for numerical color scales in the reports.

• It is now possible to map multiple assets to a single spreadsheet line.

💫 Improvements to reports

• We've updated the summary cards to support a large number of categories.

• We've reworked the navigation between pages to allow for more complex reports.

• Each page of a report now has its own url, making it easier to share a specific data view.

• We've improved the loading state of report pages, removing the flash of white between page.

🎉 Other new features

• startViewer now returns a Promise, letting you react when the scene is ready without providing an onReady callback method. This is to adapt to different types of environments (e.g. Observable notebooks), or coding preferences.

• You can now programmatically switch between 2D and 3D modes without restarting the viewer with the new setMode API. See the docs.

• We've added an API to remove all data layers at once, a reset button of sorts! See the docs.

• It is now possible to auto-rotate the viewer for display purpose. More details in the docs.

• You can now programmatically compute the ground footprint of a piece of furniture. Ideal for alternative visualizations, or to compute the area taken by specific furniture classes. See the docs.

• New keyboard shortcut for you power users! Shift+D will duplicate doors, windows, and furniture pieces in the editor.

• We're added automatic classification of facade walls, to make it easier to add custom models as facade and in preparation for experimental performance features relying on facade-only rendering for hidden floors.

• An experimental performance mode is in private alpha. We're looking at bringing the viewer to the next level of rendering performance, with a focus on not-necessarily large, but dense & complex multi-storey buildings.

💅 Other improvements

• We've improved the rendering of point data layers in 2D mode.

• We're now making sure that data layers are fully managed in 2D mode.

• We've improved consistency of the loading state of the viewer and you can now provide an optional message to be displayed when the space is loaded but still rendering. See the docs.

• We've added statistics about your space in the right pane of the editor below the publish button. This gives you (and us) some useful information to debug performance related issues.

🐛 Bug fixes

• We've fixed the free rotation of furniture while pressing the shift key, in the editor.

• We've fixed an issue where reports that had no data for a given space where also displayed in the list.

• We've improved the consistency of the timing when the scene ready event is emitted. In some cases, it was emitted too early, it's now all good.

• We've fixed an issue where the onClick event on furniture data layers would sometimes be triggered one too many times.

📚 Documentation

• You can now Ctrl+K to activate the search in the docs.

No new feature today, but this release is a big one as it significantly improves the behavior of our viewer and data layers in 2D mode, as well as for spaces that span a very large area.

See below a before/after of an extreme case — a space spanning 700m by 460m 🤯.

💅 Improvements

• We've completely reworked the 2D mode of the viewer and it now renders spaces of all sizes without flickering.

• Data layers in 2D mode are now fully managed in height/elevation, to make it much simpler to use and predictable in rendering.

• Data layers in 3D mode are now automatically positioned in height/elevation if their value is so low that it would be hidden under the ground.

• We've made sure that walls are always rendered higher than grounds and ground level data layers, making car park data viz (e.g.) much easier to achieve and predictable across space sizes. It's a trade-off with rendering of extremely large spaces, but will make the behavior more predictable for 95% of the users.

• We've improved the default behavior of ground types so it's simpler to overlap different grounds, but still provide full control in cases where it's needed.

• We've improved the rendering of structural walls so their size match exactly the size of non-structural walls they overlap.

• We've improved the performance when using subspace rendering, by not rendering non included levels at all. They used to be hidden, now they're gone 🙈.

• You can now pass color values with their CSS names, like 'cyan', in the data layer color options.

🐛 Bug fixes

• We've fixed an issue that could sometimes lead to an unintended "flash" effect when clicking the info link in the viewer.

• We've fixed an issue where stairs were missing in 2D mode.

• We've fixed the handling of ranges of levels to include using ~ in shared space links.

• We've fixed an issue with 2d rendering with thick grounds.

• We've fixed a bug that would crash the viewer if it was passed elements that don't have a position or coordinates. They're now ignored.

🎉 New features

• Our first step towards subspace rendering is live. You can now specify which levels to include in the viewer. This is available through smplr.js, either when you start the viewer (see includeLevels in the docs), or dynamically after the viewer has started (docs). It's also possible to use this feature on shared space links by appending the (zero-based) level indices to include to url: /0 for the first level only, /0-3 for the first and 4th level, /0~3 for the first to the 4th level, or any combination of these.

• We have added the possibility to update the viewer's renderOptions dynamically, letting you adapt the way the space is rendered based on the data visualization needs you have. This lets you move from a data only view to a normal view instantly without restarting the viewer. See the docs for details.

• You can now disable grounds from the rendering (see grounds.render in the docs).

• You can now pre-navigate the viewer to a certain level when you start it (see topShownLevel in the docs).

• We've added synchronous equivalents for each asynchronous function in QueryClient. This relies on our caching and requires pre-caching the space data, but make it much easier to implement batch compute queries by mapping arrays, or similar. See the docs for details.

🐛 Bug fixes

• We've fixed the point layer shape being cube instead of sphere as default.

• We’ve fixed an issue in the numeric scale where the input was not properly clamped to the scale’s domain in case a decimal gamma value was set. Highly specific? yes. Solved? yes.

This is another big release on the tail of v2.14.0. A number of you have already got a preview of our heat maps capabilities and have asked (quite impatiently 😉) when the official API would ship. The answer is today ! And it's not coming alone, but alongside our new and shiny color scales, to help you bring best practices from color theory into your data visualizations.

🎉 New features

• We've added the highly awaited heat map data layer API. You can now render heat maps in just a few lines of code. The grid is automatically generated and configurable. It is also masked automatically by your space's footprint, but you can provide a custom polygon mask to use instead. Interpolation is done out of the box, with a smart confidence range computed based on the relative location of your data points, but you can also set the confidence range that makes most sense to your use-case. Heat maps come in a few configuration styles: spheres, grid, and bar-chart, with potentially more to come based on users feedback. Check out the docs for the API reference and a live demo with code, or play around with the options without code in our timeheat demo.

• The point data layer is getting better, with shapes! You can now choose which shape you want each point to be rendered as. We're starting with spheres (the historically single option), and cubes of any size. More shapes will be added based on demand. Details in the docs.

• We've added a Color utility class to smplr.js, which lets you easily create gorgeous looking color scales that are optimized for spatial data visualization. It also provides a legend component for react or vanilla javascript, and utility methods to convert css colors into the approximate color you visually see in a Smplrspace viewer when you use them. More details in the docs. Tip: that "A little context" section is a great read. Or go play with it in our colors mini-site.

💅 Improvements

• We've added a hello world example to the doc in which smplr.js is loaded from CDN.