lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "david.w.smiley@gmail.com" <david.w.smi...@gmail.com>
Subject Re: Indexing and Querying MS SQL Server 2012 Spatial
Date Wed, 20 Aug 2014 17:49:28 GMT
Hi Alex,

I guess a spatial tutorial might be helpful, but there isn’t one.  There is
a sample at the Lucene-spatial layer but not up at Solr.  You need to use
WKT syntax for line’s and polys, and you may do so as well for other
shapes.  And in the schema use location_rpt copied from Solr’s example
schema for starters, but modified as the ref guide & wiki show to use JTS.
 The ref guide, wiki, and I would guess that book should show how to to a
bounding box query using {!bbox} — it’s pretty simple.

~ David Smiley
Freelance Apache Lucene/Solr Search Consultant/Developer
http://www.linkedin.com/in/davidwsmiley


On Tue, Aug 19, 2014 at 11:25 AM, Bostic, Alex <alex.bostic@urs.com> wrote:

> Hello I'm new to Solr:
> I have a SQL Server 2012 database with spatial columns (points/lines/polys)
> Do you have any resources to point to for the following
> Creating a Solr index of a sql server spatial table
> Bounding Box query (intersect) example, possibly with front-end from GMaps
> or OpenLayers
>  I'm currently reading Apache Solr Beginner's Guide and have reviewed
> https://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4
> I am able to index and query my non spatial data, I am just looking for
> some resource that may have some more detail about how to set everything up.
> I can provide more detail if needed.
> Thanks
>
> Alex Bostic
> GIS Developer
> URS Corporation
> 12420 Milestone Center Drive, Suite 150
> Germantown, MD 20876
> direct line: 301-820-3287
> cell line: 301-213-2639
>
>
>
> This e-mail and any attachments contain URS Corporation confidential
> information that may be proprietary or privileged. If you receive this
> message in error or are not the intended recipient, you should not retain,
> distribute, disclose or use any of this information and you should destroy
> the e-mail and any attachments or copies.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message