Select to view content in your preferred language

Need absolute path names in Pro

20211
37
09-25-2019 12:56 PM
Status: Open
Labels (1)
FredWatson
Emerging Contributor

ArcGIS Pro should have the option to use absolute path names. In ArcMap, we can choose between absolute and relative. We should have that same choice in Pro.

A key reason to allow absolute path names is to facilitate a use mode involving many projects accessing the same data. In turn, this may be motivated by preferring to have a very large and relatively stable geospatial data system that is independent of the projects that are using it (and/or independent of the users that are using it; and/or independent of the software that is using it). It may also be motivated by needing to work on so many (100-1000) projects that even a small amount of common data between projects would lead to large amounts of wasted storage space duplicating the same data.

Not everyone works this way. But enough of us do that it should be an option. I teach Arc to college students; I use it in research; I've probably created 300 MXDs in my preferred use mode, which relies on absolute path names.

It's fine if relative paths are the default. But they should not be the *only* option.

None of the existing workaround are wholly satisfactory. Using "Save As" and moving folder references from within Pro is cumbersome and only solves half the problem. Using separate drives for data and projects is too restrictive. Scripts to convert relative to absolute paths would be cumbersome.

37 Comments
AdamGaudet

Just a heads up to everyone here that this has been noted in MyEsri's Bugs & Enhancements as Bug Number "ENH-000158640 " (https://my.esri.com/#/support/bugs/bugs?bugNumber=ENH-000158640). Its description reads "Provide the option in ArcGIS Pro to choose whether the users would save the layer path as an absolute path or not, just like ArcMap 10.x" that was submitted 2023-5-28 with a status as "Under Review" (so very bottom of the totem pole). Last updated 2023-6-29 so don't hold your breath.

I got the above from a Esri support ticket which they then pointed me to the following as workarounds that may help in my situation (though again if absolute paths were in there by design then I wouldn't need any workarounds): 

  • Update Data Sources via the Catalog tab: Update Group > Data Sources > Update Data Sources
  • Save Project As to create a new project with updated paths
  • Create and extract project packages for sharing and portability

Good luck everyone!

HbAGeoinfo

Just posting here to keep the idea in the picture, when do we get the option for absolute pathnames?!

We've been postponing our transition to Pro for as long as possible mainly because of issues like this. Organising our data and files and keeping it clean gets a lot more cumbersome because of the relative paths in Pro.

CordulaGöke

Also just posting to emphasis the importance. I often work with copies of existing projects, since creating new projects does it "the esri described way" and not the way I can work fastest. This includes setting the home folder on a higher level which destroys all paths in the project. So I made a script to go through my data sources, but it is tricky, you obviously then have to get the now home folder paths right yourself.

AdamGaudet

Re-posting as this came up for us again and was wondering if anyway headway was made. @CordulaGöke - it's a shame something like this had to be scripted on your end to account for this missing functionality. I'm considering of doing the same though some staff here have gotten used to our "work-around" and I'm afraid might be now more trouble than what it's worth.

OlivierLarouche77

I just want to let you know that i have the same issue that everybody in this threed and it's so disapointing thant a "so simple" option present in ArcMap is misssing in ArcGIS Pro... 

CONTEXT
We have multiple server in all our office (7 office) that are synchronisez by robocopy from a main source. Every body have a "relative" drive connection (J:\) pointing to the local server that are exactly the same data that is use to connect on the same data where ever you are.

Most commonly we use LYRx to connect to the source data and connect the drive J:\ inside every layer file. That way, every user can load the data on the server of their office. We absolutely need to use the toolbox to share thoses layerfile because the defaut way to share (Right clic+ share as layer file) share it by defaut with relative path... I'm about to fill a tickey to ESRI about that.

The other problem that we have, and i've closed my eyes since then about that. It happend if we copy a project from a folder to another (in case we are doing some folder cleanup or to share a good project to someone) and it change evey layer path but in our case, the data never follow the project...

The worst part is when we try to open a project that is on another server (by trying to collaborate with someone from another office). When we open the project by a UNC path, he will try to reconnect every data from that UNC path even if we have the exact data stored at the same place.

We really need that option, please...

PatIampietro

@AdamGaudet @KoryKramer is ENH-000158640 even still active? Clicking on the link https://my.esri.com/#/support/bugs/bugs?bugNumber=ENH-000158640 and searching MyEsri support https://my.esri.com/#/support/bugs/bugs for ENH-000158640 both turn up zero results for me...

 

I'd like to subscribe to the request if it is still a thing, even if there is low likelihood of a positive outcome. 

OlivierLarouche77

@KoryKramer I’ve just submitted a ticket to Esri Support regarding this topic, as well as a related issue with absolute paths (ENH-000183980: In ArcGIS Pro, provide the ability to save with absolute paths in Save As Layer File).

I hope Esri will address this situation and implement a change soon.

Thank you.