aodn / aodn-portal

AODN Open Geospatial Portal
https://portal.aodn.org.au/
GNU General Public License v3.0
21 stars 13 forks source link

AODAAC - wrong time range #1157

Closed lbesnard closed 10 years ago

lbesnard commented 10 years ago

On step 2 of an AODAAC product, if a user writes a date which does not exist in ncwms, then on step 3, the taken date is the minimum data of the data set, and not the closest one, which might end up doing a very very long aggregation job

pmbohm commented 10 years ago

@pblain A few alternatives: 1) Users cant manually enter dates (readonly input field) 2) Popup an error when the date is unavailable 3) We calculate the closest date thoughts?

lbesnard commented 10 years ago

Could we do 3) and 2) ?

pblain commented 10 years ago

Is it the portal or the AODAAC doing this? I would have thought the portal would send the AODAAC whatever the user enters. If the date does not exist in ncWMS the AODAAC should handle it - presumably by taking the closest date.

dnahodil commented 10 years ago

This is a Portal problem, it also affects GoGoDuck.

kereid commented 10 years ago

@lbesnard for testing purposes.... I need at least the collection name and also a date that does exist in ncwms and also a date that does not and will cause the long aggregation. Thanks

lbesnard commented 10 years ago

@pblain it is pretty likely the AODAAC would compute the closest date if the portal would send the date entered by the user, but the portal sends the lower limit date first to the AODAAC.

@kereid I'm happy to show you, quite simple to demonstrate, quite complicated to write down

pblain commented 10 years ago

The fix will be to modify the portal to send the aggregator whatever range the user types.

pmbohm commented 10 years ago

Additionally to @pblain 's comment, if the date does not exist the map layer will then not update