Moving Shared Mobility Operations Data to Pro - Update AGOL Feature Layer

[jaime-mckeown]

From Mary:

I am trying to get started today in moving the Shared Mobility Operations items into a project. When I do this, what is considered best practice regarding connections to geodatabases? If there is information pointing to the old geodatabase, do I need to import them into the project’s geodatabase?

If it’s better that we talk over a Teams call or that I need to do more training on workflows/best practices, I’m open to either. I’d like to be as self-sufficient as possible in this process.

[jaime-mckeown]

To Mary:

Since you are creating a new Project (create a new folder for the project), which also creates a new project FGDB, I would import all the existing feature classes into the project FGDB, so everything exists in the same project folder. It’s cleaner, and easier to work with and you will always know where your data lives.

After you get everything moved into the Project, I would move the old Mxd and FGDB to an Archive folder within the directory until you know you don’t need it anymore.

[jaime-mckeown]

• Looked over her project, everything looks great
• Re-publish the feature layer since there is a new provider added to the map
• Reconfigure the Web Map, need to add LINK.