Metacat Servlet action=spatial_query returns incorrect results
It appears that the metacat spatial query (metacat?action=spatial_query) does not return correct results. Based on a few test cases, it appears that only spatial queries which intersect the north-west corner of the geographic coverage return a correct result. This indicates a rather serious error in the spatial intersection logic.
Updated by Matthew Perry over 16 years ago
1) handleSpatialQuery called createSpatialquery w/ parameters in the wrong order
2) createSpatialQuery's logic was wrong; changed to match the logic specified in AdvancedSearch.java:
/* * Else, if the user does not select the boundaryContained checkbox, use the * following logical expression. N, S, E, and W are the boundaries of the * bounding box, while N', S', E', and W' are the boundaries specified in a * given EML document: * (N' > S) && (S' < N) && (E' > W) && (W' < E)