search

aodn / aodn-portal

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

WMS spatial constraint not updated for new collections #1225

Closed pmbohm closed 10 years ago

pmbohm commented 10 years ago

To reproduce

Add a collection (with filters) Draw a Spatial Extent Add a new collection (with filters) Go to Step 3

What does happen

The latest collection does not show any spatial extent filter info

What should happen

All collections (with filters) will include spatial extent when the spatial extent has been defined. The spatial extent will also be defined identically for both ncWMS and WMS layers

jkburges commented 10 years ago

I'm unable to re-create this one.

danfruehauf commented 10 years ago

See if it's related to #1250.

jkburges commented 10 years ago

I'm seeing #1250 - but is that what is meant here by "latest collection does not show any spatial extent filter info"? I had assumed it was talking about on step 2. In any case step 2 looks ok, so this is possibly just a duplicate (or vice-versa).

danfruehauf commented 10 years ago

Related to #1217, where layers need to exist to have a spatial extent attached to them.

dnahodil commented 10 years ago

@jkburges I can demonstrate this one to you if you like?

danfruehauf commented 10 years ago

@dnahodil It happens to be that 2fc76867e22c628d2223394aa136054173b12de0 introduced this bug.

Can you recall the reason behind it?

danfruehauf commented 10 years ago

Tracing back to #1121.

Need a different fix for that I guess.

kereid commented 10 years ago

Adding new test cases to testrail and trialing as I do so and found this one to not be resolved so re-opening

dnahodil commented 10 years ago

Closing as this is fixed in current RC

kereid commented 10 years ago

Seeing this in rc today

spatial extent

anguss00 commented 10 years ago

Tested this morning on production v3.29.3. Cannot replicate the bug on either production or RC, so going to close this one