Some duplicate panoramas who only differ by case

[dustinfreeman]

I did a fresh clone of the repo onto a mac, and noted this warning:

warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

  'data/panoramas/15008b.JPG'
  'data/panoramas/15008b.jpg'
  'data/panoramas/2169.JPG'
  'data/panoramas/2169.jpg'
  'data/panoramas/3053.JPG'
  'data/panoramas/3053.jpg'
  'data/panoramas/3746.JPG'
  'data/panoramas/3746.jpg'
  'data/panoramas/4855.JPG'
  'data/panoramas/4855.jpg'
  'data/panoramas/4978.JPG'
  'data/panoramas/4978.jpg'

I've run a diff on all these pairs and they appear to be identical. However, I'm not sure if this captures metadata or indexing elsewhere...

[LydonThorpe]

They all both resolve and appear to be duplicates. If these duplicates are still in the repo I think it's safe to delete the duplicate ones? I'd say maybe keep the lower case, as that's how extensions are supposed to be done.

@OlivierMorf thoughts?

[OlivierMorf]

I would guess yes. We don't need duplicates. I usually use .jpg (lower case).

[OlivierMorf]

It's a pain we can't use other format. Some and more and more sends HEIC fomat.

[LydonThorpe]

Once we get Willard's tool up and running we could have a set of scripts to automatically convert formats. Until now maybe a GitHub action or something could be set up to find HEICs and convert them?

…

On Tue, May 13, 2025, 4:22 PM Olivier MORF ***@***.***> wrote: *OlivierMorf* left a comment (nycmeshnet/node-db#14) <#14 (comment)> It's a pain we can't use other format. Some and more and more sends HEIC fomat. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A45S3MLZPQFHW2LARIXAVKL26JH73AVCNFSM6AAAAABQ2DCT46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZXHA2DOOBSG4> . You are receiving this because you commented.Message ID: ***@***.***>