umartin commented on code in PR #809:
URL: https://github.com/apache/sedona/pull/809#discussion_r1148862814
##########
docs/tutorial/sql.md:
##########
@@ -212,10 +212,50 @@ root
!!!note
SedonaSQL provides lots of functions to create a Geometry column,
please read [SedonaSQL constructor API](../api/sql/Constructor.md).
+
+## Load GeoJSON using Spark JSON Data Source
+
+Spark SQL's built-in JSON data source supports reading GeoJSON data.
+To ensure proper parsing of the geometry property, we can define a schema with
the geometry property set to type 'string'.
+This prevents Spark from interpreting the property and allows us to use the
ST_GeomFromGeoJSON function for accurate geometry parsing.
+
+=== "Scala/Java"
Review Comment:
Fixed
##########
docs/tutorial/sql.md:
##########
@@ -256,6 +296,66 @@ root
Sedona supports spatial predicate push-down for GeoParquet files, please refer
to the [SedonaSQL query optimizer](../api/sql/Optimizer.md) documentation for
details.
+## Load data from JDBC data sources
+
+The 'query' option in Spark SQL's JDBC data source can be used to convert
geometry columns to a format that Sedona can interpret.
+This should work for most spatial JDBC data sources.
+For Postgis there is no need to add a query to convert geometry types since
it's already using EWKB as it's wire format.
+
+=== "Scala/Java"
Review Comment:
Fixed
--
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]
