Project

General

Profile

Actions

feature request #4294

open

order of map legend entries conforms to term order

Added by Andreas Kohlbecker about 8 years ago. Updated 6 months ago.

Status:
In Progress
Priority:
Priority14
Category:
cdmlib
Start date:
Due date:
% Done:

0%

Estimated time:
0:30 h
Severity:
normal

Description

The order in distribution maps is defined by the order of the styles in the map service request parameter as= this order should be defined by the order of the terms (OrderedTermBase).

the order of the status is discussed in #3906 (EuroMed: preference of distribution status in case multiple distributions exist for the same area)

The expected order of the legend entries is like:

PresenceTerm.ENDEMIC_FOR_THE_RELEVANT_AREA
PresenceTerm.NATIVE
PresenceTerm.NATIVE_DOUBTFULLY_NATIVE
PresenceTerm.INTRODUCED_NATURALIZED
PresenceTerm.INTRODUCED_ADVENTITIOUS
PresenceTerm.INTRODUCED
PresenceTerm.INTRODUCED_DOUBTFULLY_INTRODUCED
PresenceTerm.NATIVE_PRESENCE_QUESTIONABLE
PresenceTerm.INTRODUCED_PRESENCE_QUESTIONABLE
PresenceTerm.CULTIVATED
AbsenceTerm.NATIVE_FORMERLY_NATIVE
AbsenceTerm.NATIVE_REPORTED_IN_ERROR
AbsenceTerm.INTRODUCED_REPORTED_IN_ERROR
AbsenceTerm.INTRODUCED_FORMERLY_INTRODUCED
PresenceTerm.INTRODUCED_UNCERTAIN_DEGREE_OF_NATURALISATION
AbsenceTerm.CULTIVATED_REPORTED_IN_ERROR
PresenceTerm.PRESENT
Actions #1

Updated by Andreas Kohlbecker almost 8 years ago

Hi Franck,

i am about to figure out how the order of the map legend entries are defined and how it can be influenced in a reliable way wich works for all versions of the map service.

My first experiments with an example from http://dev.e-taxonomy.eu/trac/wiki/MapRestServiceExamples revealed that the order seems to be defined by the order of the as parameter entries:

http://edit.africamuseum.be/edit_wp5/v1/areas.php?l=tdwg1&legend=1&mlp=3&title=a:foreign|b:native|c:rare|d:unknown&ad=tdwg4:c:MXEDU|b:MXETA|tdwg3:a:MXC,CUB|b:MXE,MXG|c:MXS,MXT&as=a:329d2a,483eef,2,2_2|b:ab8dc9F,da1029,2,5_7|c:d2e347|d:f7555d&ms=500&bbox=-115,6.78,-75.19,29.8&recalculate=false

http://edit.africamuseum.be/edit_wp5/v1/areas.php?l=tdwg1&legend=1&mlp=3&title=a:foreign|b:native|c:rare|d:unknown&ad=tdwg4:c:MXEDU|b:MXETA|tdwg3:a:MXC,CUB|b:MXE,MXG|c:MXS,MXT&as=b:ab8dc9F,da1029,2,5_7|c:d2e347|a:329d2a,483eef,2,2_2|d:f7555d&ms=500&bbox=-115,6.78,-75.19,29.8&recalculate=false

(BTW: the above is not working with v1.4_dev !)

Then I tried a more realistic test:

http://edit.africamuseum.be/edit_wp5/v1.4_dev/rest_gen.php?&image=true&recalculate=false&ms=512,512&bbox=-52.208579,12.692779,84.447524,66.352633&l=background_gis:Y,euromed_2013:Z&title=b:native%2C++doubtfully+native|h:native|c:introduced|d:native%2C++presence+questionable|f:introduced%2C+adventitious+%28casual%29|g:introduced%2C+naturalized|e:present&ad=euromed_2013%3Aparent:h:It,Gg|d:Ca|euromed_2013%3Aemarea:h:Ge,Cs,Hs%28A%29,Ga%28C%29,Tu%28A%29,Uk%28K%29,Sk,La,Uk%28U%29,Hu,Rf%28NW%29,Ar,Au%28L%29,Si%28S%29,Rf%28E%29,Rf%28K%29,Bu,Gr,Ga%28F%29,Da,Rf%28CS%29,Ct,Cg,Rf%28N%29,Tu%28E%29,Rf%28C%29,Lt,Ab%28A%29,Sr,Hs%28S%29,Su,Be%28L%29,Au%28A%29,Si%28M%29,By,Es,Lu,He,Ho,BH,Sl,Rf%28S%29,Rm,Ab%28N%29,Mo,Be%28B%29,Sy,Po,Al,Mk,Ga%28M%29|b:Br|c:Hb%28E%29|e:Sa,Le|f:Hb%28N%29|g:Co&as=Z:ffffff,c8c8c8~|Y:e0faff~|b:00ff00~0.1,|g:c86400~0.1,|h:008000~0.1,|f:c8c800~0.1,|c:c89600~0.1,|d:00c8b4~0.1,|e:9cdf00~0.1,&legend=1

http://edit.africamuseum.be/edit_wp5/v1.4_dev/rest_gen.php?&image=true&recalculate=false&ms=512,512&bbox=-52.208579,12.692779,84.447524,66.352633&l=background_gis:Y,euromed_2013:Z&title=b:native%2C++doubtfully+native|h:native|c:introduced|d:native%2C++presence+questionable|f:introduced%2C+adventitious+%28casual%29|g:introduced%2C+naturalized|e:present&ad=euromed_2013%3Aparent:h:It,Gg|d:Ca|euromed_2013%3Aemarea:h:Ge,Cs,Hs%28A%29,Ga%28C%29,Tu%28A%29,Uk%28K%29,Sk,La,Uk%28U%29,Hu,Rf%28NW%29,Ar,Au%28L%29,Si%28S%29,Rf%28E%29,Rf%28K%29,Bu,Gr,Ga%28F%29,Da,Rf%28CS%29,Ct,Cg,Rf%28N%29,Tu%28E%29,Rf%28C%29,Lt,Ab%28A%29,Sr,Hs%28S%29,Su,Be%28L%29,Au%28A%29,Si%28M%29,By,Es,Lu,He,Ho,BH,Sl,Rf%28S%29,Rm,Ab%28N%29,Mo,Be%28B%29,Sy,Po,Al,Mk,Ga%28M%29|b:Br|c:Hb%28E%29|e:Sa,Le|f:Hb%28N%29|g:Co&as=Z:ffffff,c8c8c8~|Y:e0faff~|g:c86400~0.1,|h:008000~0.1,|f:c8c800~0.1,|c:c89600~0.1,|d:00c8b4~0.1,|e:9cdf00~0.1,|b:00ff00~0.1,&legend=1

This change however did not have any effect. I tried other approaches but I could not influence the order in any way.

Cheers

Andreas

Actions #2

Updated by Andreas Kohlbecker almost 8 years ago

  • Status changed from New to Resolved
  • Assignee changed from Andreas Kohlbecker to e.raab-straube -

fixed by: r21566, r21565

Hi Eckhard,

the order of the map legend entries should correct now, except of course of the present status which is unwanted. But this is another issue.

please can you check if the legend is actually fixed now?

Andreas

Actions #3

Updated by Eckhard von Raab-Straube almost 8 years ago

Hi Andreas,

I think the order of map legend should be as you have described it, except:

PresenceTerm.INTRODUCED_NATURALIZED

PresenceTerm.INTRODUCED

PresenceTerm.INTRODUCED_ADVENTITIOUS

Eckhard

Actions #4

Updated by Andreas Kohlbecker almost 8 years ago

from email:

Hallo Eckhard,

die Reihenfolge in der Legende entspricht exakt der Priorität der Status, das ist aus zeitlichen Gründen derzeit nicht anders lösbar.

Mehr Flexibilität wäre wünschenswert, da gebe ich dir Recht, ist aber mit einigem Aufwand verbunden, und daher denke ich es ist besser ich kümmere mich um dringlichere Baustellen, wie die Bibliographie aka. Referenzen etc. ich denke das ist in eurem Sinne

Andreas


The subject of this ticket is that the order of map legend entries should conform to term order, this is solved! I will therefore open a new ticket for the freely configurable legend order: #4369 (order of map legend entries freely configurable)

Actions #5

Updated by Andreas Müller over 7 years ago

  • Target version set to cdmlib RELEASE 3.5.0
Actions #6

Updated by Eckhard von Raab-Straube over 7 years ago

Looks like fixed: order is ok, except what I wrote in this ticket before:

"I think the order of map legend should be as you have described it, except:

PresenceTerm.INTRODUCED_NATURALIZED PresenceTerm.INTRODUCED PresenceTerm.INTRODUCED_ADVENTITIOUS"

Example: http://test.e-taxonomy.eu/dataportal/preview/euromed/cdm_dataportal/taxon/f3397e54-17e0-4f97-b276-afdd54d8b047

The colour should get paler in the order, not becoming paler and then darker again.

However, I do not understand why some areas get the "present" status instead of the correct one. E.g., in Solidago candensis, the status for France is "present", whereas the status should in fact be "introduced: naturalised".

In Symphyotrichum squamatum,the status for Italy and Turkey is "present", but it should be "introduced: naturalised"

Andreas M., could you check the data? Something to do with the import or transmission engine?

Actions #7

Updated by Andreas Kohlbecker over 7 years ago

Replying to e.raab-straube:

Looks like fixed: order is ok, except what I wrote in this ticket before:

"I think the order of map legend should be as you have described it, except:

PresenceTerm.INTRODUCED_NATURALIZED PresenceTerm.INTRODUCED PresenceTerm.INTRODUCED_ADVENTITIOUS"

Example:http://test.e-taxonomy.eu/dataportal/preview/euromed/cdm_dataportal/taxon/f3397e54-17e0-4f97-b276-afdd54d8b047

The colour should get paler in the order, not becoming paler and then darker again.

This seems to be a misconfiguration in the edit map server, I will create a new ticket in which we can examine this issue in depth ... #4818

Actions #8

Updated by Andreas Kohlbecker over 7 years ago

Replying to a.kohlbecker:

Replying to e.raab-straube:

Looks like fixed: order is ok, except what I wrote in this ticket before:

"I think the order of map legend should be as you have described it, except:

PresenceTerm.INTRODUCED_NATURALIZED PresenceTerm.INTRODUCED PresenceTerm.INTRODUCED_ADVENTITIOUS"

Example:http://test.e-taxonomy.eu/dataportal/preview/euromed/cdm_dataportal/taxon/f3397e54-17e0-4f97-b276-afdd54d8b047

The colour should get paler in the order, not becoming paler and then darker again.

This seems to be a misconfiguration in the edit map server, I will create a new ticket in which we can examine this issue in depth ... #4818

I misunderstood this, the colors are correct but the order of the introduces status is not correct, it shoul dbe like:

  • PresenceTerm.INTRODUCED_NATURALIZED

  • PresenceTerm.INTRODUCED

  • PresenceTerm.INTRODUCED_ADVENTITIOUS

This (http://euromed.luomus.fi/euromed_map.php?taxon=283364&size=medium) is the reference map for Symphyotrichum squamatum.

Andreas

Actions #9

Updated by Andreas Kohlbecker over 7 years ago

i created a new ticket for the problem with the distribution status present : #4822

Actions #10

Updated by Eckhard von Raab-Straube almost 7 years ago

This is a minor issue, still not fixed. Can be postponed.

Actions #11

Updated by Andreas Kohlbecker almost 7 years ago

  • Status changed from Resolved to In Progress
  • Assignee changed from e.raab-straube - to Andreas Kohlbecker
  • Target version changed from cdmlib RELEASE 3.5.0 to Euro+Med Portal Release
Actions #12

Updated by Andreas Kohlbecker almost 7 years ago

  • Priority changed from Highest to Priority12
Actions #13

Updated by Andreas Müller about 6 years ago

  • Priority changed from Priority12 to Priority14
Actions #14

Updated by Andreas Müller about 6 years ago

Priority increase to have a look to the ticket if time is left until version 1.0 of the portal

Create new ticket for remaining task

Actions #15

Updated by Andreas Müller about 4 years ago

  • Description updated (diff)
  • Estimated time set to 0:30 h
Actions #17

Updated by Andreas Kohlbecker 6 months ago

  • Tags changed from euro+med, migration to euro+med, migration, map
Actions #18

Updated by Andreas Müller 6 months ago

  • Assignee changed from Andreas Kohlbecker to Andreas Müller
  • Private changed from Yes to No
Actions

Also available in: Atom PDF