Menu
Phenology Weekly
Living Almanac: Phenology Weekly - a US based phenology newspaper! You can access it on paper.li or linked within PEP725Living Almanac: Phenology Weekly
Remark: We think it's worth reading but PEP725 does not have any influence to the content of this newspaper!
Submitting datasets to the PEP725 project
1. General remarks
Dear PEP725 partners!
Thanks for submitting your actual/ historical phenological observations to our Pan European Phenology Database. We really appreciate your efforts for providing this information in the desired and in the following - in detail- described file format.
In 2017, we completely renewed our database structure, so the explanations below refer to the modified modalities.
But until further notice, we will accept also data in the previous format.
We ask for your understanding that new plants or phases that have not yet been implemented can only be accepted in the new data format!
If you have any questions please feel free to contact us (pep725@zamg.ac.at)
2. METADATA
- station information:
Additional stations (the actual station list is given in pep_stations) or changes in metadata should be well documented and - if possible - reported in following format:
| header | description |
|---|---|
| s_id | PEP725 station id, will be assigned at the first submission |
| nat_id | national station number |
| lon | longitude in decimal degrees [WGS84] |
| lat | latitude in decimal degrees [WGS84] |
| alt | altitude in [m] asl |
| name | name of station |
- contact information:
Required for new partners and should be updated / checked on new subissions! Detailed information of the institution/member/organization that submits the data could be send in following format:
| header | description |
|---|---|
| provider_org | provider organization, for example ZAMG |
| provider_name | provider- contact person name |
| provider_email | actual contact address (e-mail) of provider |
| provider_web | link to the national phenological web site [if existing] |
3. DATA
The main data set of phenological observation should be submitted in following file structure:
| header | description | more information |
|---|---|---|
| s_id | PEP725 station number | PEP725 station list (huge file, be patient) |
| gss_id | plant identifier | PEP725 plant list |
| phase_id | phenological phase id | PEP725 pheno - phase list |
| year | YYYY | |
| day | number of day in year [1-365/366] | |
| cult_season | season of cultivation | 0..not applicable,1..summer cereals - sowing in spring, 2..winter cereals - sowing in autumn |
| affected_flag | planned for recurrence phases, affection due to pests, frost, ... | 0...observation not affected or impairment not known |
4. TRANSITION
If you have already sent observations and are struggling with the implementation of the new system, the following two tables will be certainly helpful.
| link | description |
|---|---|
| PEP725 plant conversion | On this table you can have a quick look on the former plant_id/cult_id codes and the corresponding new gss_id. In some cases (crops) you will need additionally the cult_season flag |
| PEP725 pheno-phase conversion | This table shows the translation between our former BBCH coding and the new phase_id. For all true BBCH phases the new phase_id will be the same, but as you know we need to define some new development stages to cover the observation reality. So please check this table if you need to do some adjustments as well the complete phase definition in the above section. We have now the complete BBCH scale and a couple of addional ones (e.g. autumnal colouration and leaf fall in 10% steps) something else might suit better to your national observation practice! Anyway, if you still can't find a suitable phase please let us know. |
EUMETNET