Skip to content

Conversation

@sergiusens
Copy link

Serves at least as a temporary measure.

I tested with what I have ORF and RAF. I used claude to write the boilerplate (having already partially done this manually for another project)

image image

Alleviates #40

Signed-off-by: Sergio Schvezov [email protected]

@CyberTimon
Copy link
Owner

Thank you very much for your work. It’s great to see pull requests moving in this direction.

I noticed that you are now formatting the EXIF data in the backend. With the previous EXIF library, all EXIF data was extracted directly from the image and then sent to the frontend. The MetadataPanel is responsible for mapping the programmatic names to the displayed values, including the “All EXIF Data” section.

Have you already tried simply fetching the raw EXIF data from the backend and handling the parsing in the frontend? The current approach introduces an issue: part of the parsing happens in the backend, and then parsing happens again in the frontend. I hope my question makes sense.

Thank you again for your work.

@sergiusens
Copy link
Author

I understand, I only added the parsing later on as I was seeing raw exif data, but I will take another look and if I can figure out why what was happening

@sergiusens sergiusens force-pushed the rawexif branch 2 times, most recently from d09290d to 7fc5fdf Compare December 22, 2025 20:03
@sergiusens
Copy link
Author

I found some time @CyberTimon, and have pushed an update

Additionally add logic to extract GPS info from RAF.

Signed-off-by: Sergio Schvezov <[email protected]>
@sergiusens
Copy link
Author

rebased to remove conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants