Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Establish a plan to migrate existing 10.x UTRANS tools to Pro/Python #286

Open
2 tasks
gregbunce opened this issue Dec 11, 2023 · 3 comments
Open
2 tasks
Assignees
Labels
status: planning The issue is dedicated for planning only with no other work planned status: uncommitted This feature has not been committed to the plan

Comments

@gregbunce
Copy link

gregbunce commented Dec 11, 2023

Benefit

As we move forward with the next version of the roads and trails data we need to migrate the existing 10.x Desktop tools to Python and ArcGIS Pro. There needs to be some conversations on what that looks like and what needs to be migrated. I have a general plan and I'd like to get others' feedback as well as request some assistance on the actual migration (the technical stuff).

Acceptance Criteria

  • Set up 1 to 2 meetings to outline a plan forward
  • Establish a plan to migrate road update tools from 10.x to Pro in 2025-Q1 and/or 2025-Q2

Notes

Risks

No response

Issue Reference

@gregbunce gregbunce changed the title Establish a plan to migrate existing 10.x UTRANS tools to Pro/Python Planning: Establish a plan to migrate existing 10.x UTRANS tools to Pro/Python Dec 19, 2023
@steveoh steveoh added the status: planning The issue is dedicated for planning only with no other work planned label Dec 19, 2023
@gregbunce gregbunce changed the title Planning: Establish a plan to migrate existing 10.x UTRANS tools to Pro/Python Establish a plan to migrate existing 10.x UTRANS tools to Pro/Python Dec 19, 2023
@gregbunce
Copy link
Author

moving this feature to Q4 with the goal of having 1 or 2 brainstorming/planning meetings on next steps for the roads update process. Portal will be a key piece however, we're currently in testing with distributed collaboration and we still have a few issues (possible bug) to work out. regardless, it think it would be beneficial to meet once or twice in Q4 to layout the larger plan.

@nathankota nathankota added the carried forward This task was carried forward into the next quarter label Mar 25, 2024
@steveoh steveoh added status: uncommitted This feature has not been committed to the plan and removed carried forward This task was carried forward into the next quarter labels Jul 31, 2024
@eneemann eneemann assigned eneemann and unassigned gregbunce Jan 8, 2025
@MichaelAGRC
Copy link
Member

Continues into Q3

@steveoh
Copy link
Member

steveoh commented Jan 22, 2025

In the future, you also need to update the program increment. I'll move this one.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: planning The issue is dedicated for planning only with no other work planned status: uncommitted This feature has not been committed to the plan
Projects
Status: No status
Development

No branches or pull requests

5 participants