Latest Contributions by Robert_LeClair

Best workflow to remove hidden synchronization versions is to synchronize back to the data receiver replica, resolve any conflicts (if any), unregister replicas (which will delete hidden sync versions), rep/post/rec to DEFAULT, and compress.  From there, you can rebuild replica workflow.  Not required certainly but you could do this if you think there is state pinning going on. ... View more

An older workflow (SDE Command Line) for a Full Compress and replication but it documents well.  "Below are the steps for a successful compress: - Take a backup of the data. - It is important to have no locks on the data. Disconnect all the Users.* - Synchronize all the Replicas without making any edits. - If there remain any Sync Versions in the state tree after the resynch process, delete these Sync Versions using the Sdeversion -o delete option. - Reconcile/Post the data. - Compress the database twice." Good luck! ... View more

Ha - I know!  Even though ArcInfo Workstation "retired" at 10.2 I think, we still have users using it today.  I think the Arc<Fill In the Blank> products will be with us for a while. ... View more

I'd recommend contacting Esri Support Services and create a new incident for trouble shooting this issue. ... View more

Hmmm...is it the hidden synchronization versions that are pinning states then? ... View more

Gotcha.  So did you unregister using the Replica Manager on both the parent and child replica sides? ... View more

Agree John - it is a monumental shift in technology and workflows.  Kind of like Workstation to ArcView and ArcView to ArcMap.  We're at the same shift point with ArcMap to ArcGIS Pro workflows.  3 major shifts in GIS Technology over 20+ years.  And this is only for the Desktop world.  I understand that users can be frustrated by this as it changes or breaks existing workflows that have been developed over years.  The saving grace is that ArcMap, ArcCatalog, ArcScene, ArcGlobe and the extensions for those products are not going away anytime soon.  So the impetus to have to change to Pro is not there - those applications will continue to be released for years to come. ... View more

I assume you're synchronizing between the replicas before compressing the geodatabase?  Replication and Archiving will prevent a Full Compress certainly. ... View more

Certainly David.  I'm one of two Desktop Technical Leads for Esri Training Services so it's my responsibility to answer GeoNet questions in my domain of expertise - Desktop and Geodata.  ArcGIS Pro and ArcMap/ArcCatalog fit in those categories. Like you, I started using Esri products in the early 90's - ArcInfo Workstation 5.0, ArcView 1.0, ArcGIS 8.0 and Atlas*GIS.  Totally agree that when those products initially came out, they were not complete and were developed over time.  Developing new software is a time/cost intensive process and reading reports from the Pro Dev Team, I can tell you that they're working incredibly hard to fix bugs, add new functionality, incorporate ArcMap functionality and develop new functionality that is not possible in ArcMap. I suspect the Pro Pane (similar to the Catalog Window) is not complete yet either (just my opinion).  I'll be curious to see what new functionality 1.4 brings.  I did not mean to imply an opposition within the Pro Dev Team to new ideas - that's certainly not the case.  I know the Pro Dev Team/Pro Product Managers actively monitors the Ideas page for Pro and contribute responses where they can.   Yes, the Ideas page is a great way to contribute/alert the team your needs for a Desktop GIS application.  Hope this helps. ... View more

I see you contributed an ArcGIS Idea recently for a full-featured data management app for Pro - thx!  By doing this, it does get viewed by the Pro Dev Team where software decisions are made... ... View more

Correct.  As I mentioned in an earlier response, I'm an Esri Desktop/Geodata instructor and do not work with the Dev/Marketing/Corporate teams so am not privy to any of those discussions on software development/platforms.  From presentations at User Conference with members from the Pro Team, ArcGIS Pro is that fusion of 5 products.  Before ArcGIS Pro was developed there was discussions and attempts to make ArcMap/ArcCatalog a 64-bit application but after a few months, the team determined it was not possible "upgrading" the code to be compatible on 64-bit hardware.  Technically, ArcMap was first developed around 1997 and released in 1999.  During the last 19 years, the way software is coded/developed has changed significantly.  Thus ArcGIS Pro uses the current model for software development rather than using a 1997 model.  ArcGIS Pro is not 100% complete - on that we can all agree.  But the ArcGIS Pro Dev Team is working very hard for ArcMap equivalency that we hope to have at 1.4.  ArcMap 8.0 was not a complete product when it first came out but it became an amazing Desktop GIS over time.  What I see from ArcGIS Pro currently is amazing and will only improve.  Hang in there and please contribute thoughts/ideas/workflows to the Pro Dev Team to help make ArcGIS Pro another amazing Desktop GIS. ... View more

Yes, create your own Project Template for Pro. ... View more

Are you looking to do this in 2D (ArcMap) or 3D (ArcScene or ArcGIS Pro)?  If ArcMap, add the two layers to the Data Frame with the DEM the bottom layer.  You could create a Hillshade (Spatial Analyst extension) from the DEM for shaded relief.  Then add the temperature layer on top of the Hillshade and set a transparency of say 40%. ... View more

The snapping tool only works for geographic data not graphic data generated from the Draw Toolbar.  As mentioned above, you can convert graphics to features and then snap. ... View more

The workflow is that ArcGIS Pro's Project Pane will be used to manage one's geographic data.  With that said, keep in mind that ArcGIS Pro is not a complete product yet.   ArcGIS Pro 1.4 is scheduled to be released later this year and with that - the goal is ArcMap equivalency with regard to functionality.  For long time GIS users, when ArcMap 8.0 was released, it did not have the equivalency of ArcView 3.x - it took time.  It wasn't until 8.3 that I transitioned my company's workflows to ArcMap (wasn't working for Esri then). ... View more