Skip to content

Commit d0c7fbc

Browse files
committed
address issues with spatial indexing docs
1 parent f7fb2ea commit d0c7fbc

File tree

4 files changed

+15
-14
lines changed

4 files changed

+15
-14
lines changed

articles/cosmos-db/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -431,12 +431,12 @@
431431
- name: Geospatial overview
432432
displayName: geospatial, spatial
433433
href: sql-query-geospatial-intro.md
434-
- name: Querying geospatial data
434+
- name: Query geospatial data
435435
displayName: geospatial, spatial, query
436436
href: sql-query-geospatial-query.md
437-
- name: Indexing geospatial data
438-
displayName: geospatial, spatial, indexing
439-
href: sql-query-geospatial-indexing.md
437+
- name: Index geospatial data
438+
displayName: geospatial, spatial, index
439+
href: sql-query-geospatial-index.md
440440
- name: Parameterized query
441441
displayName: parameterized query, parameterized, parameter, parameters
442442
href: sql-query-parameterized-queries.md

articles/cosmos-db/sql-query-geospatial-indexing.md renamed to articles/cosmos-db/sql-query-geospatial-index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Indexing geospatial data with Azure Cosmos DB
2+
title: Index geospatial data with Azure Cosmos DB
33
description: Index spatial data with Azure Cosmos DB
44
author: timsander1
55
ms.service: cosmos-db
@@ -8,7 +8,7 @@ ms.date: 02/20/2020
88
ms.author: tisande
99

1010
---
11-
# Indexing geospatial data with Azure Cosmos DB
11+
# Index geospatial data with Azure Cosmos DB
1212

1313
We designed Azure Cosmos DB’s database engine to be truly schema agnostic and provide first class support for JSON. The write optimized database engine of Azure Cosmos DB natively understands spatial data represented in the GeoJSON standard.
1414

articles/cosmos-db/sql-query-geospatial-intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,4 +195,4 @@ Now that you have learned how to get started with geospatial support in Azure Co
195195

196196
* Learn more about [Azure Cosmos DB Query](sql-query-getting-started.md)
197197
* Learn more about [Querying spatial data with Azure Cosmos DB](sql-query-geospatial-query.md)
198-
* Learn more about [Indexing spatial data with Azure Cosmos DB](sql-query-geospatial-indexing.md)
198+
* Learn more about [Index spatial data with Azure Cosmos DB](sql-query-geospatial-index.md)

articles/cosmos-db/sql-query-geospatial-query.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Here is a list of geospatial system functions useful for querying in Azure Cosmo
2424
|ST_ISVALID| Returns a Boolean value indicating whether the specified GeoJSON Point, Polygon, or LineString expression is valid.|
2525
| ST_ISVALIDDETAILED| Returns a JSON value containing a Boolean value if the specified GeoJSON Point, Polygon, or LineString expression is valid. If invalid, it returns the reason as a string value.|
2626

27-
Spatial functions can be used to perform proximity queries against spatial data. For example, here's a query that returns all family documents that are within 30 km of the specified location using the ST_DISTANCE built-in function.
27+
Spatial functions can be used to perform proximity queries against spatial data. For example, here's a query that returns all family documents that are within 30 km of the specified location using the `ST_DISTANCE` built-in function.
2828

2929
**Query**
3030

@@ -42,7 +42,7 @@ Spatial functions can be used to perform proximity queries against spatial data.
4242
}]
4343
```
4444

45-
If you include spatial indexing in your indexing policy, then "distance queries" will be served efficiently through the index. For more information on spatial indexing, see [geospatial indexing](sql-query-geospatial-indexing.md). If you don't have a spatial index for the specified paths, the query will do a scan of the container.
45+
If you include spatial indexing in your indexing policy, then "distance queries" will be served efficiently through the index. For more information on spatial indexing, see [geospatial indexing](sql-query-geospatial-index.md). If you don't have a spatial index for the specified paths, the query will do a scan of the container.
4646

4747
`ST_WITHIN` can be used to check if a point lies within a Polygon. Commonly Polygons are used to represent boundaries like zip codes, state boundaries, or natural formations. Again if you include spatial indexing in your indexing policy, then "within" queries will be served efficiently through the index.
4848

@@ -94,7 +94,7 @@ Azure Cosmos DB also supports performing inverse queries, that is, you can index
9494
}]
9595
```
9696

97-
`ST_ISVALID` and `ST_ISVALIDDETAILED` can be used to check if a spatial object is valid. For example, the following query checks the validity of a point with an out of range latitude value (-132.8). ST_ISVALID returns just a Boolean value, and ST_ISVALIDDETAILED returns the Boolean and a string containing the reason why it is considered invalid.
97+
`ST_ISVALID` and `ST_ISVALIDDETAILED` can be used to check if a spatial object is valid. For example, the following query checks the validity of a point with an out of range latitude value (-132.8). `ST_ISVALID` returns just a Boolean value, and `ST_ISVALIDDETAILED` returns the Boolean and a string containing the reason why it is considered invalid.
9898

9999
**Query**
100100

@@ -110,7 +110,7 @@ Azure Cosmos DB also supports performing inverse queries, that is, you can index
110110
}]
111111
```
112112

113-
These functions can also be used to validate Polygons. For example, here we use `ST_ISVALIDDETAILED` to validate a Polygon that is not closed.
113+
These functions can also be used to validate Polygons. For example, here we use `ST_ISVALIDDETAILED` to validate a Polygon that is not closed.
114114

115115
**Query**
116116

@@ -131,8 +131,9 @@ These functions can also be used to validate Polygons. For example, here we use
131131
}]
132132
```
133133

134-
## LINQ Querying in the .NET SDK
135-
The SQL .NET SDK also providers stub methods `Distance()` and `Within()` for use within LINQ expressions. The SQL LINQ provider translates this method calls to the equivalent SQL built-in function calls (ST_DISTANCE and ST_WITHIN respectively).
134+
## LINQ querying in the .NET SDK
135+
136+
The SQL .NET SDK also providers stub methods `Distance()` and `Within()` for use within LINQ expressions. The SQL LINQ provider translates this method calls to the equivalent SQL built-in function calls (ST_DISTANCE and ST_WITHIN respectively).
136137

137138
Here's an example of a LINQ query that finds all documents in the Azure Cosmos container whose `location` value is within a radius of 30 km of the specified point using LINQ.
138139

@@ -176,4 +177,4 @@ Now that you have learned how to get started with geospatial support in Azure Co
176177

177178
* Learn more about [Azure Cosmos DB Query](sql-query-getting-started.md)
178179
* Learn more about [Geospatial and GeoJSON location data in Azure Cosmos DB](sql-query-geospatial-intro.md)
179-
* Learn more about [Indexing spatial data with Azure Cosmos DB](sql-query-geospatial-indexing.md)
180+
* Learn more about [Index spatial data with Azure Cosmos DB](sql-query-geospatial-index.md)

0 commit comments

Comments
 (0)