paleolimbot commented on PR #240: URL: https://github.com/apache/parquet-format/pull/240#issuecomment-2272441997
> IIUC, the Covering/kind field has already specified the way to encode the data. For example, WKB for bbox I am a little confused about the bbox in the covering here...a WKB polygon is not sufficient to encode a bbox in more than two dimensions (although the `kind`/`value` proposal is sufficiently flexible that we could evolve that without a thrift change should the use case emerge). > Maybe we should use Standard WKB (no SRID, Z, M value) or ISO WKB (with Z, M value but no SRID) GeoParquet specifies ISO WKB (as a SHOULD) and I think this is what should be used everywhere in this spec. > Do you think Big Endian make sense? I always use little endian because big endian forces looping + swapping endian for each 8 bytes of every ordinate on virtually all modern hardware (unless I am mistaken!). (Neither here nor there for the spec, though, since WKB has the endianness specified in the first byte). -- 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]
