Kyle Barron

Maybe it would be useful to consider flatgeobuf's approach of having various ways to represent the CRS: https://github.com/flatgeobuf/flatgeobuf/blob/b013ac326568914aee43bcf3aa3c77574d629aa5/src/fbs/header.fbs#L58-L65. Or STAC's [PROJ extension](https://github.com/stac-extensions/projection/#fields), which allows any of `epsg`, `wkt`, `projjson` but...

> The other notable change here is the change that an omitted CRS defaults to longitude/latitude. Did this get changed back in the PR?

> We could add a "crs_type" key alongside the "crs" to disambiguate the parsing of the string if this is a problem for implementors? I was thinking this might be...

What about converting e.g. from FlatGeobuf to GeoArrow without access to PROJ, such as in the browser or Node. FlatGeobuf doesn't include PROJJSON, so I'd have to include one of...

Being able to put _anything_ in there just smells bad. Reading back through the discussion in https://github.com/geoarrow/geoarrow/issues/8... is `4326` valid input? Do we defer to PROJ for what is valid...

> person? It may just be me... Hey me too! 😂 There's two of us! > This is the reason why I've been implementing GeoParquet and Arrow (not GeoArrow, just...

Yeah, I wasn't clear but I meant to say: you're so close to supporting GeoArrow already! If you just wrap the three columns into a logical struct can give it...

The key is that in arrow the struct is _logical_. So each of the X, Y, Z columns (within the struct!) are still their own separate buffers. If you save...

I agree that we should have some way to declare an unknown CRS, just also feel that we want to store the CRS in _some_ structured way. I actually hit...

Is there ever a case where you want to store multiple representations of the same CRS, so that a consumer can choose whichever is easiest for them to use? Like...