Geography Types
Note
Bing Maps for Enterprise service retirement
Bing Maps for Enterprise is deprecated and will be retired. Free (Basic) account customers can continue to use Bing Maps for Enterprise services until June 30th, 2025. Enterprise account customers can continue to use Bing Maps for Enterprise services until June 30th, 2028. To avoid service disruptions, all implementations using Bing Maps for Enterprise REST APIs and SDKs will need to be updated to use Azure Maps by the retirement date that applies to your Bing Maps for Enterprise account type.
Azure Maps is Microsoft's next-generation maps and geospatial services for developers. Azure Maps has many of the same features as Bing Maps for Enterprise, and more. To get started with Azure Maps, create a free Azure subscription and an Azure Maps account. For more information about azure Maps, see Azure Maps Documentation. For migration guidance, see Bing Maps Migration Overview.
These geography types can be used to:
Add a geography property to a data source entity schema. See Data Schema and Sample Input.
Query for entities that are within a specified geography using the 'intersects' spatial filter. See Query Options.
Query for entities and return the intersection of the geography for each entity with a specified geography using the 'intersections' function. See Query Options.
Limits and Requirements
The maximum number of points for any entity geography value is 100,000.
The maximum number of points for the 'intersects' spatial filter and 'intersection' function is 250.
When using CSV format to define entity data, enclose the geography description in quotes ("").
When using 'intersects' and 'intersection' functions, enclose the geography description in single quotes(' ').
Recommended Geographies
The following geography types are recommended to give the best performance when querying.
| Attribute | Description | Input Data Type | OData Data Type |
|---|---|---|---|
| Point | A pair of latitude and longitude values. For a more detailed description, see Point. Examples: POINT(116.03059 44.49031) |
well-known text (WKT) | Edm.Geography |
| LineString | A set of latitude and longitude values that are connected by line segments. For a more detailed description and examples, see LineString. For CSV files, this value must be enclosed in quotes ("") when the value contains a comma (,). Examples: LINESTRING(-116.03059 44.49031, -116.03117 44.4928) CSV file: "LINESTRING (-116.03059 44.49031, -116.03117 44.4928)" |
well-known text (WKT) | Edm.Geography |
| Polygon | One or more sets of latitude and longitude points that describe a closed outer shape and closed shapes within the outer shape. The area of the polygon is the space between the inner and outer shape boundaries. Points are connected by line segments. The first and last points of each set must be the same. For a more detailed description and examples, see Polygon. For CSV files, this value must be enclosed in quotes ("") when the value contains a comma (,). Examples: POLYGON ((-95.44067 48.6559, -95.44083 48.66306, …-95.44067 48.6559)) CSV file: "POLYGON ((-95.44067 48.6559, -95.44083 48.66306, …-95.44067 48.6559))" |
well-known text (WKT) | Edm.Geography |
Other Geographies
The following geography types are supported, but for best performance when querying, use line string, polygon and point types.
| Attribute | Description | Input Data Type | OData Data Type |
|---|---|---|---|
| MultiPoint | A set of points. For a more detailed description and examples, see MultiPoint. For CSV files, this value must be enclosed in quotes ("") when the value contains a comma (,). Examples: MULTIPOINT((-122.3, 47),( -121.3 47)) CSV file: "MULTIPOINT((-122.3, 47),( -121.3 47))" |
well-known text (WKT) | Edm.Geography |
| MultiLineString | A set of line strings. For a more detailed description and examples, see MultiLineString. For CSV files, this value must be enclosed in quotes ("") when the value contains a comma (,). Examples: MULTILINESTRING((-122.3 47, -121.3 47), (-121.3 45, -122.3 47)) CSV file: "MULTILINESTRING((-122.3 47, -121.3 47), (-121.3 45, -122.3 47))" |
well-known text (WKT) | Edm.Geography |
| MultiPolygon | A set of polygons that to not overlap. For a more detailed description and examples, see MultiPolygon. Examples: MULTIPOLYGON((-95.44067 48.6559, -95.44083 48.66306, -95.43524 48.66315, -95.44067 48.6559)),((-95.43503 48.65588, -95.42981 48.65556, -95.4297 48.6524, -95.43503 48.65588))) CSV file: " MULTIPOLYGON((-95.44067 48.6559, -95.44083 48.66306, -95.43524 48.66315, -95.44067 48.6559)),((-95.43503 48.65588, -95.42981 48.65556, -95.4297 48.6524, -95.43503 48.65588)))" |
well-known text (WKT) | Edm.Geography |
| GeometryCollection | A set of multiple geography types. For a more detailed description and examples, see GeometryCollection. For CSV files, this value must be enclosed in quotes ("") when the value contains a comma (,). Examples: GEOMETRYCOLLECTION(POINT(116.03059 44.49031),LINESTRING(-115.92223 44.23223, -115.73234 44.432784)) CSV file: "GEOMETRYCOLLECTION(POINT(116.03059 44.49031),LINESTRING(-115.92223 44.23223, -115.73234 44.432784))" |
well-known text (WKT) | Edm.Geography |