Project

General

Profile

Bug #2505

Spatial query errors with multiple geographic coverages

Added by Matthew Perry about 13 years ago. Updated about 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
07/31/2006
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2505

Description

The current spatial query logic (in the servlet action=spatial_query OR in the advancedSearch) does not properly account for documents containing muliple geographic coverages. It simply checks your search box against the xmlpath for northBoundingCoordinate, south, etc. So queries are actually being run against the bounding box of all bounding boxes. The result is that you may be getting false postives.

For example, lets say we have a document with a geographic coverage in northern Maine AND southern California. Someone performs a spatial query around Kansas and this document will show in the results.

In order to perform the proper query, we'll have to compare the spatial search box against EACH of the geographic coverages in a document. My understanding is that we'll need a way to differentiate, based on the xml path, between different geographicCoverages ?

History

#1 Updated by Matthew Perry about 13 years ago

See bug 2499. Refactoring of spatial harvesting process has this handled.

Instead of representing each document as a single point or polygon, they are now defined as a multi-point (one feature -> mutiple points ) or a multi-polygon.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2505

Also available in: Atom PDF