Skip to content

Switch to ArcGIS Pro-based Base Map Caching #551

Closed

Description

@stdavis

Benefit

Currently, our traditional base map caches are generated using a dedicated ArcGIS Server running on a VM in GCP. Years ago, ArcGIS Pro added the ability to generate caches on it's own but there were issues. I submitted bugs for these issues years ago and it appears that they have finally been resolved as of Pro v3.4.

Switching to Pro for generating base map caches would have several benefits. For one, it would allow us to drop the ArcGIS Server license that we have for the caching machine saving us thousands of dollars per year. It would also allow us to generate caches on a machine with many more CPUs (ArcGIS Server licensing limited us to only a few). This has the potential to allow us to cache much more quickly.

Acceptance Criteria

  • test imagery caching to make sure that we don't run into a problem when we need to cache new imagery
  • re-architect honeycomb to use Pro
  • figure out how to take advantage of the removal of the limit on CPUs (should we scale horizontally or vertically?)
  • uninstall ArcGIS Server
  • cancel License with Esri

Notes

Risks

  • There may be other road blocks with the Pro software

Issue Reference

agrc/honeycomb#22

Activity

  1. self-assigned this
    on Jan 28, 2025
  2. stdavis commented on Apr 1, 2025

    @stdavis
    MemberAuthor

    Q3 Sprint 6 Notes

    • Updated honeycomb to use Pro instead of Server to cache.
    • Worked through a variety of bugs.
    • Submitted test caches for Terrain, Overlay, and Lite to Zach for validation. He said that they looked good.
    • Modernized a bunch of other things in the honeycomb project
    • Begin production cache of Overlay
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

payingThis issue earns $$

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions