Ticket #130 (new defect)

Opened 8 years ago

Last modified 8 years ago

alternate range matching

Reported by: igor Owned by: joe
Priority: normal Milestone:
Component: DataProvider Version: 1.2
Severity: normal Keywords:
Cc:

Description

Give users the ability to specify specific ranges, rather than just attempting an intersection match. (mostly for spectral ranges, may also be useful for time ranges)

Change History

comment:1 Changed 8 years ago by joe

This ticket is mainly a reminder -- we had mentioned this in the 0.6 API planning -- adding another keyword to the 'time' or 'wave' structure to specify the match type.

For those data providers that don't support the option, because intersections are the most likely to match, we can always reduce the list in the core, before sending it back.

We'll need the developers to talk, to figure out what type of alternative matching modes to support, and what we want to call them, etc. (this may be a fairly large undertaking, just in coordination)

Note: See TracTickets for help on using tickets.