uros-db commented on code in PR #55790:
URL: https://github.com/apache/spark/pull/55790#discussion_r3226769924


##########
docs/sql-ref-datatypes.md:
##########
@@ -95,8 +95,8 @@ Spark SQL and DataFrames support the following data types:
 
 * Spatial types
   Spatial objects as defined in the [OGC Simple Feature 
Access](https://portal.ogc.org/files/?artifact_id=25355) specification.
-  - `GeometryType`: Represents GEOMETRY values—spatial objects in a Cartesian 
coordinate system. The type can be fixed to a single SRID, e.g. 
`geometry(4326)`, or allow mixed SRIDs with `geometry(any)`. Default SRID when 
not specified is 4326 (WGS 84).
-  - `GeographyType`: Represents GEOGRAPHY values—spatial objects in a 
geographic coordinate system (latitude/longitude). Edge interpolation is always 
SPHERICAL. The type can be fixed to a single SRID, e.g. `geography(4326)`, or 
allow mixed SRIDs with `geography(any)`. Default SRID is 4326 (WGS 84).
+  - `GeometryType`: Represents GEOMETRY values, spatial objects in a Cartesian 
coordinate system. The type must be fixed to a single SRID, e.g. 
`geometry(4326)`, or allow mixed SRIDs with `geometry(any)`. In SQL, `GEOMETRY` 
columns must always be declared with an explicit SRID or `ANY`.
+  - `GeographyType`: Represents GEOGRAPHY values, spatial objects in a 
geographic coordinate system (latitude/longitude). Edge interpolation is always 
SPHERICAL. The type must be fixed to a single geographic SRID, e.g. 
`geography(4326)`, or allow mixed SRIDs with `geography(any)`. In SQL, 
`GEOGRAPHY` columns must always be declared with an explicit SRID or `ANY`.

Review Comment:
   Applied suggestion, thanks!



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to