Help us improve Huwise
Improve filtering in lineage legend
Improve how reuses are showcased in a portal
Adding more visual customisation options in Studio would make it easier to create engaging, branded, and professional-looking dashboards—helping users deliver more impactful data experiences.
Allowing custom icons on Opendatasoft maps would greatly enhance the visual appeal and usability of spatial datasets. Branded or context-specific icons can make it easier for users to interpret map content at a glance, and are particularly important for government agencies that rely on standardised or officially mandated symbols for public-facing maps. Currently, to meet these requirements, some users are forced to export their data and build maps in external tools like Mapbox. Enabling native support for custom icons within ODS would reduce friction, improve design consistency, and help retain users within the platform.
We’ve observed that in Opendatasoft, when a parent portal is allocated a total amount of storage (e.g., 12GB) and a portion of that is assigned to a workspace (e.g., 10GB), the system still allows the parent portal to consume unused workspace storage if it exceeds its own allocation. This creates a risk where the workspace may not have access to its full allocated capacity when needed. A potential improvement would be to introduce a setting that locks or enforces the storage allocation between the parent portal and workspaces—ensuring that each environment can only use its designated quota unless explicitly reallocated. This would support more predictable and fair storage usage across teams.
Add two step verification at log-in for users with permissions to change things (i.e. those that can change data sets/pages etc).Maybe it could be an option even for those that have permission to browse data sets that are not public.This way, those who are concerned about security will feel a bit at ease.
I think a useful feature to help us manage our back office would be for the datasets section to allow us to filter by the Update frequency.
Add semantic search to search bar
Hello, When placing only strictly necessary cookies, the cookie consent banner is only displayed when clicking in the footer tab. I would like to have more flexibility in the banner management to be able to display the cookie consent banner - i.e for users upon their first visit - even if I don’t place cookies that require users' explicit consent.Thanks :)
Bonjour,dans le studio, lorsqu’on crée différents blocs dans une section, leur répartition en largeur sont fixes (si j’ai 2 blocs : chacun utilise 50% de l’espace, si j’en ai 3 : 33%, etc...)… Hors, si on veut présenter une page dans un esprit : KPI + graphique associé (donc sur 2 blocs à 50 % chacun), on se retrouve avec un très large KPI et un graphique très souvent trop petit du fait de la taille du bloc.Aussi, dans la partie “Disposition des blocs”, ne serait-il pas possible d’ajouter un paramètre qui permette de définir 1/3 - 2/3 lorsqu'on est sur 2 blocs et idem pour les configurations à 3 ou 4 blocs ? ou d’avoir un sélecteur de taille qui permettrait de redimensionner en largeur les blocs pour une répartition plus agréable ?Bonne idée… non ?Amélie Auto-translation 🪄Hello, in the studio, when we create different blocks in a section, their width distribution is fixed (if I have 2 blocks: each uses 50% of the space, if I have 3: 33%, etc. ...)… However, if we want to present a page in a spirit: KPI + associated graph (so on 2 blocks at 50% each), we end up with a very large KPI and a graph very often too small due to the size of the block. Also, in the “Block layout” section, would it not be possible to add a parameter which allows you to define 1/3 - 2/3 when you are on 2 blocks and the same for the configurations 3 or 4 blocks? or to have a size selector which would allow the blocks to be resized in width for a more pleasant distribution? Good idea… right? Amélie
I would like to see an enhancement to help improve stakeholder engagement and interaction. Specifically, a mechanism for stakeholders to register their interest against datasets, upcoming plans etc —similar to a ‘like’ or ODS Community “upvote” button. This will allow better visibility of stakeholder interest and will help identify which datasets, maps, or charts are most relevant to stakeholders.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK