search

bsed / ala

Automatically exported from code.google.com/p/ala
0 stars 0 forks source link

Add to Map | Facet fails against an 'All areas' #474

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Reported by Robyn Lawrence at my seminar on 11/12/2013.

Add to map | Areas | Gazetteer polygon - Namadgi Wilderness Zone
Add to map | Areas | Gazetteer polygon - Namadgi NP
Add to map | Areas | Gazetteer polygon - Kosiusko NP

Add to Map | Facet | All areas

Fails with Error 404 after about 5 minutes (insult to injury)

Tried 

Export | All areas | shapefile/WKT and KML and then
Import | Areas shape/KML/WKT but same failure on all formats

Original issue reported on code.google.com by leebel...@gmail.com on 18 Dec 2013 at 4:30

Attachments:

GoogleCodeExporter commented 9 years ago 
There is no easy fix for this one.  The issues relates to performing geospatial 
searches on multiple complex areas. Biocache-service is performing an "OR" 
search on each of these WKT.  Given the complexity of these areas this is an 
expensive operation. With all three of these areas included the search times 
out with SOLR.

There are a couple of solution:
1) Disable the "All area layers" options. Instead provide an action that merges 
selected area layers together and make the users use the merged layer.

2) Make biocache-service union the WKT together and only search for one WKT.  
Main issue with this one is that the resulting WKT is not exact based on JTS 
lib: See FAQ D7 - http://tsusiatsoftware.net/jts/jts-faq/jts-faq.html 

Either way we may need to modify biocache-service so that a search timeout 
param can be provided.

I am going to downgrade this issue because it has been working this way for 
almost the entire year. Also there is no time to address it before the end of 
the year.

Original comment by natasha....@csiro.au on 19 Dec 2013 at 11:16

GoogleCodeExporter commented 9 years ago 
Thanks Natasha. See Issue #270 as I think this remains the best strategy. 

This is an important issue to address as we need to remove limitations in being 
able to build 'complex' areas. This reasoning was behind my push to provide 14 
different options in 'Add to map | areas'. I hadn't figured on a 15th, but time 
suggested otherwise. The improvement of the Area report is likely to also to 
put pressure for 15 (or equivalent - so long as a merge is possible). 
Currently, a manual addition could require a lot of work.

Original comment by leebel...@gmail.com on 20 Dec 2013 at 12:07

GoogleCodeExporter commented 9 years ago 
Reassigning to Adam. During the meeting we had when Adam was in Canberra we 
discussed this as a task. ie the merging layers into a single layer for 
querying purposes

There may also be a biocache-service search "timeout" aspect to be handled too.

Original comment by natasha....@csiro.au on 7 Apr 2014 at 3:53

GoogleCodeExporter commented 9 years ago 
Attempts are made to keep WKT sent to biocache below the new parameter 
max_q_wkt_length.  Still need to tell users when this occurs because what is 
mapped as the area is not what biocache queries operate on.

Original comment by adam.col...@gmail.com on 2 May 2014 at 2:27

GoogleCodeExporter commented 9 years ago 
This works now really well - and VERY fast for the example from Robyn Lawrence 
#1.

ToProd once the Warning is implemented.

Original comment by leebel...@gmail.com on 5 May 2014 at 1:44

GoogleCodeExporter commented 9 years ago

Original comment by adam.col...@gmail.com on 20 May 2014 at 12:17