Hello,
I am indexing WKT polygons on a RptWithGeometrySpatialField defined as follows:
<fieldType name="location_grpt" class="solr.RptWithGeometrySpatialField"
spatialContextFactory="JTS" autoIndex="true"
geo="true" distErrPct="0.5" maxDistErr="1"
distanceUnits="kilometers" />
I am currently experimenting on tuning the values of distErrPct and maxDistErr.
>From my experiments, increasing the value of distErrPct from the default 0.15
>to 0.5 greatly increases indexing speed (5 times faster), however, only
>increasing maxDistErr from 0.001 to 1 has no impact at all.
I have a few questions:
· I do not understand clearly from the documentation how do distErrPct
and maxDistErr relate to each other and what explains that changing maxDistErr
does not have impact. Is it possible to further explain the relationship
between those two values?
· From the documentation, whatever is the value of distErrPct, with
RptWithGeometrySpatialField my queries will always be fully precise. Is it
correct? So why not always putting the value to 0.5, which seems to improve
indexing performance and I am not measuring major query speed impact.
· Lastly, the documentation says that RptWithGeometrySpatialField is
particularly optimized for INTERSECTS. Most of my queries are currently testing
the intersections of a box with indexed polygons. The box is transformed to a
coordinated range query, such as myfield:[49.9,57.0 TO 72.8,160.1] . Should I
modify my code to do explicitly an INTERSECTS for better performances or is my
query automatically converted to an INTERSECTS?
Thank you in advance!
Benoît
------------------------------------------------------------------------------
E-MAIL DISCLAIMER
The present message may contain confidential and/or legally privileged
information. If you are not the intended addressee and in case of a
transmission error, please notify the sender immediately and destroy this
E-mail. Disclosure, reproduction or distribution of this document and its
possible attachments is strictly forbidden.
SPACEBEL denies all liability for incomplete, improper, inaccurate,
intercepted, (partly) destroyed, lost and/or belated transmission of the
current information given that unencrypted electronic transmission cannot
currently be guaranteed to be secure or error free.
Upon request or in conformity with formal, contractual agreements, an
originally signed hard copy will be sent to you to confirm the information
contained in this E-mail.
SPACEBEL denies all liability where E-mail is used for private use.
SPACEBEL cannot be held responsible for possible viruses that might corrupt
this message and/or your computer system.
-------------------------------------------------------------------------------
