Best Practices - reviewer.gdb

2989
1
09-09-2013 02:25 PM
StevenCox
New Contributor
Hi. I am supporting customers who work in different datums. I understand that you set the datum when the first session is created in the reviewer.gdb.  What I don't understand is the best practice regarding this. For a new DR user, do I send them a copy of the new reviewer.gdb that came with install with the result that each person has their own reviewer.gdb that they use? And if so, does that mean that they must make copies of the original reviewer.gdb  each time they need work in another datum with the result that they might have reviewer01.gdb, reviewer02.gdb, etc with each assigned a different datum?

From what I read, the datum of a reviewer.gdb must match the analyzed data's datum in order to write the geometry to the reviewer table. So it seems that they need to have multiple reviewer.gdb files to account for that.

I want to make sure I am deploying this correctly and not starting off on the wrong foot. Would appreciate any comments on general best practices with respect to administration. I watched all the videos but they didn't touch on that point.

Sincerely
Steven Cox
GIS team
Anadarko Petroleum
The Woodlands, Texas
Tags (2)
0 Kudos
1 Reply
KumarBhardwaj
Occasional Contributor II
Hi Steven,

If you are dealing with more than one datum then it is suggested to have different Reviewer workspace for each datum.

For a new DR user, do I send them a copy of the new reviewer.gdb that came with install with the result that each person has their own reviewer.gdb that they use?
- You donâ??t need to send a copy of Reviewer workspace to a new Data Reviewer user, they can create a new Reviewer workspace with the specific datum matching their data. Please refer to the following link explaining how you can create a new Reviewer workspace.

Starting a Reviewer session in a nonenterprise geodatabase
http://resources.arcgis.com/en/help/main/10.1/index.html#/in_a_nonenterprise_geodatabase/01020000005...

Starting a Reviewer session in an enterprise geodatabase
http://resources.arcgis.com/en/help/main/10.1/index.html#/in_an_enterprise_geodatabase/0102000000610...

And if so, does that mean that they must make copies of the original reviewer.gdb each time they need work in another datum with the result that they might have reviewer01.gdb, reviewer02.gdb, etc with each assigned a different datum?
- Yes, they have to use different Reviewer workspaces for different datum.
For eg. If I have two Parcel datasets with one in projection WGS 1984 and another in projection NAD 1983 then I have to create two separate Reviewer workspaces if I want to QC both of them. However, if you have the Reviewer workspace set for one datum then you can use Sessions to separate the work done by different users.

From what I read, the datum of a reviewer.gdb must match the analyzed data's datum in order to write the geometry to the reviewer table. So it seems that they need to have multiple reviewer.gdb files to account for that.
- Yes, datum of the Reviewer workspace should match with the datum of the analyzed data to write the geometries in the Reviewer table.

I want to make sure I am deploying this correctly and not starting off on the wrong foot. Would appreciate any comments on general best practices with respect to administration. I watched all the videos but they didn't touch on that point.
- If you are working with Enterprise Geodatabase then please refer to the following links to setup the Reviewer workspace appropriately:

Storing the Reviewer workspace in an enterprise Geodatabase in a version environment scenario:
http://resources.arcgis.com/en/help/main/10.1/index.html#/Storing_the_Reviewer_workspace_in_an_enter...

Best Practices for Storing the ArcGIS Data Reviewer Workspace in an Enterprise Geodatabase for Oracle:
http://downloads.esri.com/support/whitepapers/other_/J9785_GIS_Data_ReViewer_Wkspace_ArcSDE_Oracle_5...

Best Practices for Storing the ArcGIS Data Reviewer Workspace in an Enterprise Geodatabase for SQL Server:
http://downloads.esri.com/support/whitepapers/other_/J9786_ArcGIS_Data_ReViewer_Workspace_ArcSDE_SQL...
0 Kudos