Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map search not working properly #4

Open
ccaudill opened this issue Dec 16, 2014 · 5 comments
Open

Map search not working properly #4

ccaudill opened this issue Dec 16, 2014 · 5 comments

Comments

@ccaudill
Copy link
Collaborator

When you do a search at http://demo.geothermaldata.org/map_search, soon to be http://data.geothermaldata.org/map_search, there is not a URL created which allows a user to save the search or send that search link to someone else. See this properly functioning in the Library search:
ngds-links

This is a problem, because the new main page Drupal site uses a search box much like at http://www.geothermaldata.org/ where the term can take the user to the Map search with that term and results loaded - this cannot happen without forming the URL as seen above in the Library search. This was working in the Map Search in the old code, but didn't carry over to demo.
@FuhuXia
@pjbarry21
@skmar

@ccaudill
Copy link
Collaborator Author

Perhaps this helps? "I spoke with Adrian about this, he says that a post request needs to be written in for the Map search to work from the Drupal site. But as it is now the map search from the Drupal site won't work." https://github.com/ngds/ckanext-ngds/issues/339

@ccaudill
Copy link
Collaborator Author

The map search is not working in the newest build (http://159.87.39.5/map_search). Cannot search by term or BB. @FuhuXia

@ccaudill ccaudill added this to the REI milestone Feb 12, 2015
@FuhuXia
Copy link
Collaborator

FuhuXia commented Mar 3, 2015

This issue is related to the mapsearch extension design and volume of datasets. It turns out a postgres db query is used to process the bbox spatial info, then all qualified dataset ids are collected from db and passed to solr query. When the id collection gets large, solr cant handles the large query and returns error. So when total datasets is in hundreds, or the bbox is small, the search works fine. When bbox is large and/or total datasets grow to thousands, the issue will surface. To fix the issue, we need to change the way mapsearch extension do spatial search, it needs to pass bbox info to the solr and let solr process spatial info, not postgres db.

@ccaudill
Copy link
Collaborator Author

ccaudill commented Mar 3, 2015

Excellent - I'm glad you know what's going on there

@FuhuXia
Copy link
Collaborator

FuhuXia commented Mar 11, 2015

This issue has been addressed in rpm version 307. To the end user mapsearch is working now. On the backend we have not completed the coding to move all spatial queries to solr, instead we increased the capability for solr so it wont give error when accepting large id collection from ckan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants