jorisvandenbossche commented on PR #240: URL: https://github.com/apache/parquet-format/pull/240#issuecomment-2427188380
Related to the last major round of updates (summarized at https://github.com/apache/parquet-format/pull/240#issuecomment-2395099696), considering the change for where to put the CRS description: > > Offloaded the CRS representation to Parquet file metadata fields such that multiple geometry columns can refer to the same CRS. This also makes sure that the Parquet spec does not rely on another spec for CRS. > > This seems like a very strange way to parameterize the CRS to me that doesn't simplify the specification I agree with @paleolimbot that this indirection does not simplify the specification, and indeed does let any other discussion point (how should the CRS be described, PROJJSON or something else?) go away. Could you provide some more rationale for why the spec would choose to put the CRS descriptions in the FileMetaData key_value_metadata, and then per column refer to a key in that metadata? I understand that if you have many geometry columns with the same CRS that this saves some space, but are there other reasons for this design? (my feeling is that the many-geometry-columns use case is not worth the added complexity) -- 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]
