Please note that this forum is no longer in use and has been replaced by an online contact us form.

Be assured that the information service rendered by the EEA remains similar. Note that the content of this forum will remain publicly available until the end of 2020. After that we will archive it for internal use for a max retention period of 3 years. Any personal data will be deleted after this retention period.

With kind regards,
EEA Enquiry Service

Please login to participate.
Discussion
.
pedromonteiro Aug 08, 2012 10:21 AM
Different codes for Vipera latastei.
Vipera latastei is coded with number 2009 in <http://eunis.eea.europa.eu/species/8807/general> , but is coded with numbers 5904 (new entry) and 6027 (old entry) by the Codelist for species in <http://bd.eionet.europa.eu/[…]/reference_portal>.
Why, and what is the right code?
Thank you very much
Replies (3)
EEA Aug 08, 2012 02:33 PM
We will get back with the answer to you, as soon as our experts will be back from summer vacation,
Kind thanks for your understanding,
EEA Com
EEA Aug 09, 2012 10:54 AM
Dear Pedromonteiro,

In the Natura2000 reference portal:
Vipera latastei is a valid name and has code 5904
Vipera latasti is a synonym and has code 6027

The code 2009 is from the original import of N2000 codes that was done several years ago. We will update it in EUNIS as soon as possible and wish to thank you for pointing this inconsistency out.

If you want to use the code for Vipera latastei in the context of Natura 2000, then you should use 5904.

We hope this information will help.

Best Regards.
EEA Com
pedromonteiro Aug 10, 2012 01:09 PM
Thanks for your reply and attention. As far as I understand, N2000 codes primarily address names (not taxa), so they may be different, and/or change over time, even when the taxon is the same: in this case, the Vipera latastei species has(d) 3 different codes (new, old and oldest) . Those differences and changes may sometimes cause trouble in linking species databases. So, in a previous thread, I suggested an unique and uniform base reference that could fix one stable code for one taxon (different names / code names for the same taxon could be linked to the same taxon code). Anyway, for now and for this purpose, I will also try to relate to EOL codes. Best regards, and thank you again. Pedro Monteiro.
 
Loading