Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 20 Jun 2011 18:30:47 +0000 (UTC)
From: "David Smiley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <943035423.21937.1308594647385.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1028318501.19657.1308540047384.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2609) Coordinate range queries do not work
 with Spatial Solr
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052136#comment-13052136 ] 

David Smiley commented on SOLR-2609:
------------------------------------

Yes, this should be a feature request for "Allow arbitrary bbox lat-lon, not limited to circle".  Under the hood, I recall the first order of business is resolving the point-radius to a bounding box. At that point the special prime-meridian logic is handled. It seems it would not be hard to make a patch that ads new parameters for explicit lat-lon bbox params.

> Coordinate range queries do not work with Spatial Solr
> ------------------------------------------------------
>
>                 Key: SOLR-2609
>                 URL: https://issues.apache.org/jira/browse/SOLR-2609
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 3.1
>            Reporter: Zac Smith
>              Labels: spatialsearch
>
> The Spatial Search documentation states that you can create your own bounding box using a range query:
> "Since the LatLonType field also supports field queries and range queries, one can manually create their own bounding box rather than using bbox: ...&q=*:*&fq=store:[45,-94 TO 46,-93]"
> This works unless your range covers an area where longitude goes from 180 to -180. For instance I want all items in the longitude range of 
> 178 to -177 which of course gives no results (it is not a valid numeric range). It's not really surprising that this doesn't work as it is just a standard range query with no spatial filters being applied.
> I am wondering if this is just an issue with the documentation and there is another way that this should be done? Please advise if more details are needed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org