Latest Contributions by MDB_GIS

‎08-05-2020

Mark, Yes. I am using ArcGIS Pro 2.6

‎08-04-2020

I know this is many years after the initial post, but holy cow, thank you so much for this. Using this, I was able to automate renaming 500+ feature classes.

‎08-04-2020

I recently created a topo dataset for our county that is broken up into around 300 tiles. All of our data is stored on a network drive because those are backed up daily and also because we have multiple users that may need to access that data. In the process of creating that data, I used feature class to feature class GP tool several times and each time it took a substantial amount of time to complete. Furthermore, when I was finally finished creating the database, I opened a map and attempted to start adding in some of the layers to arcGIS Pro, it took what felt like an eternity for the feature datasets in the file geodatabase to open. I timed it and on average, it took ~20 seconds for the feature datasets to open and display the data. When I copied the folder to my local drive and tried the same operations, it was a night and day difference. The feature class to feature class GP tool was substantially faster and opening the feature datasets was near instant. Has anyone else experienced this issue and resolved it? Long term storage of data locally is simply not an option for me. Furthermore, this issue does not occur in ArcMap. It is specific to Pro. I would greatly appreciate any advice that you may have!

‎08-03-2020

Glad to hear it! I hope to see it soon! This is pretty much the only thing Pro is missing from my daily workflows. Once COGO polygons are in, I will probably never have to open arcMap again.

‎07-31-2020

You wouldn't happen to have a link to that thread, do you? I'd like to follow it. I looked before I posted this topic but couldn't find it. Parcel maintenance is literally the only workflow I have not moved to pro. I would really like to do so, but I am not willing to switch to the parcel fabric yet for a number of reasons. It's a shame that something as silly as this will force us to continue using ArcMap.

‎07-31-2020

If so, this is a pretty drastic design flaw in my opinion. I am the GIS Admin at my org and I have migrated to Pro. I have ten other GIS users that have yet to make that transition to ArcGIS Pro, however. I am attempting to recreate my old attribute assistant workflows from ArcMap in Pro. I was able to do so but immediately noticed that when I opened an old map from ArcMap, that the data source was broken. When I attempted to point it to the feature class, nothing happened. The little red exclamation point remained. Is this intentional or am I seriously being forced to use ArcMap until I can convince 10 people who have been using ArcMap for 10+ years to upgrade? They are extremely unlikely to upgrade, so it seems like my hands are tied unless I just force them to make the upgrade. I would prefer not to force anyone to do anything. I've been making the case for users to switch and believe they will do so when they see fit. Not to mention transitioning and training 10 new users of ArcGIS Pro would be a pretty substantial time sink for me.

‎07-30-2020

Looking to follow up on this. Is this still in the product plan?

‎07-30-2020

I have successfully migrated our data into the parcel fabric as well. I have been testing out the fabric for the last week to see if it is something I could commit to using going forward. To be truthful, my experience with the fabric so far has just been confusing and I find it takes more steps than necessary to get what I am looking for. The documentation for the parcel fabric is disorganized and incomplete (in my opinion).I have struggled to replicate my basic workflows from ArcMap. I would love to take the ESRI class on the fabric, but there is simply no money in our budget to do so. I prefer just being able to COGO in polygons just as we have been for many, many years in ArcMap. I am 100% certain that I could make the parcel fabric work for me if I had the time and resources to devote to learning it, unfortunately, I am a 1 man shop that is spread extremely thin and I do not have time to figure out the much more complex workflow on my own. I will likely revisit the parcel fabric later down the line once the product and documentation has (hopefully) matured and expanded, but until then I would really like to be able to replicate our tried and true ArcMap workflows in ArcGIS Pro. To clarify, I am not against the parcel fabric at all. In fact, I love the idea of it. The problem is that (at least to me) it has been extremely unintuitive to use and there isn't a lot of cohesive guidance on using it. All of ESRI's documentation acts under the assumption that your data is coming into the fabric with all the pre-populated information required to make it work as advertised, and that just isn't the case for us. That in addition to me struggling to figure out the correct workflows (and the lack of time to devote to figuring it out) just tells me that this isn't something in the cards for me right now.

‎07-30-2020

I am.

‎07-30-2020

I have. To my knowledge there is no way to fix misclosures when using constraints, however.

‎07-30-2020

I have transitioned every workflow over to arcGIS Pro except for parcel editing because of this. I understand that ESRI intends for users to use the parcel fabric in ArcGIS Pro. That being said, I have tried to make that transition twice now and given up both times. The documentation that is available on working within the parcel fabric is disorganized and incomplete in my opinion. I spent more time spinning my wheels trying to figure out how to correctly work in the fabric than I did actually doing the work. I like the idea of the parcel fabric, and will continue to try and transition to it over time, however it just isn't there for me yet. I would love to be able to use our old workflow to COGO polygons directly into arcGIS Pro until we can successfully make the transition. The lack of this crucial feature is the only thing keeping me from making a full switch to Pro. I realize that there is a construct polygons from lines tool as well, however that is not the same. I do not see why I should need to manage a separate feature-class for the sole purpose of being a "middleman" feature class. The ability to COGO polygons was available in ArcMap. For ArcGIS Pro to every be truly "equivalent" to ArcMap it needs to have the ability to COGO polygons.

‎07-23-2020

I have no idea that how this solution slipped by me! I ended up finding a second way to accomplish this as well using the "Extract" tool in ArcGIS Desktop. This way seems a bit more straightforward, so I will use it next time. Thank you!

‎07-16-2020

I have been given a request to export ALL GIS features that we have for a certain geographic area only. We have quite a lot of layers, so I would like to find a quicker way to do this short of exporting each layer one at a time. Does anyone know of a tool that will let you batch export selected features to a new shapefile using the same name as the input feature classes?

‎06-16-2020

I have found myself in the position of an accidental DBA at my job. I am trying to get our enterprise off the ground, and in doing so, I have come across a glaring oversight in the UI for ArcGIS Pro. I've set up three different users in the database. One for Admin, one for editors, one for viewers. Admin has full control, editors can create feature classes and edit data, and viewer can connect and view data only. Once I had these created, I decided to test them out in both ArcMap and ArcGIS Pro since we have users on both. In ArcMap, it behaved as expected. I was able to edit and save using the admin and editor logins. When I attempted to edit the data using the viewer login, I got this error message. This clearly identifies that editing is not allowed due to the permissions. When I did this same test in ArcGIS Pro, this is the error message I got. When I press F1 for help, it links to this page, which says nothing to indicate that the problem is related to database permissions. Had I been an end user and not someone explicitly testing for this, I would have had no idea what the problem was and how to report it to receive help. There really needs to be a new message that indicates precisely why the feature class is not editable.

‎06-12-2020

Yeah, that's what I figured as well. It's a shame because the LGIM Schema is such a great solution for GIS deparments just coming online. It is essentially a road map of necessary data. Fortunately I was able to get it working (see my update above), but it really should be better documented and brought into ArcGIS Pro, in my opinion.

Online Status	Offline
Date Last Visited	2m ago

My Ideas

Latest Contributions by MDB_GIS

Re: What is the deal with ArcGIS Pro and accessing data stored on a network?

Re: Renaming multiple Featureclasses

What is the deal with ArcGIS Pro and accessing data stored on a network?

Re: Add full COGO functionality to ArcGIS Pro

Re: Using Attribute Rules renders data unusable in ArcMap. Is this intentional?

Using Attribute Rules renders data unusable in ArcMap. Is this intentional?

Re: Add full COGO functionality to ArcGIS Pro

Re: Add the ability to COGO polygons in ArcGIS Pro.

Re: Add the ability to COGO polygons in ArcGIS Pro.

Re: Add the ability to COGO polygons in ArcGIS Pro.

Add the ability to COGO polygons in ArcGIS Pro.

Re: Is there a way to easily export a selection from multiple layers into multiple shapefiles?

Is there a way to easily export a selection from multiple layers into multiple shapefiles?

Improve error messages when a layer is not editable due to insufficient database permissions.

Re: So is the older (2017) iteration of ArcGIS Local Government Information Model (LGIM) effectively dead?

Re: How to maintain Natural Boundaries?

The Save As option should create a local folder an...

Re: Replacing a feature service URL in AGOL web ma...

How to get an attribute rule to calculate XY in De...

Re: What format does the Cogo reader require?