Latest Contributions by MelanieWawryk

Thank you! Now the difficult task of moving the geodatabase to new projection. Layers need to be recreated in a new geodatabase since you can't change the projection on an existing layer so a huge task but happy there is a way forward. ... View more

Try sending an email to morgan.goadsby@mnr.gov.on.ca and ask how far out it is, maybe knowing it is a requirement federally will light a fire under them. ... View more

Currently you can't do it without creating a custom projection and reprojector so not advised at this point. All unofficial from a source that is in the know but unnamed * Province of Ontario is now working on a transformation from NAD83 to NAD83-CSRS V6 but have no official delivery date. * They also hope to create a NAD83 to NAD3-CSRS v8 transformation. * Probably NOT creating a transformation to V7 since V6 to V7 have an average difference of 1.5mm and V8 being released. * V8 is being released by NRCAN now and they do not expect to see much of a difference between V7 and V8 either. * Minimal difference between V6, V7 and V8 and all using the same epoch. * Moving to CSRS V6/V7/V8 will be required to move to the next generation of positioning reference (NATRF). * CAN-NET is currently using V7 but anticipated they will move to V8 in the future to support ON/Can initiatives ... View more

Thank you, that worked. I don't understand why it would remove the licensing service when it was working at the lower version. Ran "C:\Program Files\ArcGIS\Pro\Resources\ArcGIS Licensing Service\ArcGISLS.msi" and then it worked. Thanks for your help ... View more

That is great, thank you! ... View more

Thank you @MelitaKennedy  for looking in to it, the links in your post are not working, could you update them when you get a chance please? Thanks ... View more

We thought about this and know it will work with larger engineering firms and developers but for smaller contractors that aren't super computer literate, it will be too much for them. They would be creating and running an organization for one person stumping trees or a similar non-techy job. We are thinking about running a separate organization for our contractors but managing the licensing seems overly complicated. Ideally, people could purchase a mobile user license independently much like the public license and then be invited to one or more organizations. The billing for the mobile license would go to them and the contractor could work for multiple cities with their mobile license without the overhead of an organization. The organization could either add them to their organization or run a side organization just for contractors. (or Esri could build in an optional side organization for people you want to do work but you want to make sure they don't have access to any other content) ... View more

Basically, the individual user account needs a paid mobile worker option that doesn't require an organization. This is for small company workers doing things like tree-stumping, lighting repairs or rink setups. They don't have a GIS department and aren't particularly computer savvy so maintaining and managing an organization is too much for them. We want them to update what they are doing through a field maps app that we provide to them. (*** This would have been better when tracking wasn't included in mobile worker, we don't need them to create tracks just update data. We want a way for them to easily pay for a user account so they can use an app that we create by inviting them to the group. Even if we had to run the side organization with one creator and there was a way to allow them to individually purchase mobile workers, that would be fine too, we just don't want to have to collect the money for their licenses and don't want their numbers to come out of our license. ... View more

Looks like AGOL might have an issue with one of their servers. We export about 80 layers to open data daily using Python and ArcPro and one won't update and hasn't for some time. If we rename and export it, it works so not on our side or the pro document. All others export through the script and manually as expected.  Error messages are likely not related to the issue, I suspect the 400 means it is not in the index at Esri so there is possibly a bad cluster or re-indexing needed. Status: InProgress StatusMessage: Server Response: ERROR: code:400, Unable to delete item. This service item has a related Service item, Bad syntax in request. Status: InProgress StatusMessage: Publishing tool execution failed Status: Failed ErrorMessage: Failed to publish web layer We had a similar issue in 2020 where every 8th or so person could not get into a survey123 app and it turned out to be a bad cluster and once Esri re-indexed or did their magic the issue was resolved.  The item is our roads layer in open data if it helps Esri find which server has an issue because I am pretty sure this is an AGOL issue, not a local one. ... View more

ArcPro and AGOL  also do not work well with Big integer. We don't have anything that is a big integer and only use long. If you look at the layer in ArcCatelog it shows as long integer but the data design view of the same layer shows it as big integer. If we export to AGOL it gives a warning message about big integer and sure enough, it is big integer in AGOL. I guess the bug is in ArcPro 3.2.2. Please fix   ... View more