From 07fcd073c2992f29cd986efbe5699e5b050443a2 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Tue, 17 Feb 2026 09:22:06 +0100 Subject: [PATCH 01/13] DWB release for Egest API --- .../dataworkbench/news/recent-releases.md | 4 ++-- .../dataworkbench/news/releasefeb26trd.md | 23 +++++++++++++++++++ sections/dataworkbench/toc.json | 4 ++++ 3 files changed, 29 insertions(+), 2 deletions(-) create mode 100644 sections/dataworkbench/news/releasefeb26trd.md diff --git a/sections/dataworkbench/news/recent-releases.md b/sections/dataworkbench/news/recent-releases.md index 9bdae711..400887d7 100644 --- a/sections/dataworkbench/news/recent-releases.md +++ b/sections/dataworkbench/news/recent-releases.md @@ -7,11 +7,11 @@ description: This is an overview of recent releases of Data Workbench and Data P ## Recent Data Workbench changes +1. [February 2026 third release](releasefeb26trd.md) 1. [February 2026 second release](releasefeb26sec.md) 1. [February 2026 release](releasefeb26.md) 1. [January 2026 second release](releasejan26sec.md) 1. [January 2026 release](releasejan26.md) -3. [December 2025 release](releasedec25.md) ## Recent Data Platform changes @@ -22,8 +22,8 @@ description: This is an overview of recent releases of Data Workbench and Data P 5. [February 2025 release](dp-releasefeb25.md) ## Recent API changes +1. [February 2026 third release](releasefeb26trd.md) 1. [January 2026 second release](releasejan26sec.md) 1. [January 2026 release](releasejan26.md) -1. [Platform July 2025 release](dp-releasejul25.md) The latest API specification is available through our [API Explorer](https://developer.veracity.com/docs/section/api-explorer/76904bcb-1aaf-4a2f-8512-3af36fdadb2f/developerportal/dataworkbenchv2-swagger.json). \ No newline at end of file diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md new file mode 100644 index 00000000..e4d1910f --- /dev/null +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -0,0 +1,23 @@ +--- +author: Veracity +description: This is the changelog for the February 2026 third release of Data Workbench. +--- + +# February 2026 third release: Egest API + +To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. +An additional filter is now applied to the Year column, ensuring data before the defined cutoff years is no longer returned. + +## Cutoff Rules Applied +* Compliance Data Quality MRV EU (OVDQ MEU): Year ≥ 2025 +* Compliance Data Quality MRV UK (OVDQ MUK): Year ≥ 2025 +* Compliance Data Quality DCS (OVDQ DCS): Year ≥ 2025 +* Compliance Data Quality FuelEU (OVDQ FEUM): Year ≥ 2025 +* Emissions Connect Data Quality (OVDQ VLV): Year ≥ 2023 + +* Data before these cutoff years will be returned as empty periods. + +## Expected Impact +* Reduced volume of unnecessary historic data. +* Improved system response times and performance. +* More focused views for end users. diff --git a/sections/dataworkbench/toc.json b/sections/dataworkbench/toc.json index dfe8cff6..c8c6bef0 100644 --- a/sections/dataworkbench/toc.json +++ b/sections/dataworkbench/toc.json @@ -12,6 +12,10 @@ "text": "Latest releases", "href": "news/recent-releases.md" }, + { + "text": "February 2026 third release", + "href": "news/releasefeb26trd.md" + }, { "text": "February 2026 second release", "href": "news/releasefeb26sec.md" From f04d1b084439ca1bcb7deee4472b57e246d19818 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Tue, 17 Feb 2026 09:29:18 +0100 Subject: [PATCH 02/13] fixing metadata --- sections/dataworkbench/news/releasefeb26trd.md | 1 - 1 file changed, 1 deletion(-) diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md index e4d1910f..57a427af 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -2,7 +2,6 @@ author: Veracity description: This is the changelog for the February 2026 third release of Data Workbench. --- - # February 2026 third release: Egest API To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. From ab1f5cd5ae45411cf9d8933c43516b2c15f73ccc Mon Sep 17 00:00:00 2001 From: Docs <107537882+mkzieb@users.noreply.github.com> Date: Tue, 17 Feb 2026 09:30:34 +0100 Subject: [PATCH 03/13] Update releasefeb26trd.md fixing meta data display --- sections/dataworkbench/news/releasefeb26trd.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md index 57a427af..5deb48a7 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -1,7 +1,8 @@ ---- +--- author: Veracity description: This is the changelog for the February 2026 third release of Data Workbench. --- + # February 2026 third release: Egest API To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. From ebb6740c00be456ee24b262706b49167714f6db6 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Mon, 2 Mar 2026 10:17:01 +0100 Subject: [PATCH 04/13] changed file for operationalvesseldata --- sections/datastandards/operationalvesseldata.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sections/datastandards/operationalvesseldata.md b/sections/datastandards/operationalvesseldata.md index b8653f71..7055b04e 100644 --- a/sections/datastandards/operationalvesseldata.md +++ b/sections/datastandards/operationalvesseldata.md @@ -5,7 +5,7 @@ description: Description of Operational Vessel Data Standards in Veracity # Operational Vessel Data (OVD) - + Interface Description @@ -29,7 +29,7 @@ Operational Vessel Data (OVD) is a standard for log abstracts and other operatio The OVD data service on Veracity is continuously assuring data from thousands of vessels. By submitting data to Veracity OVD, your data is structured, analyzed, enriched and quality assured before you have the option to use it in one of the many services running on Veracity, like MRV and DCS/CII verification, Emissions Connect, or to share quality assured data via the Veracity Data Workbench with stakeholders or other parties or solutions that will utilize your data, like Poseidon Principles or Sea Cargo Charter. -A full and comprehensive description of the OVD standard can be found in the [OVD Interface Description](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVD%203.11.1%20interface%20description.xlsx). To further learn, play with and test your OVD data, the [OVD Guide](https://ovdguide.veracityapp.com) has interactive guidance to the most important elements of OVD and allow you to test upload files. +A full and comprehensive description of the OVD standard can be found in the [OVD Interface Description](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVD%203.12%20interface%20description.xlsx). To further learn, play with and test your OVD data, the [OVD Guide](https://ovdguide.veracityapp.com) has interactive guidance to the most important elements of OVD and allow you to test upload files. OVD consists of several schemas. A schema is a definition of how to fill in the operational vessel data, with defined columns and clear rules for what to put into each of the columns/rows. The two most used schemas in OVD are Log Abstract (LA), listing all key events from the vessels’ operations, and the Bunker Reports (BR), listing all bunkers in the relevant period. Both the Log Abstract and the Bunker Reports are required for DNV’s verification services, like MRV and DCS/CII verification. @@ -41,4 +41,4 @@ Below is an example of how the OVD Log Abstract would look for a vessel sailing Have a look at the [Sample Files](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVDsamplefiles.zip) to find more examples. -Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file +Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file From ad410069c5a3b2e16da6dedc7ca77f62c116c551 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Mon, 2 Mar 2026 10:35:12 +0100 Subject: [PATCH 05/13] Updated operationalvesseldata --- sections/datastandards/operationalvesseldata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sections/datastandards/operationalvesseldata.md b/sections/datastandards/operationalvesseldata.md index 7055b04e..113404c4 100644 --- a/sections/datastandards/operationalvesseldata.md +++ b/sections/datastandards/operationalvesseldata.md @@ -41,4 +41,4 @@ Below is an example of how the OVD Log Abstract would look for a vessel sailing Have a look at the [Sample Files](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVDsamplefiles.zip) to find more examples. -Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file +Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file From 2c2f2d47192a39e52f5366da27df1cbbc1fc2c75 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Mon, 2 Mar 2026 11:01:45 +0100 Subject: [PATCH 06/13] Revert "Updated operationalvesseldata" This reverts commit ad410069c5a3b2e16da6dedc7ca77f62c116c551. --- sections/datastandards/operationalvesseldata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sections/datastandards/operationalvesseldata.md b/sections/datastandards/operationalvesseldata.md index 113404c4..7055b04e 100644 --- a/sections/datastandards/operationalvesseldata.md +++ b/sections/datastandards/operationalvesseldata.md @@ -41,4 +41,4 @@ Below is an example of how the OVD Log Abstract would look for a vessel sailing Have a look at the [Sample Files](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVDsamplefiles.zip) to find more examples. -Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file +Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file From e8bd7df7601895b3ca8a1caa60f53901ee713960 Mon Sep 17 00:00:00 2001 From: MICZIE Date: Fri, 6 Mar 2026 09:08:17 +0100 Subject: [PATCH 07/13] OVD Egest release notes: updated with new info --- sections/dataworkbench/news/releasefeb26trd.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md index 5deb48a7..50fde1a9 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -8,6 +8,9 @@ description: This is the changelog for the February 2026 third release of Data W To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. An additional filter is now applied to the Year column, ensuring data before the defined cutoff years is no longer returned. +To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. +Data before the defined cutoff years is no longer returned. + ## Cutoff Rules Applied * Compliance Data Quality MRV EU (OVDQ MEU): Year ≥ 2025 * Compliance Data Quality MRV UK (OVDQ MUK): Year ≥ 2025 @@ -16,8 +19,10 @@ An additional filter is now applied to the Year column, ensuring data before the * Emissions Connect Data Quality (OVDQ VLV): Year ≥ 2023 * Data before these cutoff years will be returned as empty periods. +* **If you want to keep those data, please download it before 2026-03-11.** ## Expected Impact * Reduced volume of unnecessary historic data. * Improved system response times and performance. * More focused views for end users. + From c52025954879f4379f7571eb5c954710afcdb36d Mon Sep 17 00:00:00 2001 From: MICZIE Date: Fri, 6 Mar 2026 09:11:14 +0100 Subject: [PATCH 08/13] changed date format --- sections/dataworkbench/news/releasefeb26trd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md index 50fde1a9..6cebaf8c 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -19,7 +19,7 @@ Data before the defined cutoff years is no longer returned. * Emissions Connect Data Quality (OVDQ VLV): Year ≥ 2023 * Data before these cutoff years will be returned as empty periods. -* **If you want to keep those data, please download it before 2026-03-11.** +* **If you want to keep those data, please download it before 11 March 2026.** ## Expected Impact * Reduced volume of unnecessary historic data. From b9b089855c7469b38af763356df4fd81c0dda935 Mon Sep 17 00:00:00 2001 From: Docs <107537882+mkzieb@users.noreply.github.com> Date: Fri, 6 Mar 2026 09:16:11 +0100 Subject: [PATCH 09/13] Update releasefeb26trd.md --- sections/dataworkbench/news/releasefeb26trd.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasefeb26trd.md index 6cebaf8c..78512892 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasefeb26trd.md @@ -4,10 +4,6 @@ description: This is the changelog for the February 2026 third release of Data W --- # February 2026 third release: Egest API - -To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. -An additional filter is now applied to the Year column, ensuring data before the defined cutoff years is no longer returned. - To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. Data before the defined cutoff years is no longer returned. From f35ddcbf24ce15162da88224c3cc768af2472d7e Mon Sep 17 00:00:00 2001 From: MICZIE Date: Fri, 6 Mar 2026 09:59:08 +0100 Subject: [PATCH 10/13] DWB/OVD release egest API --- sections/dataworkbench/news/recent-releases.md | 2 +- .../news/{releasefeb26trd.md => releasemar26.md} | 7 +------ sections/dataworkbench/toc.json | 4 ++-- 3 files changed, 4 insertions(+), 9 deletions(-) rename sections/dataworkbench/news/{releasefeb26trd.md => releasemar26.md} (78%) diff --git a/sections/dataworkbench/news/recent-releases.md b/sections/dataworkbench/news/recent-releases.md index 400887d7..65cb7a3e 100644 --- a/sections/dataworkbench/news/recent-releases.md +++ b/sections/dataworkbench/news/recent-releases.md @@ -7,11 +7,11 @@ description: This is an overview of recent releases of Data Workbench and Data P ## Recent Data Workbench changes +1. [March 2026 release](releasemar26.md) 1. [February 2026 third release](releasefeb26trd.md) 1. [February 2026 second release](releasefeb26sec.md) 1. [February 2026 release](releasefeb26.md) 1. [January 2026 second release](releasejan26sec.md) -1. [January 2026 release](releasejan26.md) ## Recent Data Platform changes diff --git a/sections/dataworkbench/news/releasefeb26trd.md b/sections/dataworkbench/news/releasemar26.md similarity index 78% rename from sections/dataworkbench/news/releasefeb26trd.md rename to sections/dataworkbench/news/releasemar26.md index 6cebaf8c..110bb915 100644 --- a/sections/dataworkbench/news/releasefeb26trd.md +++ b/sections/dataworkbench/news/releasemar26.md @@ -1,13 +1,9 @@ ---- +--- author: Veracity description: This is the changelog for the February 2026 third release of Data Workbench. --- # February 2026 third release: Egest API - -To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. -An additional filter is now applied to the Year column, ensuring data before the defined cutoff years is no longer returned. - To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. Data before the defined cutoff years is no longer returned. @@ -25,4 +21,3 @@ Data before the defined cutoff years is no longer returned. * Reduced volume of unnecessary historic data. * Improved system response times and performance. * More focused views for end users. - diff --git a/sections/dataworkbench/toc.json b/sections/dataworkbench/toc.json index c8c6bef0..4c55226a 100644 --- a/sections/dataworkbench/toc.json +++ b/sections/dataworkbench/toc.json @@ -13,8 +13,8 @@ "href": "news/recent-releases.md" }, { - "text": "February 2026 third release", - "href": "news/releasefeb26trd.md" + "text": "March 2026 release", + "href": "news/releasemar26.md" }, { "text": "February 2026 second release", From dfc23728fa2b03f1736ae7786f8d242212267a8a Mon Sep 17 00:00:00 2001 From: Docs <107537882+mkzieb@users.noreply.github.com> Date: Fri, 6 Mar 2026 10:04:21 +0100 Subject: [PATCH 11/13] Update operationalvesseldata.md --- sections/datastandards/operationalvesseldata.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sections/datastandards/operationalvesseldata.md b/sections/datastandards/operationalvesseldata.md index 7055b04e..651baefe 100644 --- a/sections/datastandards/operationalvesseldata.md +++ b/sections/datastandards/operationalvesseldata.md @@ -5,7 +5,7 @@ description: Description of Operational Vessel Data Standards in Veracity # Operational Vessel Data (OVD) - + Interface Description @@ -29,7 +29,7 @@ Operational Vessel Data (OVD) is a standard for log abstracts and other operatio The OVD data service on Veracity is continuously assuring data from thousands of vessels. By submitting data to Veracity OVD, your data is structured, analyzed, enriched and quality assured before you have the option to use it in one of the many services running on Veracity, like MRV and DCS/CII verification, Emissions Connect, or to share quality assured data via the Veracity Data Workbench with stakeholders or other parties or solutions that will utilize your data, like Poseidon Principles or Sea Cargo Charter. -A full and comprehensive description of the OVD standard can be found in the [OVD Interface Description](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVD%203.12%20interface%20description.xlsx). To further learn, play with and test your OVD data, the [OVD Guide](https://ovdguide.veracityapp.com) has interactive guidance to the most important elements of OVD and allow you to test upload files. +A full and comprehensive description of the OVD standard can be found in the [OVD Interface Description](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVD%203.12.1%20interface%20description.xlsx). To further learn, play with and test your OVD data, the [OVD Guide](https://ovdguide.veracityapp.com) has interactive guidance to the most important elements of OVD and allow you to test upload files. OVD consists of several schemas. A schema is a definition of how to fill in the operational vessel data, with defined columns and clear rules for what to put into each of the columns/rows. The two most used schemas in OVD are Log Abstract (LA), listing all key events from the vessels’ operations, and the Bunker Reports (BR), listing all bunkers in the relevant period. Both the Log Abstract and the Bunker Reports are required for DNV’s verification services, like MRV and DCS/CII verification. @@ -41,4 +41,4 @@ Below is an example of how the OVD Log Abstract would look for a vessel sailing Have a look at the [Sample Files](https://veracitycdnprod.blob.core.windows.net/developer/veracitystatic/ovd/OVDsamplefiles.zip) to find more examples. -Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. \ No newline at end of file +Data can be submitted to DNV’s Veracity OVD via continuous and automated transfer using modern REST API interfaces, or via manual upload of CSV files. Please contact [Veracity Support](mailto:support@veracity.com) if you want to know more about how to establish automated transfer of OVD data. From e21e647fb0b6d4725eb016850da894588d179bc8 Mon Sep 17 00:00:00 2001 From: Docs <107537882+mkzieb@users.noreply.github.com> Date: Fri, 6 Mar 2026 10:04:43 +0100 Subject: [PATCH 12/13] Update releasemar26.md --- sections/dataworkbench/news/releasemar26.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sections/dataworkbench/news/releasemar26.md b/sections/dataworkbench/news/releasemar26.md index 110bb915..65dee847 100644 --- a/sections/dataworkbench/news/releasemar26.md +++ b/sections/dataworkbench/news/releasemar26.md @@ -1,4 +1,4 @@ ---- +--- author: Veracity description: This is the changelog for the February 2026 third release of Data Workbench. --- From 1ceabce4e4a3f75be901464226872215a0587230 Mon Sep 17 00:00:00 2001 From: Docs <107537882+mkzieb@users.noreply.github.com> Date: Fri, 6 Mar 2026 10:06:01 +0100 Subject: [PATCH 13/13] Update releasemar26.md --- sections/dataworkbench/news/releasemar26.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sections/dataworkbench/news/releasemar26.md b/sections/dataworkbench/news/releasemar26.md index 65dee847..4988963e 100644 --- a/sections/dataworkbench/news/releasemar26.md +++ b/sections/dataworkbench/news/releasemar26.md @@ -1,9 +1,9 @@ --- author: Veracity -description: This is the changelog for the February 2026 third release of Data Workbench. +description: This is the changelog for the March 2026 release of Data Workbench. --- -# February 2026 third release: Egest API +# March 2026 release: Egest API To improve system performance and reduce unnecessary data processing, access to historical data within the Egest API has been restricted. Data before the defined cutoff years is no longer returned.