Latest Contributions by MelanieWawryk

The Web Editor is an ideal tool for lightweight, task‑focused GIS editing, especially for organizations that want to empower broader teams to make simple updates without requiring full professional GIS software. Our goal is to roll out Web Editor as a streamlined alternative to ArcGIS Pro for users who only need to perform basic, controlled edits. However, because Web Editor is restricted to the Creator user type, it becomes significantly more expensive than necessary. Purchasing a Creator license effectively bundles ArcGIS Pro and other advanced capabilities that these users do not need and will not use. This creates avoidable licensing overhead and reduces our ability to scale light-editing workflows to the staff who would benefit most. Moving Web Editor to the Contributor user type would: Enable broader adoption of light editing across organizations without unnecessary licensing costs. Support modern web‑based editing workflows without requiring ArcGIS Pro deployments or advanced GIS skills. Allow GIS teams to maintain governance and data integrity while empowering non‑GIS staff to update authoritative layers. Align Web Editor with its intended purpose—a simplified, browser‑based tool for minimal edits, not a professional‑grade editing environment. Contributor‑level access would make Web Editor a practical, cost‑effective solution for organizations looking to modernize editing workflows and reduce reliance on desktop software for routine updates. ... View more

A significant issue exists with managing groups in Portal and ArcGIS Online, especially when dealing with Active Directory (AD) groups. Currently, only group owners can administer groups, which creates serious challenges for long-term management and continuity. This problem becomes particularly evident with AD-linked groups: Group owners can't add other admins since members are restricted to AD users. Ownership can only be transferred to existing AD group members, who are typically standard users without administrative privileges. When a group owner leaves the organization, administrators are forced to manually remove all apps, maps, and other content from the group just to delete it. This is followed by transferring the content to a new admin user and recreating the AD group from scratch. Allowing Admins to manage groups without being members would solve this issue, improving efficiency and reducing administrative burdens. It would ensure that content and group structures remain intact even when ownership changes, making group management more flexible and reliable. ... View more

The new version of ArcPro 3.4.0 doesn't honour stand alone licensing. Updated version through the wizard and now it is stuck on the single use error. Created a new license provisioning file, tried to apply it and said already licensed. Open ArcPro again and still wouldn't work so needed to switch to a named user. This is on a headless server machine so we like to use stand-alone licenses for them. Not really an idea but didn't want to have to go through the million support questions to report it. I'll wait for the next update and try again and will used named user while I wait.   ... View more

We urgently need the conversion from NAD_1983_UTM_Zone_17N (WKID: 26917) to NAD_1983_CSRS_UTM_Zone_17N (WKID: 22617 or 22717) v6 or v7 for Ontario. This request has been logged as ENH-000171425, and while it has been marked as a long-term roadmap item, it’s critical to emphasize that the delay is not due to a lack of business justification but rather the significant development effort involved. However, this is a pressing need. NAD83 (CSRS) UTM v7 was released in March 2019, and v6 in 2017, yet Ontario—a large and key region—was somehow overlooked in earlier roadmaps. We cannot afford further delays. Please prioritize this conversion as Ontario's operational needs are growing more urgent.   ... View more

We are increasingly being asked to create apps to track work being done by contractors doing work for the municipality. Currently, we need to create an account for them under our organization. We would prefer that they pay for a mobile user account and not be part of our organization. They don't need their own organization just an account for whoever is using the app. We don't want them to have access to our organization just the apps we give them access to and we don't want the accounts to come out of our ELA numbers, they can purchase them separately. I think if Esri created a public paid mobile account and then allowed organizations to add them to groups using the username that would solve our issue. They wouldn't be able to create anything in AGOL just access apps that have been made for them. ... View more