[Im4ca-wp1.beta] IM4CA Romania Campaing 2026 Finalsied metadata and dataformat for in-situ measurements

Wed Jul 22 17:09:29 CEST 2026

Provided there is a unique mapping of IDs used here to the IDs (and coordinates) of OMV, this sounds like a good solution.

Dominik

Von: Im4ca-wp1.beta <im4ca-wp1.beta-bounces at listserver.vu.nl> Im Auftrag von Röckmann, T. (Thomas)
Gesendet: Mittwoch, 22. Juli 2026 14:43
An: Mathis.Lozano <mathis.lozano at lsce.ipsl.fr>
Cc: im4ca-wp1 beta <im4ca-wp1.beta at listserver.vu.nl>
Betreff: Re: [Im4ca-wp1.beta] IM4CA Romania Campaing 2026 Finalsied metadata and dataformat for in-situ measurements

Dear Mathis, Sara and others,  

Thanks a lot for providing the template, very useful!

We want to flag an important concern: In this template we would give away information from the OMV database, namely the three items

# site ID including coordinate

# site type 

# site details

 And maybe also part of the information in "#distance source-measurement” uses the OMV database. 

We are not allowed to publish the precise coordinates. If we did this for all sites, then the entire OMV database would become available publicly. 

I suggest to modify as follows: 

We cannot use the ID provided by OMV, and need to come up with another ID system. 

For the coordinates we can use the location of the maximum of our plume, or the average coordinates of the track, or imagery from Google Maps, but not the coordinates from the OMV file. 

Site type: as assessed by our own observations, but NOT use the OMV nomenclature unless obvious (e.g. oil well)

Site details: again, as assessed by our own observations, NOT from the OMV database, in several cases it will be “unknown". 

Regarding the distance, we can possibly calculate it from Google Maps imagery but not from the OMV database. 

TO ALL, PLEASE MAKE SURE THAT WE DO NOT MAKE OMV INFORMATION PUBLIC!

Best regards

Thomas and Foteini

On 22 Jul 2026, at 10:09, Mathis.Lozano <mathis.lozano at lsce.ipsl.fr <mailto:mathis.lozano at lsce.ipsl.fr> > wrote:

You don't often get email from mathis.lozano at lsce.ipsl.fr <mailto:mathis.lozano at lsce.ipsl.fr> . Learn why this is important <https://aka.ms/LearnAboutSenderIdentification>  

Hello everyone, 

If the link I sent yesterday does not work, or if you are prompted to enter a password, you can access the template folder containing the data files through the following path in the ShareBox. 

WP1- Anthropogenic emissions Thomas Röckmann and Jean-Daniel Paris / Data / Romania campaign / RAW DATA vehicles / LSCE data / Aeris / 20260602_Template 

Have a nice day. 

Mathis Lozano 

  _____  

De: "Mathis.Lozano" <mathis.lozano at lsce.ipsl.fr <mailto:mathis.lozano at lsce.ipsl.fr> >
À: "im4ca-wp1 beta" <im4ca-wp1.beta at listserver.vu.nl <mailto:im4ca-wp1.beta at listserver.vu.nl> >
Envoyé: Mardi 21 Juillet 2026 18:43:25
Objet: Fwd: [Im4ca-wp1.beta] IM4CA Romania Campaing 2026 Finalsied metadata and dataformat for in-situ measurements

Hello everyone,

In this folder, 

20260602_Template <https://vu.data.surf.nl/s/2tDZeQLmniYAqCo?dir=/WP1-%20Anthropogenic%20emissions%20Thomas%20R%C3%B6ckmann%20and%20Jean-Daniel%20Paris/Data/Romania%20campaign/RAW%20DATA%20vehicles/LSCE%20data/Aeris/20260602_Template> 

You will find typical post-processed data for a full day of measurements. Please use these files as examples, as this will make it easier for us to process the data and perform the quantification afterward.

The folder contains several files corresponding to individual measurement sequences from the day. You will find Gaussian Plume Measurements (GPM), Other Test Method measurements (OTM), and Sniffing measurements (SNIF). Each file first contains metadata as commented lines (starting with #), followed by the measurement data.

I have also added screenshots associated with each sequences. The screenshot files have exactly the same names as their corresponding data files.

Please note that these files templates were developed for car-based measurements, as we are not experts in drone measurements. 

Here are some clarifications and requested modifications regarding the metadata files:

*	Site ID: ROxxxxxx → ATTR_6
*	Add the distance from the source (in meters) to the measurement location (middle and/or maximum plume distance).
*	Add the source information → the source name and coordinates can be found in the file provided by Petrom (Old_romeo_sites_01062026.xlsx attached to this mail).
*	Add an additional step to the data processing workflow → Step 6: Calibration and corrections (temperature and water vapor) applied to CH₄ values.
*	Change the time format to → YYYY-MM-DD HH:MM:SS
This format is more convenient for our data processing and quantification procedures.
*	incorrect values → -999

For OTM measurements, please keep one minute of data before and after each OTM sequence. This will make it easier for us to determine a suitable local background and subsequently subtract it for enhancement calculations. The background data are also valuable for heading calculations.

Best 

Mathis Lozano. 

  _____  

De: "Sara.Defratyka" <sara.defratyka at lsce.ipsl.fr <mailto:sara.defratyka at lsce.ipsl.fr> >
À: "im4ca-wp1 beta" <im4ca-wp1.beta at listserver.vu.nl <mailto:im4ca-wp1.beta at listserver.vu.nl> >
Envoyé: Jeudi 16 Juillet 2026 12:27:49
Objet: Re: [Im4ca-wp1.beta] IM4CA Romania Campaing 2026 Finalsied metadata and dataformat for in-situ measurements

Hello everyone,

as mentioned, here is a powerpoint with some example of sites names and photos. I'll update it regulary and I will send a message around as I go through all sites vistied by LSCE. I took the names from file with sites visited during ROMEO. For most cases, I used a name from the name column: Facility_type_details. I replaced it if we got more information about the visited oil well (e.g., adding if it's active or inactive, clearly abandoned; if it's pumpjack or oil pump). You can find it here:

https://vu.data.surf.nl/f/264442335 (it's in the same location as spreadsheets with list of visited sites). For our LSCEspreadsheet, I also added a column with a time when a note was made. 

If visited site is not at ROMEO site liste, but it is in the recent files shared by PETROM, please use ATTR_5 name as a site name. ATTR_5 is also used as ID (ROxxx) in ROMEO file.

Also, as Dominik spotted, adding coordiantes of visited sources in the datafile is needed. Later this week we will send LSCE example data with this information added. I will highlited in the email this change.

Finally, please double check if each team provided spreadsheet with visited sites. As mentioned on the meeting we need coordinates, information if site was sniffed, quantified and if emission was observed, for quick visualisation and statistics for this reporting report.

Best,

Sara

  _____  

From: "Sara.Defratyka" <sara.defratyka at lsce.ipsl.fr <mailto:sara.defratyka at lsce.ipsl.fr> >
To: "im4ca-wp1 beta" <im4ca-wp1.beta at listserver.vu.nl <mailto:im4ca-wp1.beta at listserver.vu.nl> >, "margareta hellstrom" <margareta.hellstrom at mgeo.lu.se <mailto:margareta.hellstrom at mgeo.lu.se> >, "ute karstens" <ute.karstens at mgeo.lu.se <mailto:ute.karstens at mgeo.lu.se> >
Sent: Thursday, 9 July, 2026 17:53:30
Subject: IM4CA Romania Campaing 2026 Finalsied metadata and dataformat for in-situ measurements

Hello everyone,

finally I managed to finalise the template of metadata and dataformat. Following it by everyone will facilitate submitting IM4CA data to ICOS Carbon Portal, but also calculating emissions rates and final upscaling. On the previous, post-campaing meeting for ground teams, we came to the conclusion that ideal, one team is responsible for the quanitifcation, using well-prepared data from the ground teams. 

Some clarifications:

You can find the template in the attachment, as a txt file: "IM4CA_Romania_Campaing_in_situ_metadata_data_format".

The file name convention is: yyyy-mm-dd-ROMxxxx-seq-team.csv (details in .txt file)

Overall, it should be 1 csv file per site and sequence, merged in a zip file. Separate zip files should be made for car, drone and tall tower measurements. This csv file should include all mentioned metadata in the template plus a dataframe. Note # is used as a comment, ; as a column separation and . for decimal places.

Note also, that based on ICOS CP suggestion, dataformat is YYYY-MM-DDTHH:MM:SSZ and the data should be in UTC time.

We need to decide the common nomenclature for site type details (e.g., pumpjack, gas well, water tank).

System diagnostic are omitted to facilate following the data. It's also up to invidiual teams to use their instrument system dignostic to flag data. The method of flagging and correcting/calibrating data should be also desribed in the metadata.

Please, especially from the drone mass balance perspective, let me know if some crucial variables are missing (maybe some more information about the highet above the ground)?

We should be able to send around an examples datafile from LSCE next week, so it should help to follow the template. 

Deadline

First datafiles should be created until end of this month, for the ICOS CP submission. Then, ideally each team prepars the set of their .csv until September, for further quantifications and upscaling.

Submission to ICOS CP

We will ask ICOS CP for the data embargo, potentially until end of the project. In this case, we will have enough time to work on our data before they come publicly available. However, we still need to submit data to ICOS CP relatively quickly, to prove to EU that data publication chain is established.

For the submission to the ICOS CP, data should go through at list first quality control. Then, later in the project, new data versions can be added as well. 

The first submission, of some example data should be done until end of this month. It should be separate submissions of all csv files merged into indvidual zip folders for drone, cars and tall tower measurements (eg., one zip folder per measurement platform), with added a spreadsheet "spatiotemp_uploadmeta_im4ca-wp1_DRAFT". Also, some metadata report should be included there. Hopefully, this report can be made by extracting information from Deliverable 1.1.

Additionla needed actions 

1) Please also fill the spreadsheet of visited sites. It is crucial we have the informations about: site name, type, details, lat, long, sniffing, done quantification and if CH4 emissions was observed. Having this data, we are able to make a quick statistic now and how may sites were visited. It will also allow to estiamte how long it will take to calcualte emission rate from all visited sites. You can find the individual spreadsheets for each team here:

https://vu.data.surf.nl/s/emwBToabB7H94n7?dir=/Data/Romania%20campaign/OVERVIEW%20Field_collected_data

2) For now, I have details of the main data provider per team. Could I also ask you to send a details of each person involved in data colelction and processing? In this case they can be listed as contirbutors during ICOS CP submission. Please send to me: name, e-mail and ORCID ID of all contributors.

Remote data:

This template is only for in-situ measurements. As discussed, we will work on template of netcdf file for remote data separately. In the meantime, you can test those two tool to check the compatibility of your already existing files:

 <https://mcc.podaac.earthdatacloud.nasa.gov/> https://mcc.podaac.earthdatacloud.nasa.gov/ 

 <https://compliance.ioos.us/index.html> https://compliance.ioos.us/index.html

I hope you survived until end of this enormous email!

Take care duirng heatwaves!

Best,

-- 

Dr Sara Defratyka
orcid.org/0000-0002-9488-4518
LSCE - UVSQ
Bât 714 P1115
Orme des Merisiers
91191 Gif-sur-Yvette

[Fichier texte:ATT00001]

_______________________________________________
Im4ca-wp1.beta mailing list
Im4ca-wp1.beta at listserver.vu.nl <mailto:Im4ca-wp1.beta at listserver.vu.nl> 
https://listserver.vu.nl/mailman/listinfo/im4ca-wp1.beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listserver.vu.nl/pipermail/im4ca-wp1.beta/attachments/20260722/65444dce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7504 bytes
Desc: not available
URL: <https://listserver.vu.nl/pipermail/im4ca-wp1.beta/attachments/20260722/65444dce/smime-0001.p7s>