Regenerate an already monitored site, and a slimmer Report Builder
In the Regeneration section you can now start a regeneration on a site you already have under monitoring, recognising it from the satellite preview of its perimeter. In the Report Builder the area above the document shrinks to a single bar, the data labels are readable again, and sensor data loads far more reliably.
New Features
5 updatesStart a regeneration on a site you already monitor
sito-esistente-in-rigenerazioneIn the Regeneration section, the window you use to create a new site now offers an opening choice between two ways of working: create a brand-new site, drawing or uploading its perimeter as you have always done, or start from a site you already have under monitoring. Until yesterday, in order to follow the regeneration of an area already present in the platform, you had to recreate it from scratch: redraw the perimeter, fill in the descriptive data again and end up with a second site telling the story of the same area twice. Choosing "Use an existing site" makes the path far shorter, because the perimeter and the data stay the ones the site already has and the procedure jumps straight to the two steps that genuinely matter: assigning the Grower and listing the plants that were put in the ground. The list of available sites shows the name and the surface in hectares for each one, and marks with a badge those that are already followed in regeneration, so you never risk starting the same work twice. Once you have picked the site and completed Grower and plants, the "Start regeneration" button closes the procedure saving only the new information, without duplicating or altering what was already there. If something does not go through, the window stays open and lets you try again without starting over, and the new attempt repeats only the part that had failed. The classic way of creating a brand-new site is unchanged, so there are no habits to relearn when that is what you need. You will find the new option under XNatura → Regeneration → Map → New site, at the first step of the procedure on a computer.
A perimeter preview on the map, and picks you can undo
anteprima-perimetro-sito-esistenteChoosing a site from a list of names is not always enough to be sure you have taken the right one, especially when the names look alike or recall the municipality rather than the plot. That is why, in the procedure that starts a regeneration on an already monitored site, as soon as you select a site a small satellite map appears above the list, drawing its perimeter. The framing adapts by itself to the shape of the area, so you recognise at a glance whether you are looking at the row of trees, the wood or the meadow you had in mind, and you can also drag the map and zoom to check the surroundings. If the site you picked has no drawn perimeter yet, a notice appears in place of the map and says so clearly, so you immediately understand why there is nothing to see. We have also made mistaken picks undoable: clicking again on the site already selected deselects it, and the same goes for the Grower choice, both when you point to yourself and when you have searched for and selected a person. Before, a wrong click could only be replaced with another one, never genuinely undone, and getting back to a clean state meant closing and reopening the whole procedure. When you deselect, the button that leads to the next step switches off again, confirming that the step has gone back to incomplete and that nothing will be saved by mistake. They are two small details, but they take the hesitation out of the moment of choosing: you can try, look and step back. You will find them under XNatura → Regeneration → Map → New site, by choosing "Use an existing site".
Bug Fixes
5 updatesThe data labels in the Report Builder are readable again
barra-report-piu-leggibileThe top bar of the Report Builder holds the pickers that state which data the document you are writing refers to: the organisation, the site, the perimeter and the land-use class. On wide screens those pickers were squeezed down to showing one or two letters of the chosen value, because the label printed inside them ate half of the available space and the buttons on the right took the rest: the result was that you could not read what you were working on. The labels are no longer printed inside the picker, but appear in the tooltip you get by hovering over it and at the top of the menu that opens on click, where they are highlighted in colour. All the space freed up goes to the value, which now has almost twice as many characters available and in most cases reads in full. The report's name has more room too and is truncated far more rarely. The buttons on the right have been lightened: history, AI generation and preview stay as icons, with the name of the action in the tooltip on hover, while the action that completes or reopens the report uses a short wording, with the full sentence in the tooltip and in the confirmation window. The only label still written out is the one for the land-use class, because its value alone would be hard to interpret. There is nothing for you to do, the fix is already active for everybody: you can check it under XNatura → Monitoring → Site → Report, by opening a document in the Report Builder.
Improvements
5 updatesA single bar above the document, instead of four
barra-avanzamento-report-unicaAbove the writing area of the Report Builder up to four full-width bars could pile up — the invitation to regenerate the contents with AI, the notice about blocks still to be generated, the warning about blocks too long for the page and the document's status — and together they ate a serious slice of screen before you got to see the document at all. We have gathered them into a single slim row, far shorter, which disappears entirely once the report is complete and there is nothing to flag. The document's status has stopped being a bar and has become a pill next to the report's name, with the actions to complete it or reopen it moved into the top bar: that way it takes no vertical space at all. We took the opportunity to make the money side more transparent: the button that generates the missing parts in bulk stays inactive until the estimated cost is available, always shows the cost and the remaining credit, and when the credit is not enough it explains so in the label itself, stating what you have and what would be needed. Before, with the estimate still in flight, that button could look clickable while the price was not visible. Closing the bar no longer hides the figures either: it collapses into a pill that keeps showing cost and credit, and the numbers are never truncated, while the prose around them is. The warning about over-long blocks has become actionable, with a link taking you straight to the block that needs sorting, and the counters now clearly tell apart the texts actually generated from the processing merely started. You can see the new bar under XNatura → Monitoring → Site → Report, by opening a document that still has parts to generate.
Sensor data loads far more reliably
sensori-caricamento-piu-stabileThe pages showing the data recorded by the acoustic sensors — the sound spectrum, the density maps and the pollinator activity charts — have to sift through large amounts of recordings, and over very wide time ranges the answer can take several tens of seconds. When one of these requests failed to complete within the expected time, the platform automatically repeated it several times, and those repetitions ended up slowing down the other parts of the page too, which had nothing to do with the sensors. A request of this kind that does not go through is no longer fired again and again: you are told straight away, so you can narrow the analysis period and try again without the rest of the page suffering for it. On top of that, data already downloaded is reused for a few minutes: if you move from one tab to another and then come back, or reopen the same detail, the view reappears immediately instead of redoing all the work from scratch. We have also fixed a double load in the Census section: when you chose the year, the requests went out a first time with no date limit at all — asking for the whole history — and a second time with the correct period. The selected year is now applied immediately, so every request leaves with the right range already in place and the data arrives much faster. As a welcome side effect, changing the perimeter version without changing the year no longer clears the date filter you had set by hand. There is nothing to do to benefit from it: open XNatura → Monitoring → Census → Sensors and you will notice the difference on the very first load.