Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of david.w.smiley@gmail.com
 designates 209.85.160.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <BFE16376743FF645B5745106A7C968B619A51975@AUS-P-EXMB32.EX.URS.COM>
References: <BFE16376743FF645B5745106A7C968B619A48826@AUS-P-EXMB32.EX.URS.COM>
	<CABEwPvF+w-HZUe+WQuc3EYpV3LKFtGJhKuVqhLmgJTzRBkHb+A@mail.gmail.com>
	<07DF13AABD377140ADD3FE3E3B097F857F169DBF@se-ex024.groupinfra.com>
	<BFE16376743FF645B5745106A7C968B619A4C74B@AUS-P-EXMB32.EX.URS.COM>
	<BFE16376743FF645B5745106A7C968B619A51324@AUS-P-EXMB32.EX.URS.COM>
	<BFE16376743FF645B5745106A7C968B619A5135E@AUS-P-EXMB32.EX.URS.COM>
	<CABEwPvF-3Tn3gLH2sFnnV6=rFQQj2Qd=m3=m+UpGoq+YCigERQ@mail.gmail.com>
	<BFE16376743FF645B5745106A7C968B619A5149E@AUS-P-EXMB32.EX.URS.COM>
	<CABEwPvH7p3naw-=ZG=rqBCqLdikvEfNQpruurvJLFTaKbqJ-Hg@mail.gmail.com>
	<BFE16376743FF645B5745106A7C968B619A515C1@AUS-P-EXMB32.EX.URS.COM>
	<BFE16376743FF645B5745106A7C968B619A517F0@AUS-P-EXMB32.EX.URS.COM>
	<CABEwPvEqDmarfkON8EcUok3tgU+FDkuqeLdPCdhoHBBSFWTz_Q@mail.gmail.com>
	<BFE16376743FF645B5745106A7C968B619A51943@AUS-P-EXMB32.EX.URS.COM>
	<BFE16376743FF645B5745106A7C968B619A51975@AUS-P-EXMB32.EX.URS.COM>
Date: Sun, 24 Aug 2014 09:20:05 -0400
Message-ID: 
 <CABEwPvEX2XWgjxLqY6nshJDR2_Zd2G2oZtDikH8MGNQTOf7xsw@mail.gmail.com>
Subject: Re: Indexing and Querying MS SQL Server 2012 Spatial
From: "david.w.smiley@gmail.com" <david.w.smiley@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 24, 2014 at 2:29 AM, Bostic, Alex <alex.bostic@urs.com> wrote:
> Ok updating my field type to the below, allowed me to index :-) HUGE THAN=
KS
>
> <fieldType name=3D"location_rpt" class=3D"solr.SpatialRecursivePrefixTree=
FieldType" spatialContextFactory=3D"com.spatial4j.core.context.jts.JtsSpati=
alContextFactory"
>         geo=3D"false" distErrPct=3D"0.025" maxDistErr=3D"0.000009" units=
=3D"degrees" worldBounds=3D"ENVELOPE(-150281000,150281000,74670000,-5792200=
0)" />
>
> Two more questions:
> Should I update maxDistErr?

Definitely, yes.  The value you have there is based on a meter when
geo=3Dtrue.  Apparently  you are using a projection (geo=3D=E2=80=9Cfalse=
=E2=80=9D), and
you should pick a value corresponding to the maximum precision you
want in your projected space.  It appears that 7.5 is a meter,
assuming the min & max X you have above represent the entire world (on
earth).  Maybe you can afford to be less precise, and save time on
indexing.

FYI you should check out my blog post related:
http://www.opensourceconnections.com/blog/2014/04/11/indexing-polygons-in-l=
ucene-with-accuracy/

>
> Is it possible to use the SQL Server Geometry type and convert it to WKT =
in the data-config file as shown below, or is there still an issue that I a=
m not seeing
>
> query=3D"SELECT wt.Id, wt.Name, wt.WorkTypeTypeId,wt.ChildId,wt.CreatedDa=
te,wt.ModifiedDate,wt.Year, wta.GEOM.STAsText(), wta.OBJECTID,wta.WTArea
>   FROM dbo.WorkTypes wt Inner Join dbo.WorkTypeAreas wta ON wt.Id =3D wta=
.WorkTypeId">
>
> wta.GEOM.STAsText() <- does not show in the index, is of type SQL Server =
Geometry
>
> wta.WTArea <- does show in the index, is of type varchar(max)
>
> they are defined similarly in schema.xml
> <field name=3D"geom" type=3D"location_rpt" indexed=3D"true" stored=3D"tru=
e"/>
>
> <field name=3D"wtarea" type=3D"location_rpt" indexed=3D"true" stored=3D"t=
rue" />

I don=E2=80=99t know=E2=80=A6 this is related to SQL Server and not Lucene/=
Solr.

~ David
p.s. I=E2=80=99m going to FOSS4G next month.  There are at least 2 talks ab=
out
Lucene spatial.