Context Navigation

← Previous Ticket
Next Ticket →

#1510 closed defect (fixed)

wrong subset syntax in WCS-T?

Reported by:	Peter Baumann	Owned by:	Bang Pham Huu
Priority:	major	Milestone:	9.4
Component:	petascope	Version:	development
Keywords:		Cc:	Dimitar Misev, Bang Pham Huu
Complexity:	Easy

Description

it seems that the subsetting parameter in WCS-T are not implemented according to the standard ("subset=…") but like "subset1=…,subset2=…".
Actions:

check implementation
if really deviating, adjust to std

Change History (8)

comment:1 by Dimitar Misev, 7 years ago

Cc:	Bang Pham Huu added

any updates?

comment:2 by Vlad Merticariu, 7 years ago

WCS-T reuses the subset parameters used by WCS. The implementation currently supports both:

http://ows.rasdaman.org/rasdaman/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageId=AvgLandTemp&subset=Lat(0)&subset=Long(0)&subset=ansi("2000-02-01T00:00:00.000Z")

and

http://ows.rasdaman.org/rasdaman/ows?service=WCS&version=2.0.1&request=GetCoverage&coverageId=AvgLandTemp&subset1=Lat(0)&subset2=Long(0)&subset3=ansi("2000-02-01T00:00:00.000Z")

comment:3 by Dimitar Misev, 7 years ago

so we can close the ticket?

comment:4 by Bang Pham Huu, 7 years ago

if Petascope supported then it needs to be fixed in wcst_import to use the subset parameter only.

comment:5 by Peter Baumann, 7 years ago

hm, why are we supporting something nonstandard? I cannot remember a conscious design decision for this. Neither I can see any advantage. However, it is confusing for users.

comment:6 by Dimitar Misev, 7 years ago

Priority:	critical → major

Ok so this is nothing critical. As discussed, wcst_import will be changed to support the standard syntax.

comment:7 by Dimitar Misev, 7 years ago

Owner:	changed from Vlad Merticariu to Bang Pham Huu
Status:	new → assigned

comment:8 by Bang Pham Huu, 7 years ago

Resolution:	→ fixed
Status:	assigned → closed

Note: See TracTickets for help on using tickets.

Download in other formats: