# Geotagging with polygons

**URL:** <https://tagspaces.discourse.group/t/geotagging-with-polygons/26>\
**Category:** Feature requests\
**Created:** [November 21, 2022, 6:17pm UTC](https://tagspaces.discourse.group/t/geotagging-with-polygons/26 "2022-11-21T18:17:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![grekouiconia](https://avatars.discourse-cdn.com/v4/letter/g/ea666f/32.png) [@grekouiconia](https://tagspaces.discourse.group/u/grekouiconia)\
**Post date:** [November 21, 2022, 6:17pm UTC](https://tagspaces.discourse.group/t/geotagging-with-polygons/26/1 "2022-11-21T18:17:37Z")

</div>

I’ve been working in the mining/environment sector (public organizations) for quite a while  
A major problem that we ve been facing -a problem that not even expensive software like ESRI’s ArcInfo can deal with - it only supports one coordinate tagging I think) is “projecting” documents on an **area** : that is relating a document (usually a digitally signed pdf document) with a POLYGON (or multiple polygons ) on a map  
eg a permit for a mine/ a factory/ a wind mill , a prohibition, a lease …even a survey (in a university library) etc refer to an AREA NOT to a POINT!  
so if tag spaces could show/project in a separate window (maybe from google earth-pro ??) a kml or shp that may have the same name with a pdf and is found in the same folder (eg permit1.pdf and permit1.kml) , that would make tagspaces unique in handling such data and far more handy than any other free or paid software!!

---

<div class="post-metadata">

**Author:** ![rokejulianlockhart](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/rokejulianlockhart/32/20_2.png) [@rokejulianlockhart](https://tagspaces.discourse.group/u/rokejulianlockhart)\
**Post date:** [February 9, 2023, 11:28pm UTC](https://tagspaces.discourse.group/t/geotagging-with-polygons/26/2 "2023-02-09T23:28:00Z")

</div>

I thought that TagSpaces didn’t even support UTM co-ordinates. It only shows Plus Codes and MGRS for me.

---

<div class="post-metadata">

**Author:** ![ilian](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/ilian/32/6_2.png) [@ilian](https://tagspaces.discourse.group/u/ilian)\
**Post date:** [February 10, 2023, 12:35pm UTC](https://tagspaces.discourse.group/t/geotagging-with-polygons/26/3 "2023-02-10T12:35:01Z")

</div>

The geotags in Plus Code format can be easily transformed into an UTM coordinates. We are actually already using this in the app:

 ![image](https://global.discourse-cdn.com/free1/uploads/tagspaces/original/1X/ee0492f3e5281b1162f11f45895a16bb406a4f99.png)  
We use Plus Code because they can encode latitude and longitude with a lot less characters, which is useful when you have tags in the file names.

---

<div class="post-metadata">

**Author:** ![rokejulianlockhart](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/rokejulianlockhart/32/20_2.png) [@rokejulianlockhart](https://tagspaces.discourse.group/u/rokejulianlockhart)\
**Post date:** [February 16, 2023, 3:07pm UTC](https://tagspaces.discourse.group/t/geotagging-with-polygons/26/4 "2023-02-16T15:07:29Z")

</div>

@ilian, per [Support UTM co-ordinates for geotagging](https://tagspaces.discourse.group/t/82), would you consider adding them anyway? I sometimes only want a few characters of specificity (for this same reason – to refer to an area) in which case, UTM co-ordinates are actually more compact, and certainly more consistent.