Opened 12 years ago
Closed 11 years ago
#276 closed feature (fixed)
time handling with SECORE and temporal CRS
Reported by: | abeccati | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | critical | Milestone: | 9.0 |
Component: | petascope | Version: | |
Keywords: | Cc: | swingit | |
Complexity: | Very Hard |
Description (last modified by )
SECORE provides CRS definition that supersedes an ordinary axis type field. Petascope shall make use of SECORE to resolve axis information and provide response accordingly.
To be noted that use of SECORE might still offer backward compatibility with existing clients, provide axis labels are parameterised accordingly.
Change History (4)
comment:1 by , 12 years ago
Component: | DEB → petascope |
---|
comment:2 by , 11 years ago
Cc: | added |
---|---|
Complexity: | → Very Hard |
Description: | modified (diff) |
Priority: | major → critical |
Status: | new → assigned |
Type: | defect → feature |
comment:3 by , 11 years ago
Status: | assigned → accepted |
---|
comment:4 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
Feature added in changeset:afcebaa (merge of
feature_PetascopeSecore
intomaster
).