jiayuasu commented on code in PR #1162:
URL: https://github.com/apache/sedona/pull/1162#discussion_r1436794844
##########
docs/tutorial/sql.md:
##########
@@ -656,6 +656,30 @@ Since v`1.3.0`, Sedona natively supports writing
GeoParquet file. GeoParquet can
df.write.format("geoparquet").save(geoparquetoutputlocation +
"/GeoParquet_File_Name.parquet")
```
+Since v`1.5.1`, Sedona supports writing GeoParquet files with custom
GeoParquet spec version and crs.
Review Comment:
Please also add
`You can find the projjson string of a specific CRS from here:
https://epsg.io/ (click the JSON option at the bottom of the page). You can
also customize your projjson string as needed.`
`Please note that Sedona currently cannot set/get a projjson string to/from
a CRS. Its geoparquet reader will ignore the projjson metadata and you will
have to set your CRS via ST_SetSRID after reading the file. Its geoparquet
writer will not leverage the SRID field of a geometry so you will have to
always set the geoparquet.crs option manually when writing the file, if you
want to write a meaningful CRS field.`
`Due to the same reason, Sedona geoparquet reader and writer do NOT check
the axis order (lon/lat or lat/lon) and assume they are all longitude /
latitude, even if the projjson string might say otherwise. You can always use
ST_FlipCoordinates to swap the axis order of your geometries.`
--
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]
