anchor.diff:  
   Here's an example:
   
  -`&q=*:*&fq=store:[45,-94 TO 46,-93]`
  +[source,text]
  +&q=*:*&fq=store:[45,-94 TO 46,-93]
   
   LatLonType (deprecated) does *not* support rectangles that cross the dateline. For RPT and BBoxField, if you are non-geospatial coordinates (`geo="false"`) then you must quote the points due to the space, e.g., `"x y"`.
   
  
positive.code: 
  `format`:: Defines the shape syntax/format to be used. Defaults to `WKT` but `GeoJSON` is another popular format. Spatial4j governs this feature and supports https://locationtech.github.io/spatial4j/apidocs/org/locationtech/spatial4j/io/package-frame.html[other formats]. If a given shape is parseable as "lat,lon" or "x y" then that is always supported.
  
  `distanceUnits`:: a|
  This is used to specify the units for distance measurements used throughout the use of this field. This can be `degrees`, `kilometers` or `miles`. It is applied to nearly all distance measurements involving the field: `maxDistErr`, `distErr`, `d`, `geodist` and the `score` when score is `distance`, `area`, or `area2d`. However, it doesn't affect distances embedded in WKT strings, (e.g., `BUFFER(POINT(200 10),0.2)`), which are still in degrees.
  +
  `distanceUnits` defaults to either `kilometers` if `geo` is true`, or `degrees` if `geo` is `false`.
  +
  `distanceUnits` replaces the `units` attribute; which is now deprecated and mutually exclusive with this attribute.
  
  
negative.code: 
  `geodist` is a distance function that takes three optional parameters: `(sfield,latitude,longitude)`. You can use the `geodist` function to sort results by distance or score return results.
  
  For example, to sort your results by ascending distance, use a request like:
  
  [source,text]
  &q=*:*&fq={!geofilt}&sfield=store&pt=45.15,-93.85&d=50&sort=geodist() asc
  
  To return the distance as the document score, use a request like:
  
  [source,text]
  &q={!func}geodist()&sfield=store&pt=45.15,-93.85&sort=score+asc&fl=*,score
  
  == More Spatial Search Examples
  
  