Skip to main content
Skip table of contents

Phase 1 (ArcGIS Pro)

Objectives

  • Upgrade from ArcMap Desktop to ArcGIS Pro (for one client) which would also act as a PoC

Key Activities

  1. Installing ArcGIS Pro (along with Python 3.x)

  2. Obtaining compatible license for ArcGIS Pro for PoC as well as the client

  3. Upgrading all the other supporting libraries and packages like raumel, sqlalchemy, pyodbc versions etc

  4. Upgrading all the code from Python 2.7 to Python 3.x such that it is compatible with ArcGIS Pro

  5. Upgrading the WES Spatial Plugin (to be supported with ArcGIS Pro)

  6. Data integration (and migration if needed) with ArcGIS Pro

  7. Sanity / QA

Architecture

No change. Same as the current one.

Timelines (assuming 1 dedicated resource working on this full time)

  1. Research and analysis (ongoing throughout the process): 1.5 weeks

  2. Initial setup and licensing: 1.5 weeks

    1. Understanding the licensing of ArcGIS Pro (uses a different license type than ArcMap) : 2 days

    2. Apply & get the appropriate license for an internal environment depending upon client requirements and corresponding license capabilities : 1-2 days

    3. Apply the license in ArcGIS Pro : 1 day

    4. Setup a separate internal VDI (using a base client data & code backup): 1-2 days

    5. Check database connections, file connections etc are working fine ArcGIS Pro: 1 day

    6. NOTE: we would be replicating all these steps while setting up PROD environment for the client

  3. Python code, libraries upgrade: 4 weeks

    1. Libraries upgradation, installation and compatibility: 2 days

    2. Python 2.x to 3.x for all scripts and any other ArcGIS Pro compatible changes: 2-3 weeks

    3. Dev testing the new code: 1-2 weeks

  4. Spatial Addin upgrade: 1 week to 1.5 weeks

    1. Checking if current ArcMap plugin works in ArcGIS Pro: 1 day

      1. If not, migrating to ArcGIS Pro compatible plugin: 1 week

    2. Code Changes in the Manual linking, unlinking plugin scripts as required: 2 days

    3. Dev Testing the Manual Linking / Unlinking Addin: 2 days

  5. Data Integration: 1.5 weeks

    1. PLSS and other grid data compatibility check : 1-2 days

    2. Updating all the corresponding spatial views : 1 day

    3. Changes maybe needed depending upon input/output data requirements: shapefiles / file gdb / enterprise gdb : 1 day to 4 days (if not compatible, specific changes required)

  6. Sanity / QA: 2 weeks

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.