<\/div>
<\/div>
<\/div><\/div>
<\/p>\n\n\n\n
SELECT ST_Intersects(geom1, geom2);\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n Returns:<\/strong><\/p>\n\n\n\n \nTRUE \u2192 if the geometries overlap or touch<\/li>\n\n\n\n FALSE \u2192 otherwise<\/li>\n<\/ul>\n\n\n\n<\/span>Example<\/span><\/h3>\n\n\n\nSuppose you have:<\/p>\n\n\n\n \na roads<\/em> layer<\/li>\n\n\n\n a municipalities<\/em> layer<\/li>\n<\/ul>\n\n\n\nTo find roads that pass through a municipality:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT r.*\nFROM roads r\nJOIN municipalities c\nON ST_Intersects(r.geom, c.geom)\nWHERE c.name = 'Paris';\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n This query returns all roads that intersect the municipality.<\/p>\n\n\n\n \n\n\n\n<\/span>2. ST_Within<\/span><\/h2>\n\n\n\nST_Within<\/strong> determines whether one geometry is completely contained within another.<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT ST_Within(geom1, geom2);\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n Returns:<\/strong><\/p>\n\n\n\n \nTRUE \u2192 if the first geometry is entirely inside the second<\/li>\n\n\n\n FALSE \u2192 otherwise<\/li>\n<\/ul>\n\n\n\n<\/span>Example<\/span><\/h3>\n\n\n\nTo find schools located inside a municipality:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT s.*\nFROM schools s\nJOIN municipalities c\nON ST_Within(s.geom, c.geom)\nWHERE c.name = 'Paris';\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n This query returns only the schools fully located within the municipality.<\/p>\n\n\n\n \n\n\n\n<\/span>3. Key Difference<\/span><\/h2>\n\n\n\nThe main distinction is straightforward:<\/p>\n\n\n\n Function<\/th> Meaning<\/th><\/tr><\/thead> ST_Intersects<\/td> Geometries share at least one point<\/td><\/tr> ST_Within<\/td> One geometry is completely inside another<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<\/span>What is the difference between ST_Intersects and ST_Within?<\/strong><\/span><\/h3>\n\n\n\nST_Intersects returns TRUE when two geometries share at least one point, while ST_Within returns TRUE only when one geometry is completely contained within another.<\/p>\n\n\n\n \n\n\n\n<\/span>4. When to Use Each<\/span><\/h2>\n\n\n\n<\/span>Use ST_Intersects for:<\/span><\/h3>\n\n\n\n\nroads crossing an area<\/li>\n\n\n\n overlapping zones<\/li>\n\n\n\n detecting any spatial contact<\/li>\n<\/ul>\n\n\n\n<\/span>Use ST_Within for:<\/span><\/h3>\n\n\n\n\nchecking if a point lies inside a polygon<\/li>\n\n\n\n verifying full containment within a boundary<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>5. Conceptual Examples<\/span><\/h2>\n\n\n\nConsider three scenarios:<\/p>\n\n\n\n \nA point inside a polygon<\/strong> \u2192 ST_Within = TRUE \u2192 ST_Intersects = TRUE<\/li>\n\n\n\n A line crossing a polygon<\/strong> \u2192 ST_Within = FALSE \u2192 ST_Intersects = TRUE<\/li>\n\n\n\n Two separate geometries<\/strong> \u2192 ST_Within = FALSE \u2192 ST_Intersects = FALSE<\/li>\n<\/ol>\n\n\n\n \n\n\n\n<\/span>6. Performance and Spatial Indexes<\/span><\/h2>\n\n\n\nBoth ST_Intersects<\/strong> and ST_Within<\/strong> can leverage spatial indexes.<\/p>\n\n\n\n Creating a GiST index is highly recommended:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nCREATE INDEX idx_roads_geom\nON roads\nUSING GIST (geom);\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n This significantly improves query performance.<\/p>\n\n\n\n \n\n\n\n<\/span>Conclusion<\/span><\/h2>\n\n\n\nST_Intersects<\/strong> and ST_Within<\/strong> are fundamental tools in PostGIS<\/a> for analyzing spatial relationships.<\/p>\n\n\n\n \nST_Intersects<\/strong> \u2192 checks if geometries touch or overlap<\/li>\n\n\n\n ST_Within<\/strong> \u2192 checks if one geometry is entirely contained within another<\/li>\n<\/ul>\n\n\n\nUnderstanding their differences helps you write more accurate and efficient spatial queries.<\/p>\n\n\n\n \n\n\n\n<\/span>Common Spatial Relationship Functions in PostGIS<\/span><\/h2>\n\n\n\nPostGIS provides several functions to analyze relationships between geometries:<\/p>\n\n\n\n Function<\/th> Meaning<\/th><\/tr><\/thead> ST_Intersects<\/td> Geometries share at least one point<\/td><\/tr> ST_Within<\/td> One geometry is inside another<\/td><\/tr> ST_Contains<\/td> One geometry fully contains another<\/td><\/tr> ST_Touches<\/td> Geometries touch but interiors do not overlap<\/td><\/tr> ST_Overlaps<\/td> Geometries partially overlap<\/td><\/tr> ST_Crosses<\/td> Geometries cross each other<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n\n\n\n<\/a>from \u00ab\u00a0Analysis of Spatial Relations Based on Elements\u00a0\u00bb:https:\/\/ikcest-drr.data.ac.cn\/tutorial\/k1034<\/a><\/figcaption><\/figure>\n\n\n\n \n\n\n\n<\/span>ST_Contains vs ST_Within<\/span><\/h2>\n\n\n\nThese two functions are often confused\u2014they are actually inverses.<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nST_Within(point, polygon)\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n is equivalent to:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nST_Contains(polygon, point)\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n <\/span>Example<\/span><\/h3>\n\n\n\nTo find schools within a municipality:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT s.*\nFROM schools s\nJOIN municipalities c\nON ST_Within(s.geom, c.geom)\nWHERE c.name = 'Paris';\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n Or equivalently:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT s.*\nFROM schools s\nJOIN municipalities c\nON ST_Contains(c.geom, s.geom)\nWHERE c.name = 'Paris';\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n \n\n\n\n<\/span>Performance Tip<\/span><\/h2>\n\n\n\nFor large datasets, combine spatial functions with a bounding box filter to improve performance:<\/p>\n\n\n <\/div><\/div><\/div><\/div><\/p>\n\n\n\nSELECT s.*\nFROM schools s\nJOIN municipalities c\nON s.geom && c.geom\nAND ST_Within(s.geom, c.geom);\n<\/code><\/pre>\n\n\n\n<\/div><\/div>\n\n\n\n The &&<\/code> operator compares bounding boxes and reduces the number of geometries to evaluate.<\/p>\n\n\n\n \n\n\n\n<\/span>Key Takeaways<\/span><\/h2>\n\n\n\n\nST_Intersects<\/strong> \u2192 the most general spatial relationship<\/li>\n\n\n\n ST_Within<\/strong> \u2192 strict containment<\/li>\n\n\n\n ST_Contains<\/strong> \u2192 inverse of ST_Within<\/li>\n\n\n\n ST_Touches<\/strong> \u2192 contact without overlap<\/li>\n<\/ul>\n\n\n\nThese functions are essential for building efficient spatial queries in PostGIS.<\/p>\n\n\n\n \n\n\n\n.<\/p>\n","protected":false},"excerpt":{"rendered":" When working with PostGIS, understanding spatial relationships between geometries is essential for building efficient queries. Two of the most widely used functions\u2014ST_Intersects and ST_Within\u2014are often confused, yet they serve different purposes. In this guide, you\u2019ll learn…<\/p>\n","protected":false},"author":1,"featured_media":16605,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[3264],"tags":[4642],"class_list":["post-16739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postgis-fr-es-en","tag-postgis-spatial-relationships-st_intersects-example-st_within-postgis-postgis-spatial-queries-difference-between-st_intersects-and-st_within-postgis-geometry-functions-st_contains-vs-st_within"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.sigterritoires.fr\/wp-content\/uploads\/2026\/03\/st_dwithin.png?fit=500%2C400&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-4lZ","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/16739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=16739"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/16739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media\/16605"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=16739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=16739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=16739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}