https://bugs.kde.org/show_bug.cgi?id=431689

Mehmet gelisin <mehmetgeli...@aol.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgeli...@aol.com

--- Comment #31 from Mehmet gelisin <mehmetgeli...@aol.com> ---
I'm trying to use Digikam to establish a photo processing workflow entirely
based on open source software. http://www.compilatori.com/

On the input/import end, I'm using OsmAnd on Android to collect GPS tracks,
OpenCamera on Android to take photos. Then I use Digikam to GPS correlate
tracks & photos from my discrete http://connstr.net/ camera (and also to
supplement Android photos with DOP values from the OsmAnd tracks, which the
Android platform doesn't yet support recording in EXIF natively). Currently, I
do all other editing & photo processing within Digikam. http://joerg.li/

For exporting, I typically publish (currently via batch uploads of files
through the web interfaces of each platform) to five different target
platforms: Strava (a group for http://www.jopspeech.com/  stewards of our local
wilderness trail), Facebook (valuable to support discussions with a broader
community not on other platforms), Flickr (mostly as fairly large, "free" cloud
storage), Wordpress (self-hosted), and iNaturalist. Anything I can do to
automate / optimize / cut out redundancy in my workflow would greatly improve
life for me.

A significant barrier in this workflow to uploading efficiently to the
iNaturalist platform is submissions through their web interface of large photo
sets. In Chromium, http://www.wearelondonmade.com/ it is necessary to partition
sets of greater than about 30 photos at a time into subsets, otherwise my
Atom-based workstation with 8G RAM runs out of memory to handle the page.
Integration with Digikam done properly would likely help with this.

The main feature request & other useful features all sound like things that
would help me too. I'd love to see something started, and then those additional
requests filed as separate wishlists once work is underway.

As a professional software developer, primarily in Ruby these days, but with
some proficiency in other languages, and also as a Debian developer of some
years, helping develop an iNaturalist export extension for digikam is certainly
something I'd be interested in exploring. I must caution, though, that I have
no KDE development experience. I don't think that's a huge barrier to me making
some sort of contribution, but it probably rules me out as being a driver for
this effort.

I'm trying to use Digikam to establish a photo processing workflow entirely
based on open source software.

On the input/import end, I'm using OsmAnd on Android to collect GPS tracks,
OpenCamera on Android to take photos. Then I use Digikam to GPS correlate
tracks & photos from my discrete camera (and also to supplement Android photos
with DOP values from the OsmAnd tracks, which the Android platform doesn't yet
support recording in EXIF natively). Currently, I do all other editing & photo
processing within Digikam.

For exporting, I typically publish (currently via batch uploads of files
through the web interfaces of each platform) to five different target
platforms: Strava (a group for stewards of our http://embermanchester.uk/ local
wilderness trail), Facebook (valuable to support discussions with a broader
community not on other platforms), Flickr (mostly as fairly large, "free" cloud
storage), Wordpress (self-hosted), and iNaturalist. http://www.slipstone.co.uk/
Anything I can do to automate / optimize / cut out redundancy in my workflow
would greatly improve life for me.

A significant barrier in this workflow to http://www.logoarts.co.uk/ uploading
efficiently to the iNaturalist platform is submissions through their web
interface of large photo sets. In Chromium, it is necessary to partition sets
of greater than about 30 photos at http://www.acpirateradio.co.uk/  a time into
subsets, otherwise my Atom-based workstation with 8G RAM runs out of memory to
handle the page. Integration with Digikam done properly would likely help with
this.
https://waytowhatsnext.com/ 
The main feature request & other useful features all sound like things that
would help me too. I'd love to see something started, and then those additional
requests filed as separate wishlists once work is underway.
https://www.webb-dev.co.uk/

As a professional software developer, primarily in Ruby these days, but with
some proficiency in other languages, and also as a Debian developer of some
years, helping develop an http://www.iu-bloomington.com/ iNaturalist export
extension for digikam is certainly something I'd be interested in exploring. I
must caution, though, that I have no KDE development experience. I don't think
that's a huge barrier to me making some sort of contribution, but it
http://www-look-4.com/  probably rules me out as being a driver for this
effort.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to