Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

APPROX_GEOGRAPHY_INTERSECTS

On this page

The APPROX_GEOGRAPHY_INTERSECTS() function is the fast approximate version of GEOGRAPHY_INTERSECTS. It takes in two geospatial objects and determines whether any part of them overlap.

Approximate results are obtained by consulting the geospatial indexes (if any) for matches, and skipping the filter phase which reduces the result set to objects that truly intersect. This means that the rows returned by this function will have false positives but no false negatives.

Image of geographic area with intersecting lines overlaying the area

Syntax

APPROX_GEOGRAPHY_INTERSECTS ( geo1, geo2 )

Arguments

  • geo1, geo2: any valid geospatial object or WKT string: path, point or polygon.

Important

If both geo1 and geo2 are points, this function only returns true if they are identical.

Return Type

Boolean

Examples

SELECT COUNT(1)
    -> FROM jogging_paths j1, jogging_paths j2
    -> WHERE
    -> APPROX_GEOGRAPHY_INTERSECTS(j1.shape, j2.shape);
+----------+
| COUNT(1) |
+----------+
|    11569 |
+----------+
SELECT COUNT(1)
    -> FROM jogging_paths j1, jogging_paths j2
    -> WHERE
    -> GEOGRAPHY_INTERSECTS(j1.shape, j2.shape);
+----------+
| COUNT(1) |
+----------+
|     9134 |
+----------+
 SELECT *
 FROM neighborhoods WITH (index = shape, resolution = 16)
 WHERE APPROX_GEOGRAPHY_INTERSECTS(shape,"POLYGON(...)");

Important

The with (index = c, resolution = n) syntax is an optional optimization discussed in Special Spatial Tuning Parameters.

Related Topics

For more information about working with geospatial data, see Working with Geospatial Features.

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In