Opened 5 years ago

Closed 21 months ago

#150 closed enhancement (fixed)

SECORE: disallow and flag nested composition

Reported by: pbaumann Owned by: bphamhuu
Priority: minor Milestone: Future
Component: secore Version: 8.3
Keywords: Cc: dmisev
Complexity: Medium

Description

as per OGC Abstract Topic 2, compound CRSs shall not contain compounds again - hence, no recursion in CRS URL composition.

SECORE should have a check on this in the resolver, it should return a suitable exception.

Change History (9)

comment:1 Changed 5 years ago by pbaumann

  • Milestone set to Future

comment:2 Changed 5 years ago by pbaumann

  • Version set to 8.3

comment:3 Changed 5 years ago by pbaumann

  • Component changed from applications to SECORE
  • Owner changed from dmisev to mrusu

adjusted component.

comment:4 Changed 5 years ago by pbaumann

  • Owner changed from mrusu to dmisev
  • Status changed from new to assigned

oops, seems I inadvertently changed the owner. Undoing that.

comment:5 Changed 23 months ago by bphamhuu

  • Complexity set to Very Hard
  • Owner changed from dmisev to bphamhuu

As Dimitar has suggested before, so I will take this ticket and try to understand SECORE.

comment:6 Changed 23 months ago by bphamhuu

  • Complexity changed from Very Hard to Medium

comment:7 Changed 21 months ago by bphamhuu

Hi Prof. Peter,

I'd like to ask for your clarification about "nested composition" as I and Dimiar has different perspectives:

+ Dimitar thinks an exception should be thrown in this case (nested "crs-compound" flag in URL).

http://localhost:8088/def/crs-compound?
1=http://localhost:8088/def/crs-compound?1=...

+ I think an exception should be thrown in this case (nested "crs type: GeodeticCRS, ProjectedCRS, TemporalCRS,..." as from Compound CRS definition of OGC). So 2 or more CRS types can be combined but not "duplicate CRS types" as (GeodeticCRS + GeodeticCRS) as below:

http://localhost:8088/def/crs-compound?
1=http://localhost:8088/def/crs/EPSG/0/4326&
2=http://localhost:8088/def/crs/EPSG/0/4326

Please help us with your consideration.

comment:8 Changed 21 months ago by dmisev

I think it's clear from this in the description:

compound CRSs shall not contain compounds again - hence, no recursion in CRS URL composition

+ I think an exception should be thrown in this case (nested "crs type: GeodeticCRS, ProjectedCRS, TemporalCRS,..." as from Compound CRS definition of OGC). So 2 or more CRS types can be combined but not "duplicate CRS types" as (GeodeticCRS + GeodeticCRS) as below:

I think we discussed this in another ticket as well. It's an unnecessary restriction, and I'm not sure what's the reason for it. This ticket is not suitable for this however, we should open a new ticket.

comment:9 Changed 21 months ago by dmisev

  • Resolution set to fixed
  • Status changed from assigned to closed

This ticket can be closed actually, as secore now throws an exception when a compound CRS contains further compound CRS.

Note: See TracTickets for help on using tickets.