Project

General

Profile

Actions
Copy link

feature request #2489

closed

strategy for congruent areas in distribution maps: create merged TDWG layer with all levels

Added by Andreas Kohlbecker almost 13 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Priority13
Assignee:
Andreas Kohlbecker
Category:
cdm-dataportal
Target version:
Release 5.17
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Tags:
map cichorieae

Description

distribution maps sometimes show areas which are congruent. This occurs because the according areas of different levels (TDWG 4 and 3) are marked with the same distribution status. For example Spain in the map for Sonchus tenerrimus:

http://wp6-cichorieae.e-taxonomy.eu/portal/?q=cdm_dataportal/taxon/c15bcde1-71ee-4910-ae84-f9b3fcbdb453

Spain appears darker since the area is rendered twice on time per layer and both semitransparent layers overlap.

A sensible strategy is needed to handle these situations.

In this case the

Related issues

Copied to EDIT - feature request #9122: update shapefile mappings of TDWG areas to the merged shapefile tdwg_levels_1-4FeedbackAndreas Müller

Actions
Actions
Copy link
 #1

Updated by Andreas Kohlbecker over 10 years ago

  • Status changed from New to In Progress

The best solution would be to combine all tdwg layers into one single layer and to have the following four columns in the attribute table (example for northern ireland ):

| tdwg1 | tdwg2 | tdwg3 | tdwg4 |
| 1 | 11 | IRE | IRE-NI |

Actions
Copy link
 #2

Updated by Andreas Kohlbecker over 9 years ago

  • Keywords set to map
Actions
Copy link
 #3

Updated by Andreas Müller almost 9 years ago

  • Target version set to cdm_dataportal - Next Major Release
Actions
Copy link
 #4

Updated by Andreas Kohlbecker over 8 years ago

the approach suggested in comment 1 is not fully sufficient, since the 'areas' that exist of multiple polygons will still have their individual outlines, they are not dissolved or merged.

Further actions are needed to make this work.

see QGis dissolve tool for a possible means

Actions
Copy link
 #5

Updated by Andreas Kohlbecker over 8 years ago

in [#4292#note-10] FranckTheeten mentioned potential problems that could arise from having multiple layers in one shapefile:

"I would recommend to keep them separated. I'm not sure how PostGIS and Geoserver handle overlays, from what I saw today it seems that GeoServer relies on the primary key index of the base layer to handle the z-order at display (the ones with the higher indexes are placed on top of those with lower ), this could prevent displaying a single layer aggregating the 4 zones."

Actions
Copy link
 #6

Updated by Andreas Kohlbecker about 8 years ago

  • Target version changed from cdm_dataportal - Next Major Release to Release 4.0
  • Priority changed from New to Priority14

Yes the render order of the polygons for this layer will for now only be determined by the feature index.

This could be made more deterministic by surrounding each <Rule> elements in the SLD by its own <FeatureTypeStyle>. (Update: see also MapEditing)

See for reference:

The order of <Rule> elements in the SLD already follows the order of the elements in the 'ad' map service parameter.

So simply surrounding each <Rule> element by a <FeatureTypeStyle> should give us the ability to control the render order in merged shape files.

This will make it possible to use a merged TDWG layer with all level (1-4).

Actions
Copy link
 #7

Updated by Andreas Müller almost 8 years ago

  • Target version changed from Release 4.0 to Release 4.1
Actions
Copy link
 #8

Updated by Andreas Müller almost 8 years ago

  • Target version changed from Release 4.1 to Release 4.2
Actions
Copy link
 #9

Updated by Andreas Müller almost 8 years ago

  • Target version changed from Release 4.2 to Release 4.3
Actions
Copy link
 #10

Updated by Andreas Müller over 7 years ago

  • Target version changed from Release 4.3 to Release 4.4
Actions
Copy link
 #11

Updated by Andreas Müller over 7 years ago

  • Target version changed from Release 4.4 to Release 4.5
Actions
Copy link
 #12

Updated by Andreas Müller about 7 years ago

  • Target version changed from Release 4.5 to Release 4.6
Actions
Copy link
 #13

Updated by Andreas Müller about 7 years ago

  • Target version changed from Release 4.6 to Release 4.7
Actions
Copy link
 #14

Updated by Andreas Müller almost 7 years ago

  • Description updated (diff)
  • Private changed from Yes to No
Actions
Copy link
 #15

Updated by Andreas Kohlbecker almost 7 years ago

  • Priority changed from Priority14 to Priority13
  • Target version changed from Release 4.7 to Release 4.8
Actions
Copy link
 #16

Updated by Andreas Müller almost 7 years ago

  • Target version changed from Release 4.8 to Release 4.9
Actions
Copy link
 #17

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.9 to Release 4.10
Actions
Copy link
 #18

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.10 to Release 4.12
Actions
Copy link
 #19

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.12 to Release 4.13
Actions
Copy link
 #20

Updated by Andreas Müller about 6 years ago

  • Target version changed from Release 4.13 to Release 4.14
Actions
Copy link
 #21

Updated by Andreas Müller about 6 years ago

  • Target version changed from Release 4.14 to Release 5.0
Actions
Copy link
 #22

Updated by Andreas Kohlbecker almost 6 years ago

  • Target version changed from Release 5.0 to Release 5.1
Actions
Copy link
 #23

Updated by Andreas Kohlbecker almost 6 years ago

  • Target version changed from Release 5.1 to Release 5.2
Actions
Copy link
 #24

Updated by Andreas Kohlbecker over 5 years ago

  • Target version changed from Release 5.2 to Release 5.3
Actions
Copy link
 #25

Updated by Andreas Kohlbecker over 5 years ago

  • Target version changed from Release 5.3 to Release 5.4
Actions
Copy link
 #26

Updated by Andreas Kohlbecker over 5 years ago

  • Target version changed from Release 5.4 to Release 5.5
Actions
Copy link
 #27

Updated by Andreas Kohlbecker about 5 years ago

  • Target version changed from Release 5.5 to Release 5.6
Actions
Copy link
 #28

Updated by Andreas Kohlbecker about 5 years ago

  • Target version changed from Release 5.6 to Reviewed Next Major Release
Actions
Copy link
 #29

Updated by Andreas Kohlbecker over 4 years ago

  • Tags changed from map to map, cichorieae
  • Subject changed from strategy for congruent areas in distribution maps to strategy for congruent areas in distribution maps: create merged TDWG layer with all levels
Actions
Copy link
 #30

Updated by Andreas Kohlbecker almost 4 years ago

  • Target version changed from Reviewed Next Major Release to Release 5.18
  • % Done changed from 0 to 50
Actions
Copy link
 #31

Updated by Andreas Kohlbecker almost 4 years ago

the merged shapefile has been created an is available at https://github.com/cybertaxonomy/tdwg-area-shapefiles

Actions
Copy link
 #32

Updated by Andreas Kohlbecker almost 4 years ago

to review:

  1. wait until the shapefile is available in the geoserver
  2. test manually if the order of polygons works in the EDIT mapservices
Actions
Copy link
 #33

Updated by Andreas Kohlbecker almost 4 years ago

  • Copied to feature request #9122: update shapefile mappings of TDWG areas to the merged shapefile tdwg_levels_1-4 added
Actions
Copy link
 #34

Updated by Andreas Kohlbecker almost 4 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #35

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100

the new shape file works and the layer order is correct as the following links demonstrates:

http://edit.africamuseum.be/edit_wp5/v1.2/areas.php?ad=tdwg_levels_1_4:tdwg_code:d:AGW-SL|c:AGW|b:85|a:8&as=a:8A90B6,,1|b:C889AD,,1|c:A46479,,1|d:602630,,1&ms=1000,800&bbox=-121.282614,-56.563036,1.764261,-7.368862

Next step is to remap the tdwg area terms at least in the cichorieae db and in the cdmlib resources in general --> #9122

Actions
Copy link
 #36

Updated by Andreas Müller over 3 years ago

  • Target version changed from Release 5.18 to Release 5.17
Actions
Copy link

Also available in: Atom PDF