Clarify recommended file extension

[kylebarron]

I've seen a couple instances of users saving files with a .geoparquet file extension. We should provide a recommendation of whether this is allowed or whether we recommend all files to be saved with a .parquet extension. I don't think this is covered yet in the spec.

[cholmes]

Great idea. Would be good to get this in for 1.1 (and I'm realizing we don't have a 1.1 milestone).

Curious on people's thoughts on it? I lean towards just .parquet - fit into the parquet ecosystem as much as possible and don't mess up any other tools that might expect parquet. Only argument I can think the other way is that it's useful to for organizing files to be able to look at them and see they're 'geo'? Wondering if anyone doing this today has strong opinions.

[rouault]

Comparison point: everbody publishes GeoTIFF files as ".tif" (or ".tiff" sometimes), but never as ".geotiff"

[kylebarron]

I'm +1 on recommending .parquet and explicitly discouraging .geoparquet

[TomAugspurger]

+1 for `.parquet`. Dask's `read_parquet` uses the file extension to discover which files under a prefix to read, and (by default) would not find `*.geoparquet` files: https://docs.dask.org/en/stable/generated/dask.dataframe.read_parquet.html#dask.dataframe.read_parquet .

…

On Thu, May 2, 2024 at 9:27 AM Kyle Barron ***@***.***> wrote: I'm +1 on recommending .parquet and explicitly discouraging .geoparquet — Reply to this email directly, view it on GitHub <#211 (comment)> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOIR3WRTRODEOKTGWPQ3ZAJEOJBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVEZTSMJRGUZTQNRZQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGI3TKNRVGA3DKONHORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

[hobu]

*.cog.tif and *.copc.laz is another convention that is commonly seen. Maybe *.geo.parquet could be suggested.

[jwass]

Agreed with .parquet. One of the advantages of GeoParquet is it's backward-compatible with plain parquet readers. If we change the extension that would likely break it for a lot of libraries.

[tschaub]

I also agree that if we recommend anything, it should be *.parquet.

[cholmes]

I'd say we've got consensus. If anyone wants to write the PR then feel free to claim it (assign to yourself or just comment here) - can get on the 'official' contributor list or up your 'commits contributed' to the spec ;)

[answerquest]

Comparison point: everbody publishes GeoTIFF files as ".tif" (or ".tiff" sometimes), but never as ".geotiff"

.geojson be like shucks why do I exist 🤣

chill i'm cool with anything. been saving them as .pqt actually