feature request #2489: strategy for congruent areas in distribution maps: create merged TDWG layer with all levels - EDIT - EDIT Project Management

Custom queries

5.33
cdm-dataportal (open)
last 7 days tickets
mine in current release
phycobank
phycobank-index-closed
phycobank-registration-closed
potentially missed issues
recently updated
Release3.7
Release3.8
Release4.0
Release4.1
Release4.10
Release4.11
Release4.12
Release4.13
Release4.14
Release4.16
Release4.2
Release4.3
Release4.4
Release4.5
Release4.6
Release4.7
Release4.8
Release4.9
Release4.9
Release5.0
Release5.1
Release5.10
Release5.11
Release5.12
Release5.13
Release5.14
Release5.15
Release5.16
Release5.17
Release5.18
Release5.19
Release5.2
Release5.20
Release5.21
Release5.22
Release5.23
Release5.24
Release5.25
Release5.26
Release5.27
Release5.28
Release5.29
Release5.3
Release5.30
Release5.31
Release5.32
Release5.33
Release5.34
Release5.35
Release5.36
Release5.37
Release5.38
Release5.39
Release5.4
Release5.40
Release5.41
Release5.5
Release5.6
Release5.7
Release5.8
Release5.9
Remoting-Versions
Taxeditor-UX (Platform Etablierung)

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-4

Feedback

Andreas Müller

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

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 ):

Actions

Copy link

Updated by Andreas Kohlbecker over 9 years ago

Keywords set to map

Actions

Copy link

Updated by Andreas Müller almost 9 years ago

Target version set to cdm_dataportal - Next Major Release

Actions

Copy link

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

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

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:

https://wiki.state.ma.us/confluence/display/massgis/GeoServer+-+SLD+-+Order+of+Drawing+Features
http://boundlessgeo.com/2014/04/deterministic-rendering-order-in-sld/

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

Updated by Andreas Müller almost 8 years ago

Target version changed from Release 4.0 to Release 4.1

Actions

Copy link

Updated by Andreas Müller almost 8 years ago

Target version changed from Release 4.1 to Release 4.2

Actions

Copy link

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