photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
🌈 An inclusive place for your photos, silliness, and convos! 🌈

Administered by:

Server stats:

265
active users

#geotagging

0 posts0 participants0 posts today
DJ Bonsai<p>Nope, sorry.</p><p><a href="https://bildung.social/tags/DXO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DXO</span></a> <a href="https://bildung.social/tags/PhotoLab8" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhotoLab8</span></a> kommt mir optisch zwar sehr entgegen und macht aus meinen RAWs sogar bessere Bilder als <a href="https://bildung.social/tags/Lightroom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lightroom</span></a>. Auch den Preis hätte ich bezahlt.</p><p>Aber die hohen Upgrade-Preise, fehlende hauseigene Goodies wie <a href="https://bildung.social/tags/HDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HDR</span></a>, Pano, Karten und <a href="https://bildung.social/tags/Geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Geotagging</span></a> bringen mich halt nicht weiter. Schade ums tolle Denoise und so, aber ich arbeite mich jetzt doch mal durch die etwas irre Lernkurve von <span class="h-card" translate="no"><a href="https://photog.social/@darktable" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>darktable</span></a></span> . Bis Ende August brauche ich eine LR-Alternative…</p>
Terence Eden’s Blog<p><strong>Reverse Geocoding is Hard</strong></p><p><a href="https://shkspr.mobi/blog/2025/04/reverse-geocoding-is-hard/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">shkspr.mobi/blog/2025/04/rever</span><span class="invisible">se-geocoding-is-hard/</span></a></p><p>My wife and I run <a href="https://openbenches.org/" rel="nofollow noopener" target="_blank">OpenBenches</a> - a crowd-sourced database of nearly 40,000 memorial benches. Every bench is geo-tagged with a latitude and longitude. But how do you go from a string of digits to something human readable?</p><p>How do I turn <code>-33.755780,150.603769</code> into "42 Wallaby Way, Sydney, Australia"?</p><p>Luckily, that's a (somewhat) solved problem. Services like <a href="https://opencagedata.com/" rel="nofollow noopener" target="_blank">OpenCage</a>, <a href="https://stadiamaps.com/" rel="nofollow noopener" target="_blank">StadiaMaps</a>, <a href="https://nominatim.openstreetmap.org" rel="nofollow noopener" target="_blank">OpenStreetMap</a>, and <a href="https://geocode.earth/" rel="nofollow noopener" target="_blank">Geocode.Earth</a> all provide APIs which transform co-ordinates into addresses. Done! Let's go home.</p><p>Except… Not everywhere <em>has</em> an address. <a href="https://openbenches.org/bench/35905" rel="nofollow noopener" target="_blank">Some benches are in parks</a>. They typically don't have a street number, but might have an interesting feature nearby to help with location. For example a statue or prominent landmark.</p><p>And… Not every address is relevant. <a href="https://openbenches.org/bench/26061" rel="nofollow noopener" target="_blank">Some benches are on streets</a>. But we probably don't want to imply that the bench is <em>inside</em> or belongs to a specific nearby house.</p><p>Let's step back a bit. <em>Why</em> do we want to display a human-readable address?</p><p>We have two use-cases.</p><p>"As a visitor to the site, I want to:"</p><ol><li>Read a (rough) textual representation of where the bench is.</li><li>Click on a component of the address to see all benches within that area.</li></ol><p>The first is easy to explain:</p><p></p><p>The second is harder. Suppose a bench is in Wellington, New Zealand. We want to create a URl like <a href="https://openbenches.org/location/New%20Zealand/Wellington/" rel="nofollow noopener" target="_blank">openbenches.org/location/New Zealand/Wellington/</a>. That way, users can click on the word "Wellington" and find all the benches nearby. A user can also manually edit that URl to increase or decrease precision.</p><p>Both of these are problems of <em>precision</em>.</p><p>Let's take a look at <a href="https://nominatim.openstreetmap.org/reverse?lat=51.476845&amp;lon=-0.295296&amp;format=jsonv2" rel="nofollow noopener" target="_blank">how one of the reverse geocoding services</a> deals with transforming <code>51.476845,-0.295296</code> into an address:</p><blockquote><p>Royal Botanic Gardens, Kew, Sandycombe Road, Kew, London Borough of Richmond upon Thames, London, Greater London, England, TW9 2EN, United Kingdom</p></blockquote><p><strong>That is <em>too much</em> address!</strong></p><p>Yes, it is technically accurate. But it contains far too much detail for humans, the postcode is irrelevant, and the weird-subdivisions are nothing that a local person would use.</p><p>Looking at the full API response, we can see:</p><pre><code>{ "place_id": 258770727, "licence": "Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org/copyright", "name": "Royal Botanic Gardens, Kew", "display_name": "Royal Botanic Gardens, Kew, Elizabeth Cottages, Kew, London Borough of Richmond upon Thames, London, Greater London, England, TW9 3NJ, United Kingdom", "address": { "leisure": "Royal Botanic Gardens, Kew", "road": "Elizabeth Cottages", "suburb": "Kew", "city_district": "London Borough of Richmond upon Thames", "ISO3166-2-lvl8": "GB-RIC", "city": "London", "state_district": "Greater London", "state": "England", "ISO3166-2-lvl4": "GB-ENG", "postcode": "TW9 3NJ", "country": "United Kingdom", "country_code": "gb" }}</code></pre><p>Aha! Perhaps I can build a better address using just those components!</p><p>Except… Not every country has states. And not all states are used when giving addresses. Not every location is in a city. Some places have villages, prefectures, municipalities, and hamlets.</p><p>New York, New York is a valid address, but <a href="https://blog.opencagedata.com/post/99059889253/good-looking-addresses-solving-the-berlin-berlin" rel="nofollow noopener" target="_blank">Berlin, Berlin</a> is not!</p><p>There's an <a href="https://github.com/OpenCageData/address-formatting" rel="nofollow noopener" target="_blank">address formatter by OpenCage</a> which is pretty sensible about stripping off irrelevant details. But, to go back to my first point, not every map location on OpenBenches is a street address and - even if it is on a street - it probably shouldn't have a house number.</p><p>Well, there's kind of a solution to that! Most mapping provider have a POI function - we can find nearby things of interest and use them as a location.</p><p>Here's a <a href="https://openbenches.org/bench/36734" rel="nofollow noopener" target="_blank">bench in Cook County, Illinois, USA</a>. The POI address is:</p><pre><code>{… "name": "Central Park", "coarse_location": "Des Plaines, IL, USA",…}</code></pre><p>I <em>assume</em> there's only one Central Park in Des Plaines. Do people know that "Il" is Illinois? Would "Cook County" be useful?</p><p>On the subject of localisation, not everywhere speaks English. Do I want to display addresses like "<span>原爆の子の像, 広島, 日本</span>"? How about "原爆の子の像, Hiroshima, Japan"?</p><p>We're an international site, but most benches are in Anglophone countries.</p><p>Of course, just because something is <em>physically</em> near a POI, that doesn't mean it is <em>logically</em> close to it.</p><p>Consider a bench situated <a href="https://www.openstreetmap.org/query?lat=50.580682&amp;lon=-3.467831" rel="nofollow noopener" target="_blank">at the edge of this park</a></p><p>The nearest POI is "Gay's Creamery" - across the river. Is that what you'd expect? Is there any way to easily say "if a point is <em>inside</em> an amenity* then use that as the address?</p><p>I don't want the users of our site to have to select from a list of POIs or addresses, this should be as automated as possible.</p><p><strong>The Plan</strong></p><p>For each bench:</p><ol><li>Use StadiaMaps to get the nearest POI.</li><li>Get the data in English.</li><li>Concatenate the name and coarse location.</li><li>Save the "address".</li><li>Wait for complaints?</li></ol><p>Thoughts?</p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/geolocation/" target="_blank">#geolocation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/geotagging/" target="_blank">#geotagging</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://shkspr.mobi/blog/tag/openbenches/" target="_blank">#OpenBenches</a></p>
Jon Sullivan<p>I've just finished geotagging my photos from November and December using <a href="https://mastodon.nz/tags/darktable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>darktable</span></a>. I use the "apply GPX track file" button with tracks from my Garmin GPS, or otherwise the Cyclemeter app on my iPhone, to accurately geolocate my photos. I get much better locations this way. My bigger cameras don't have internal GPS, but I also do this with all my iPhone and Nikon W300 photos. They can otherwise be off by 100 m or so. That difference matters for my nature observations.</p><p><a href="https://mastodon.nz/tags/photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>photography</span></a> <a href="https://mastodon.nz/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a></p>
Tuomas Väisänen 📼🧟‍♂️<p>I wonder why <a href="https://vis.social/tags/Twitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Twitter</span></a> was so popular in <a href="https://vis.social/tags/Turkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Turkey</span></a> in 2012-2015 especially in terms of <a href="https://vis.social/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a> posts?</p><p>We're working on extracting different types of regional <a href="https://vis.social/tags/mobility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mobility</span></a> from the data, and Turkey is over-represented in the data. The amount is approximately 2–3 times the content from Italy, France, and Spain combined.</p>
JL Johnson :veri_mast:<p>I am looking for a lightweight -preferably <a href="https://vmst.io/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a>- PC tool for mass <a href="https://vmst.io/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a> photos, maybe other exif updates. I don't use light room anymore. </p><p>My notes show I used to really be into Microsoft Pro Photo Tools. But that hasn't been updated in 15 years. v2 was released in 2008. HA! </p><p><a href="https://vmst.io/tags/photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>photography</span></a> <a href="https://vmst.io/tags/help" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>help</span></a></p>
Jon Sullivan<p>Here's a friendly reminder of the usefulness of geotagging photos using GPS tracks, even in this age of GPS in cameras and phones.</p><p>These photos are from a weekend run with my Nikon Coolpix W300, a compact waterproof camera with a GPS. The 1st map is where the camera thought it was. The 2nd map is after geotagging with a continuous GPS track.</p><p>The difference can be 100 m in some cases. That's important for nature observations. I see the same with my iPhone photos.</p><p><a href="https://mastodon.nz/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a> <a href="https://mastodon.nz/tags/photos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>photos</span></a> <a href="https://mastodon.nz/tags/map" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>map</span></a></p>
Jon Sullivan<p>A friendly reminder not to blindly trust locations that smart phones add to photos.</p><p>All these were taken in our house, yet their locations from my iPhone 13 span about 1 km.</p><p>It's probably because I took photos inside before my phone had figured out where I was. The same easily happens under a forest canopy.</p><p>This is important when making nature observations for platforms like <a href="https://mastodon.nz/tags/iNaturalist" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iNaturalist</span></a>. I geotag my photos from a GPS track, including my iPhone photos.</p><p><a href="https://mastodon.nz/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a> <a href="https://mastodon.nz/tags/SmartPhone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SmartPhone</span></a> <a href="https://mastodon.nz/tags/photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>photography</span></a></p>
Alex Wild<p>If you are interested in *where* I took a particular photograph on my website www.alexanderwild.com, click on “photo details” and you’ll get EXIF data and a little navigable map at the bottom. </p><p>I have been automatically geotagging my photos since about 2014, and am working through the older ones to add that information. </p><p><a href="https://mastodon.online/tags/insects" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>insects</span></a> <a href="https://mastodon.online/tags/geotagging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geotagging</span></a> <a href="https://mastodon.online/tags/exif" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>exif</span></a> <a href="https://mastodon.online/tags/smugmug" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>smugmug</span></a></p>