View by status   

Ability to save .mxd and .lyr files into a geodatabase

Share this idea Report Abuse

Comments (17)

Please log in to post a comment.

Sep 25, 2012
Especially if MXD's could be subject to version control and meta-data tags.  - ie provide document management functionality. 

Nov 30, 2011
I would love to save .mxd into SDE.  It would be great to be able to version that .mxd too so I can make changes to it without losing the original.  Once I am happy with the change, I could reconcile and post the mxd version to the parent.  Right now, I have too many .mxd call things like MyProject_16.mxd.

Nov 28, 2011
I like the idea of .lyr files (or the equivalent information) within SDE.
One advantage I see, is not having to maintain drive letter mappings.  With sde, I don't need to worry about staff in differernt departments mapping to the data via a consistent drive letter mapping (which is not the case across departmnents)... but we do need to maintain at least one drive letter, to allow for storage and access of the .lyr files on disk.. It would be very nice to allow access to layer "files" via the server conection string...

Oct 6, 2011
@rmontgom I think you missed the point of this idea.  If you want everyone to see the joins without having them manually do them, why not just add the join then export to a new feature class and push it out through sde?  Of course, if you joined table changes frequently this might be a pain but certainly is possible to do.

Sep 22, 2011
We store LYR files that point to SDE Feature Classes that are joined to tables.  We want to be able to store these LYR files in the SDE GDB, so that the users don't have to maunally join the tables, and don't have to navigate to LYR files stored outside the GDB. 

We have no interest in creating Packages; we don't want to export data. We want users to use data in the SDE. So what we want, I guess, is similar to a Representation, but has more ability, namely to store joins to tables and not force the user to use any particular graphic design.

Jun 3, 2011
You can...

In 9.3 and 10 you can save MXD's straight into the File GeoDatabase by going to Save As...

Interestingly in 9.3 you can see the MXD file as an MXD file in Windows File Explorer but in version 10 it gives it a cryptic name that only means something from with the GIS system.

Jul 22, 2010
I would love to store .lyr files in SDE.  .mxds would be useful as well.

Jun 7, 2010
You can accomplish this using the "Product Library" which is part of the ArcGIS 10 Production Mapping

Product Library (mxd)

Product Library Views (.lyr files)

May 31, 2010
 Sounds like asking for a bag of hurt.  What do you do when using multiple datasources?  

Perhaps this would work if treating a 'Workspace' as a package where datasources can be located and MXD and LYR files can reside in a structured filing system with updated indexing and mapping?

A package would be nice for portability.

May 10, 2010
I agree that cartographic representation is not an easy solution for groups that just want to publish "data" and not just maps.  It requires adding extra fields and extra data and extra overhead to SDE.  I just want to store what's considred the one most popular or official way to represent a feature class in SDE, so when an average user clicks "Add Data" the system just brings it in already symbolized and labeled, scale dependency, etc.

And it should bring the layer into ArcMap with that user's SDE login credentials.

May 6, 2010
The Product Library, which is part of the PLTS solutions, allows you to store any kind of document inside the gdb.

Here is the help on it:

May 1, 2010
Idea is similar to Geomedia Library featur. I would love to see this features as it make maps and geodatabase deplayoyment way much easier.

Apr 25, 2010
very good idea: this is right to avoid sparse files (gdb in a position) and lyr files in another location

Apr 23, 2010
That would be nice.  Any file type should be allowed - as long as it's a single disk file.  FYI - The following shows what can be stored in a GDB

Apr 23, 2010
Representations are not a solution to the average user. They require an editor level license to change and update, you cant "push" them back to common symbology as required.  They have great value for formal cartographic work but it is not a solution for every day GIS symbology. 

Apr 23, 2010
Inside geodatabases you can use representations to save the symbology within the gdb. Not extremely intuitive, but very helpful once you get the hang of them.



Terms and Conditions   |    Feedback   |   FAQs
Previous MonthNext Month