Billy Charlton

Rereading issue #846 "Tagging archives for prune" -- I've implemented something fairly different. This is more like git tags, and less like Gmail labels. I think a labeling feature is...

@ThomasWaldmann no specific reason for using the name instead of ID. I thought the archive name would be most identifiable for the user. I could switch to using the ID...

@bstabler Could you create a new Milestone for **Phase 6b Task 4: Visualization** please? I don't have the right permissions. Thanks!

Thank you @vsp-gleich for starting this thread! @kainagel expressed a strong opinion / plea for all standard outputs that are not "internal" working files to use WGS84 lat/long, but I...

> @billyc GPKG works very well in a Python / geopandas / QGIS toolchain, but true, I'm not sure how well-supported the format is elsewhere (in Java I would expect...

@mrieser exactly!! I do that in the Python library already, five points past the decimal are enough to get lat/long accurately on a street map. @neuma I like your summary...

If the team decides to add lat/long to any output files, let's please use a standard naming such as what [kepler.gl expects](https://docs.kepler.gl/docs/user-guides/b-kepler-gl-workflow/a-add-data-to-the-map#2-layer-detection-based-on-column-names): > kepler.gl will auto detect layer, if the...

I think we could add git check-in hooks to enforce commit message format, if we really want to forbid non-compliant checkins. We're not currently enforcing any sort of discipline on...

@michalmac -- yes to everything you just said :-) The commits require discipline, so what I find works best for me is to be loose with my commit logs on...

I second this proposal! Performance is the main problem with OMX as written. Coincidentally I was thinking of building an arrow-based Python proof of concept for this just last week....