Project

General

Profile

Actions

feature request #9197

open

Handle caucasus conspectus data in E+M and caucasus portal

Added by Andreas Müller over 2 years ago. Updated 2 months ago.

Status:
Discussed
Priority:
Highest
Category:
cdmlib
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal

Description

Distribution data for caucasus taxa from "Konspekt flory Kavkaza" has been entered into a seperate database (euromed-caucasus) some time ago (#7921).

On 2020-08-18 we (ERS, NK, AK, AM) had a meeting to discuss how to handle these data which are using areas which differ from the typical E+M caucasus areas. The following is the outcome of this meeting:

  1. for the E+M dataportal only the existing E+M areas should be shown, data needs to be aggregated to these areas
  2. where data is ambigous as the E+M area hierarchie and the conspectus areas are ambigous sometimes (conspectus areas may have 2 parent areas in the E+M hierarchy) aggregated data need to be flaged doubtful if no other data exists which is not doubtful. Question: what if the distribution status differs in the later case.
  3. there are 5 conspectus areas which are ambigous when mapped to E+M areas:

    a. VK which belongs mostly to Nothern Caucasus but the subarea Kubinsky belongs belongs to Azerbaidjan
    b. The Eastern Transcaucasus areas Alazan-Agrichay, Iori-Sheki, Murghuz-Murovdagh: they belong partly to Georgia and partly to Azerbaidjan
    c. The nothern border of Central and parts of Eastern Transcaucasia seems to be a bit more south then the country borders between Georgia and Russia

  4. issue 3c will be checked by NK if the border really differs from the country border or if the map is inaccurate at this point

  5. data in 3b needs to be aggregated in the way that doubtful distribution data will be created for Geogia and Azerbaidjan

  6. data in 3a needs to be doubfully aggregated to Northern Caucasus and Azerbaijan

  7. generally data was entered on sub-area level, however it looks like main-areas were used if data existed for ALL subareas (we tested this for Dianthus barbatus which has data "Eastern Caucasus" and in the book it has data for all 4 sub-areas, while Atriplex fominii has data only for the Eastern Caucasus sub-areas Kubinsky and Manas-Samur but no data for the main area itself. This rule still needs to be further validated. Also it needs to be checked what has been edited if all sub-areas existed but with different status.

  8. as the handling described in 7. differs from the typical handling in E+M (and from best practice) where data for all sub-areas is entered if it exists in all sub-areas we may need a script that creates the sub-area data for these cases (and deletes the main area data)
    ).

  9. for the caucasus dataportal the sub-area data should be shown if it exists, in some cases this may lead to overlapping area information as data may come from different sources (conspectus and other sources, using the E+M areas), generally this is not a problem for the maps (but maybe for the textual representation which requires hierarchical areas), problems here will be discussed later

  10. the shapefile does not need hierarchical information and therefore can be created straight forward (#9161)

The map:

and https://www.binran.ru/upload/caucasian/images/%D0%A0%D0%B0%D0%B9%D0%BE%D0%BD%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5_html_181329b1.jpg

Tervuren geoserver: http://edit.africamuseum.be/geoserver/topp/wms?service=WMS&version=1.1.0&request=GetMap&layers=topp:euromed_2013&styles=&bbox=-1600072.75,-1800000.0,5600000.0,5850093.0&width=481&height=512&srs=EPSG:7777777&format=application/openlayers


Files

picture541-1.png (538 KB) picture541-1.png Andreas Müller, 08/18/2020 01:14 PM

Related issues

Related to EDIT - task #9161: E+M shapefile with Kaukasus regionsNewAndreas Müller

Actions
Related to EDIT - task #7921: Create database for Caucasus distribution editingClosedAndreas Müller

Actions
Related to EDIT - task #10236: Import data from caucasus DB to E+MDiscussedAndreas Müller

Actions
Actions #1

Updated by Andreas Müller over 2 years ago

  • Tags set to euro+med, caucasus, map
Actions #2

Updated by Andreas Müller over 2 years ago

Actions #3

Updated by Andreas Müller over 2 years ago

  • Description updated (diff)
Actions #4

Updated by Andreas Müller over 2 years ago

  • Related to task #9161: E+M shapefile with Kaukasus regions added
Actions #5

Updated by Andreas Müller over 2 years ago

  • Related to task #7921: Create database for Caucasus distribution editing added
Actions #7

Updated by Andreas Müller over 2 years ago

  • Description updated (diff)
Actions #8

Updated by Andreas Müller over 2 years ago

An issue that we have not discussed is the border between Geogia and Armenia which does not show up in the above map. Can somebody say which conspectus areas belong to Armenia and which belong to Georgia and which belong to both (only for the areas close to the border)?

Actions #9

Updated by Andreas Müller over 2 years ago

  • Description updated (diff)
Actions #10

Updated by Andreas Müller over 2 years ago

NK:

das sind die jeweils zu Georgien und Armenien gehörenden Areales

Armenien
ЮЗЗ = SWTC
ЦЗ = CTC
ВЗ = ETC
ЮЗ = STC

Georgien
ЗЗ = WTC
ЦЗ = CTC
ЦК = CC
ВК = EC
ВЗ = ETC
ЮЗЗ = SWTC

Auf der Seite des Conspectus, wo auch die Karte zu finden ist, ist weiter unten eine Gegenüberstellung der Conspectus-Areale und der Areale aus älteren Floren und den Länder-Floren.

Actions #11

Updated by Eckhard von Raab-Straube over 1 year ago

1.) Priority: show the areas in detailed map in the Caucasus Portal. The aggregation to Euro+Med is second priority, might be postponed?

2.) to answer the question: check in the database if such cases really exist. I guess they might be extremely rare and can be handled manually.

3a)Subarea 5d)Kubinsky: map to Azerbaijan Ab(A). In this case, no doubtful indication is needed, this is not part of Rf(CS), not a part of Russia.
If distribution is BK (VK) or 5 (EC=Eastern Caucasus) as a whole, without any subdivisions, map to both Rf(CS) and to Ab(A).

3b) as already stated above, map those three areas to ?Gg(G) and ?Ab(A), make a critical note in explanations of the Caucasus portal

3c) ignore. Map those three areas (4c, 5a, 5b) entirely to Rf(CS), make a critical note in explanations of the Caucasus portal

4,5,6) see above

NEW: Subarea 10b) Dzhavachetia-Upper Akhurjan belongs to both Georgia and Armenia, map this area to ?Gg(G) and to ?Ar, make a critical note in explanations of the Caucasus portal

7) this rule seems to have been applied consistently, if not, data entry must be repeated and complemented. Different status is theoretically possible but extremely rare.

8) Check if such a script is really needed

9) needs discussion

10)can this be done or has it been done already? Straightforward sounds good. Currently at release 5.28, can it be done earlier?

NEW: Enable editing of Caucasus subareas in the Euro+Med Plantbase main editor (I tried but it seems that those areas are not available via the Editor there)

Actions #13

Updated by Andreas Müller 2 months ago

  • Status changed from New to In Progress
  • Priority changed from New to Highest
  • Target version changed from Unassigned CDM tickets to Release 5.37
Actions #14

Updated by Andreas Müller 2 months ago

  • Related to task #10236: Import data from caucasus DB to E+M added
Actions #15

Updated by Andreas Müller 2 months ago

  • Status changed from In Progress to Discussed
Actions

Also available in: Atom PDF