Map Package or Map File to share with GIS Team?

[DustinFerguson]

Hello Community,

I am looking for the best way to share maps on our team server so that one employee can pick up a project and start editing data if another employee is out or on another project. I have narrowed it down to saving the map in either a map package or a map file format and both seem to work fine. We do not have access to the Portal so this will all be through internal files. Does anyone have any experience on the pro and cons of each? Thank you in advance!

[clt_cabq]

Map packages can be created to include the data in the package rather than just a path name reference to the data location - this becomes important when you are sharing with people outside your organization or with others who don't have access to the same network, or if users are using a data resource on their c:\ drive. I'm not sure you can do that with a map file. So in the case of a map file, you have to make sure everyone has access to the same data locations, and that drives are mapped consistently across users (so that everyone's drive X points to the same directory). I guess I would question though if everyone is on the same network, why are the users not just using an aprx that is saved in a project folder? 

[DustinFerguson]

Hi @clt_cabq 

Thank you for your response. So, the way the way we have our GIS set up is every employee has their own APRX with a new map for every project we get assigned. First, so we can keep track of changes at each milestone for the client, and second, so that we are not filling up our company server more than we have to. Our team has access to the same servers where the data is in shapefile format (received from our client) which leads me to believe map files would be okay, BUT I would rather be safe than sorry. Would love to hear more input and suggestions!