🎉 New features

• Improving on the "layers" release from the previous version, we're now automatically tagging walls that are part of the facade of a space with the built-in "smplr_facade" layer. See walls.includeLayers in the docs.

• You can now set the status of a space programmatically. It's useful to publish it after creating it for the embedded editor, or to archive it when your own resources are archived or deleted. More info in the docs.

• Similarly, you can now delete a space programmatically. See the docs.

💅 Improvements

• The map viewer now displays a marker on the roof of each smplrspace building.

• Icon data layers now support passing in the icon parameter as a function, making it much easier and quicker to render data driven icon sets. Learn more in the docs.

• We've added an API to take a screenshot to a Javascript file, making it easier to upload screenshots to your own backend. See the docs.

🐛 Bug fixes

• We've fixed a bug where dotted polyline layers with animations would not follow the levels visibility and we always visible.

• We've fixed the level picker up/down buttons when opening a space with multiple selected levels.

• We've fixed an issue causing the annotations toggle in the viewer to not appear.

⚙️ Groundwork

We've setup an image processing backend that let us store high resolution images and request custom sizes that are fit for purpose, so thumbnails load quick, full screen previews are sharp, and everything is optimized for caching ⚡. It even lets us request retina display images based on the user's device. It is already being used on space preview images — you can go update the preview image from the Settings page in the space profile to take advantage of this. This is setting the groundwork for our upcoming image walkthroughs feature, stay tuned!

🥞 Introducing "Layers"

You can now mark any feature (wall, ground, door, equipment, etc.) of your spaces as part of one or more layers. It's a text-based tags system, customized on a per-space basis, directly in the editor. And it comes with accompanying viewer options that let you choose which layers to include or omit, on a per feature-type basis (see the docs). This gives you full control over which part of your spaces you want rendered or hidden.

Why would you need this? It can be used to render spaces with varying levels of details to match the different datasets you're visualizing. You can control what's visible to a user according to your own role-based access control. It also offers a technique to improve performance on complex spaces that do not always require every details rendered.

🎉 New features

• The entity manager can now be used as data source for reports. This is useful for simple, inventory-type, reports that list equipment and do not require time-based updates, or extensive amount of data imported from a 3rd party system.

• The levels explorer report template now supports point and polyline data layers, on top of the existing polygon layers. This means you get an overview of all your managed equipment across the building, whether it's an electrical room or a access point card reader.

💅 Improvements

• Our tree shaped category filter now supports both top level and nested categories.

• Reports now support multiple "primary" data sources, meaning you can apply filters across data sources of different types at the same time. This is useful for inventory type reports where (e.g.) polygon and point assets are rendered and can be filtered together.

• We've fine-tuned the atmosphere color in the map viewer so it fits better with the viewer colors.

🐛 Bug fixes

• We've fixed the statistics next to "All spaces" so archived spaces are not counted anymore.

• We've fixed the statistics next to "All projects" so spaces from deleted projects are not counted anymore.

• We've fixed an issue where the map viewer would crash if the first loaded space of a group was shorter than the other spaces.

🎉 New features

• The map viewer has a new type of data layers: Open Street Map buildings, making it really easy to build city-wide data visualization using 3D buildings from the best open data source in the industry. Learn more in the docs.

• You can now add a "space shell" data layer to the map, where each element is a space from your Smplrspace spaces rendered as an interactive and colored extruded polygon outline. Details in the docs.

• Space shell layers are also available in project reports, ideal to showcase surrounding buildings to your project of focus.

• The geopoint data layer now has a label option to add text permanently visible on top of the marker. See the docs.

🐛 Bug fixes

• We've fixed an issue where floor to ceiling window where not rendered at the good height in the map viewer.

💅 Improvements

• The “stairs” now have a grey color option, especially useful for ramps that should match the ground color.

• We've improved the color processing on report tags so the relative differences between colors is maintained on the whole brightness spectrum.

🐛 Bug fixes

• We've fixed the name of levels in a map-based project report.

• We've fixed a bug where sorting items in one report template crashed the app.

• We've fixed an issue were polygons would be corrupted in the entity manager after the were dragged.

• We've fixed an issue where unmapped polygons would show as mapped but empty after exporting and re-importing to CSV in the entity manager.

🧑‍🔬 "Projects" enter private beta

Smplrspace Projects, our new experience bringing multiple spaces on the map for campus / portfolio reporting is being opened to the first few users. It's too early to make it generally available, but get in touch if you want to give it a test run.

🎉 New features

• The map viewer has so far been rendering "space" data layers, i.e. layers for data that is compatible with our space viewer. It's now getting its first "geospatial" data layers, i.e. layers for GPS-based coordinates that are compatible with other map providers and geospatial tools. We're starting with the geopoint and geopolygon layers, more will follow.

• The map viewer is inheriting the picking mode from its sibling, the space viewer. So you can now get coordinates for clicks and build the same type of custom mapping experience in your app, but for geospatial data.

🔐 Security

• We've had to add data: to connect-src in the CSP in order for the new icons to load. Check the docs.

🎉 New features

• The map viewer now support basement rendering. Not easy digging the ground on a map, but we managed ;).

• The map viewer is getting its own control buttons, very much aligned with the (refreshed) space viewer's, so you feel at home.

• We've added option to the map viewer to hide navigation buttons, the level picker, or all controls. See the docs.

• We've added programmatic zoom methods to the map viewer. See the docs.

• Control button can now be positioned in 6 locations programmatically (see the docs). And we're opting for right side, vertically centered in our app.

• There is a new option to hide controls (see the docs).

• We've added a hierarchical "tree-shaped" filter for categories in the reports. This is useful for the visualization of large inventories of entities.

• You can now search your spaces by characters in their address or country.

💅 Improvements

• We've redesigned the controls of the space viewer, making changing levels, and switching between 2D and 3D modes easier. They also look nicer ;).

• The powered-by bar is also more sleek and simpler.

• The different types of grounds are now rendered properly in the map viewer, taking our space and map viewers a step closer to feature parity.

• We've simplified the experience in the levels page of the space profile.

🐛 Bug fixes

• We've fixed an issue related to the clean up of data layers in the map viewer. No more stale layers that stick around!

• We've fixed the "We could not publish your space" error in the embedded editor.

• We've fixed an issue where the background color in the viewer could not be updated via renderOptions.

📚 Documentation

• We've fully documented the custom helpers available in our handlebars based tooltipTemplate. Check it out here.

• We've added a note to the docs on how to embed Smplrspace in a Next.js app. Check it out here.

⚙️ Groundwork

• We're baking a whole new part to the app: Smplrspace Projects. It will allow users to bring in multiple spaces into a project, render them on the map, connect data for campus / portfolio level reporting, and more to come. Stay tuned.

🎉 New features

• We now support manually positioning labels in reports, which combined with persistent tooltips can help create overviews laying out all information on the space.

• There are a number of new options to customize the user experience in reports: choose between 2D and 3D mode, select a default level, set the initial camera placement, opt-in to reduce motion when filtering levels. These all help to create reports that give users exactly the most useful view in a single click.

• Reports now have a built-in screenshot feature to easily download the visualization to a file, to be integrated in presentations, reports, or to be printed.

💅 Improvements

• You can now edit the shape of mapped entities (polylines and polygons) in the entity manager.

• Entities mapped with "one click rooms" are now automatically set as done, making mapping of long lists quicker and more seamless.

• The automatic selection of the next entity when mapping entities is now smarter, it doesn't select already mapped entities and loops back to the start if needed.

• The desk cluster tool and the seminar seating tool have been integrated into the equipment catalog, fitting better with users workflow when furnishing a space.

• The equipment catalog interface in the editor has been refreshed a little.

🐛 Bug fixes

• We accidentally removed space.getDefinition from the APIs. It is back. Learn more in the incident status report.

🎉 New features

• The first data layer support has landed in the map viewer, with strong API compatibility with the space viewer — so you build once, apply everywhere. The polygon layer is done, more will follow. Learn more in the docs.

• The reports now support using the map viewer instead of the space viewer, paving the way for portfolio reports in an upcoming release.

🐛 Bug fixes

• We've fixed an issue where the camera placement would not be cleared when editing the space location, resulting in a potentially confusing experience if a space was moved far from its initial location. It's more seamless now.

⚙️ Groundwork (and nerdy)

• We've completely reworked the state management of the map viewer to better position us to build features easily, quickly, and reliably.

🎉 New features

• The "pre-release" version of the space profile's "Levels" page is here. There is a lot more in the works for this page, and level-based features in general, but this already lets you explore levels separately and get a public link to a single level.

• We've added an automatic option to set a level's initials, when renaming the level.

💅 Improvements

• Tags are now sorted by color in the picker to make it easier to organize them by "categories".

• We've added options to report templates to help make the reports lighter in data presented on screen.

• We've cleaned up the docs and types after the deprecation of the skybox.

• We've added the number of levels to the space profile.

• We've simplified the handling of colors when configuring templates.

• We've made filtering and sorting optional in some report templates.

🐛 Bug fixes

• We've fixed an issue where the space size didn't update properly once the data is loaded.

• We've fixed an issue that led to color hue differences on point, and dotted polyline layers depending on if it was set as a string or a function.

• We've fixed the typing of setCameraPlacement, to include the updater methods as well.

• We've fixed a bug in the space viewer's setCameraPlacement, that could lead to the rotation being missed when updating the target at the same time.