Skip to main content


I always wanted to try out the all new ArcGIS Pro but never got a chance thanks to Esri's normal style of restricting new offerings to customers under maintenance or an active Organization subscription. (Check update at the end)
Finally today I got a chance to try it through Desktop-as-a-Service offered through NVIDIA Test Drive Virtual Machines, thanks to this blog post

Signup etc.

The signup process for the service was simple - I had to provide my name, email address, mobile number etc. A PIN was sent to my mobile number for verification. Further I had to download a desktop client (available for Windows and Mac, Linux to come soon). A Chrome app was available but did not launch for me on Ubuntu! :( Though the Chrome App invoked fine on Windows 8.1 it failed to initialize for some reason.

ArcGIS Pro Experience

NVIDIA Test Grid VM is a cloud hosted Windows 7 VM. Along with ArcGIS Pro several other leading applications are hosted there to enable test drive. Once the GRID Workspace client loaded, it took nearly a minute to show the below desktop. The subsequent responses w.r.t. application launches and further operations were good. Switching between ribbon tabs on ArcGIS Pro led to screen blurs for short time frames but that was manageable.

As explained in the Esri blog post I went on to check out the ArcGIS Pro experience - 
In this Desktop virtual machine ArcGIS Pro is setup to use the Philadelphia dataset which is provided by Pictometry. It’s ready to use. This high quality, visually appealing dataset is used by the Performance Engineering team for regular performance testing of ArcGIS Pro. It’s also used by virtualization vendors in their testing efforts to benchmark their VDI platforms.
The 3D rendering was smooth and I could move around Philadelphia using the Bookmarks option and the normal pan/zoom way.


I tried some basic geoprocessing operations like Buffer and the response was good. At the same time some toolboxes like Buffer 3D failed to load. 

I later downloaded some shapefile data and loaded them onto ArcGIS Pro to try out the labeling capabilities. Unfortunately, labeling turned out to be not very intuitive and I could not get it to work in reasonable amount of time even after checking out relevant help.

I certainly appreciate ArcGIS Pro for the advancements in terms of functionality, UI/UX that has happened since I last used ArcGIS 10 some years ago. 

Update 11-03-2015

A full 60-day trial of ArcGIS Pro is now available

Will you give ArcGIS Pro a try? Let me know your thoughts about the application.


Popular posts from this blog

Resolving INS-20802: Oracle Net Configuration Assistant failed error on Windows 10

I was all excited about the migration to Windows 10 until I had to install Oracle client on it. The Oracle client installation used to fail miserably at the last stage with this error named INS-20802.

SSL VPN: Configuring and Using Forticlient on Ubuntu, creating a Launcher

Is your primary OS at home Linux and do you use Windows only to connect to your work PC over VPN or to attend meetings? Do you often wish to connect to your work VPN from a Linux PC?  If your answer is 'Yes' to the above questions, I have an answer if your workplace uses Fortinet SSL VPN. Note that it's possible to connect to Fortinet and other VPNs like Cisco VPN from Linux through the inbuilt network manager by installing additional tools but this post would focus on using the standard Forticlient for accessing the resources on your work network.
Obtaining Forticlient The most important thing to note w.r.t. using Forticlient for Ubuntu (or any Linux distro) is to note that the client is not publicly available for download from the official website. You will have to ask your IT department to download the client for you, in case they haven't provided it.

Nginx - Solution for 10060: A connection attempt failed because the connected party did not properly respond

I was in the process of setting up Nginx to serve as the reverse proxy for Nexus Repository Manager OSS. However, the Nexus repository started loading really slowly post this and used to repeatedly display disconnected and reconnected messages. The Nginx log file used to log the below error -

<timestamp> [error] 3240#3632: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: <ip address="">, server: <fqdn>, request: "GET /nexus HTTP/1.1", upstream: "http://[::1]:8081/nexus", host: "<fqdn>"