Geospatial Element Child Index Configuration Help

A Geospatial Element Child Index accelerates geospatial queries.

Each Geospatial Element Child Index keeps track of the points appearing in all XML elements or JSON properties with a given name and parent.

Geospatial Element Child Indexes also allow you to use the cts:element-child-geospatial-query or cts:json-property-child-geospatial-query constructor in searches.

Configure the following for each Geospatial Element Child Index:

• The parent namespace uri specifies the namespace URI of the parent element.
• The parent localname specifies the local name of the parent XML element or the name of the parent JSON property.
• namespace uri specifies the namespace for an element or an attribute.
• localname specifies the localname for an XML element/attribute or the name for a JSON property.
• coordinate system specifies the name of the coordinate sytem used for the geospatial data. The default of wgs84 is useful for most commercial geospatial data. Use raw when you want your points mapped onto a flat plane instead of onto the geometry of the earth. Adding /double to the end of the coordinate system name means that the coordinate system uses double precision floating point numbers instead of single precision floating point numbers. For example, wgs84/double uses double precision.
• point format describes the point format in the data: "point" means latitude precedes longitude; "long-lat-point" means longitude precedes latitude.
• range value positions specifies whether index data should be included that speeds up the performance of proximity queries involving range queries. Turn this index off if you are not interested in proximity queries and if you want to conserve disk space and decrease loading time.
• invalid values specifies whether server should allow insertion of documents that contain XML elements or JSON properties on which range index is configured and their contents cannot be coerced to the index data type. It can be configured to either ignore or reject. By default server rejects insertion of such documents. However, if a user configures invalid values to ignore, these documents can be inserted. This setting does not change the behavior of queries on invalid values after documents are inserted in the database. Performing an operation on an invalid value at query time can still result in an error.

---

Buttons and Tabs:

• Use the Configure tab to edit existing geospatial element child index configurations. Click the delete button corresponding to a geospatial element child index to remove it.
• Use the Add tab to add new geospatial element child indexes to the database configuration.