uros-db commented on code in PR #560:
URL: https://github.com/apache/parquet-format/pull/560#discussion_r3014956958


##########
Geospatial.md:
##########
@@ -44,8 +44,12 @@ locations on Earth.
 The default CRS `OGC:CRS84` means that the geospatial features must be stored
 in the order of longitude/latitude based on the WGS84 datum.
 
-Custom CRS can be specified by a string value. It is recommended to use an
-identifier-based approach like [Spatial reference identifier][srid].
+Non-defaullt CRS values are specified by any string that uniquely identifies 
coordinate reference system associated with this type.
+To maximize interoperability suggested (but not limited to) formats for CRS 
are:
+* `authorithy:identifier` - where `authorithy` represents some well known 
authorities - examples are `OGC:CRS84`, `OGC:CRS83`, `OGC:CRS27`.
+* `inlined_projjson` - Inlining whole CRS definition in 
[PROJJSON](https://proj.org/en/stable/specifications/projjson.html) format.
+* `srid:identifier` - [SRID - Spatial reference 
identifier](https://en.wikipedia.org/wiki/Spatial_reference_system#Identifier), 
`identifier` is the SRID itself.
+* `projjson:table_property_name` - where `table_property_name` is the name of 
a table property where the projjson string is stored

Review Comment:
   ```suggestion
   * `authorithy:identifier`- A reference using a well-known authority and its 
identifier. For example: `OGC:CRS83`.
   * `srid:identifier` - A reference using a Spatial Reference Identifier 
(SRID), where identifier is the numeric SRID value. For example: `SRID:0`.
   * `projjson` - A complete CRS definition embedded directly using the 
[PROJJSON](https://proj.org/en/stable/specifications/projjson.html) 
specification.
   * `projjson:table_property_name` - A reference to a CRS definition stored as 
a table property, where `table_property_name` identifies the property 
containing the 
[PROJJSON](https://proj.org/en/stable/specifications/projjson.html) string.
   ```



-- 
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