ckan / ckan/ckanext-spatial

Search filter failure

Open
#77 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
XSLT
Stars
136
Forks
207
PR merge metrics
No merged PRs in 30d

Description

G'Day all,

My apologies for this issue: it is surely something to do with PostGIS, but perhaps others may find similar problems.

We have the extension installed and it is displaying bbox outlines on datasets. This should indicate that the geoJSON is being stored with the record, and can be displayed on the preview map. Indeed, I can see the data rows in the package_extra table.

However, when we try to filter datasets based on bbox input, no records are returned.
After double checking the bbox extents and making sure that the filter _should_ run, I decided to look in the database itself.

Investigating the package_extent table, I can see three rows there that look like good candidates for spatial data...looks like this:
6b99eac7-c849-4fb8-ac35-7d3b1568f38b 0103000020E610000001000000050000008B6CE7FBA9B961402497FF907E7B2AC08B6CE7FBA9B96140F0164850FCF827C0CFF753E3A5EB6140F0164850FCF827C0CFF753E3A5EB61402497FF907E7B2AC08B6CE7FBA9B961402497FF907E7B2AC0

So this should mean that our record entry process is sound since we're getting rows written to the db. But why can't we see a filtered result? We simply get "No records found" after applying the filter.

Looking in the logs I can see we have a stack of PostgreSQL errors like these:
2014-06-20 01:39:56 UTC LOG: could not receive data from client: Connection reset by peer
2014-06-20 01:39:56 UTC LOG: unexpected EOF on client connection

At this point I am out of clues oor ideas on how to further troubleshoot.
Any assistance much appreciated!

![20-06-2014 11-44-37 am](https://cloud.githubusercontent.com/assets/582702/3336709/00c2918a-f839-11e3-86e7-5afcfa65c151.jpg)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.