Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EDE83D1AA for ; Fri, 21 Sep 2012 14:15:08 +0000 (UTC) Received: (qmail 54221 invoked by uid 500); 21 Sep 2012 14:15:07 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 54177 invoked by uid 500); 21 Sep 2012 14:15:07 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 54169 invoked by uid 99); 21 Sep 2012 14:15:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2012 14:15:07 +0000 Date: Sat, 22 Sep 2012 01:15:07 +1100 (NCT) From: "David Smiley (JIRA)" To: dev@lucene.apache.org Message-ID: <1470003826.107722.1348236907669.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (SOLR-3864) Spatial maxDetailDist doesn't follow degrees standardization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 David Smiley created SOLR-3864: ---------------------------------- Summary: Spatial maxDetailDist doesn't follow degrees standardization Key: SOLR-3864 URL: https://issues.apache.org/jira/browse/SOLR-3864 Project: Solr Issue Type: Bug Components: Schema and Analysis Reporter: David Smiley Assignee: David Smiley Technically this bug is in Lucene spatial but it's on a factory that is only really used by the Solr adapter, plus I added a mandatory attribute so I decided to file it here. The maxDetailDist attribute on SpatialRecursivePrefixTreeFieldType is interpreted as kilometers for a geospatial context. However, for this first release of spatial, all distances are standardized on degrees. Of course I want to support kilometers but not inconsistently and there isn't time for that right now. Because this is likely to be a common problem of interpreting distances for this field, I decided to add a mandatory attribute "units" which must be "degrees". When kilometers is supported then it will be added. Furthermore, the name "maxDetailDist" as a name isn't so great. As part of some renames related to this sort of thing a month back I overlooked this one. I think "maxDistErr" is better and more consistent with attributes such as "distErr" you can put in shape query. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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