Latest Contributions by GIS-Cambria

Are you applying transformations in your ArcPro project and AGOL service? Maybe the service from AGOL is sending images with the default EPSG 3857 CRS and causing a shift between a local project and service. ... View more

Any update? This would be nice either within Pro, right click on FGDB, or a GP tool. Would be wonderful to strip metadata and anything "hidden" like GP steps/info. If I'm exporting data to a customer I don't want to include all of that detail. I know I can turn off options to track GP steps but who knows what is hidden. Upvote! ... View more

It will allow you to add a vertical CRS but I don't think it will by default enable existing features to be Z aware. Just makes the dataset have a vCRS. Maybe not the solution you are looking for. I just tested it on a non Z feature and it didn't even add a VCRS even though the tool completed with success. The Z and M are still greyed out and the tabs for CRS only show XY CRS. Depending on your GIS data storage you might be able to hack the references in a RDBMS (I did this in MS SQL by altering the behind the smoke and mirrors SDE table info and xml columns.). Maybe someone else can offer a GP solution that will not create new output. ... View more

Have you tried the Projections and Transformations Toolbox/Define Projection? I don't think this will force a new copy of your dataset. Defining a project changes the current projection information but does not reproject features. ... View more

I've also run into performance issues with ArcMap 10.5 (10.4 and 10.4.1 were a little better). I've had the problems with ArcCatalog flaking out and flickering when I click on database connections. I've seen the performance of ArcMap slow to a crawl. I've seen the mess left behind from ArcDesktop upgrades. Seriously ESRI for all of the money you get from us you can do better. Upgrades should clear old folders. Upgrades should copy anything that might be required or custom (different than default) into a folder for the upgrade version and blow out the old crap.  I'm going to try a clean install as recommended here, remove any old folders and nonsense and then install 10.5 again.  BTW I'm running MS SQL 2016 and that didn't help with ArcDesktop performance when I upgraded. ArcPro did offer a little hope that I could edit data and open layers with a better response. However; ArcPro isn't prime time and we use tools for the LGIM that aren't available yet in ArcPro. QGIS looks better by the day... ... View more

Thanks for a quick response with your attached update! ... View more

This topic seems to have a lot of traction lately. It might have been mentioned before that using XRay for ArcCatalog will let you do this. However, use caution because anything with a relationship class will delete the relationship--this includes attachments. The reason; it will create a copy of your table with the reordered fields and then delete the old and rename the new to what the old was. It works great just be mindful of relates. ... View more

For address management I think the OTB dynamic value rules have a bad expression example. For SiteAddressPoints the rule/expression for ADDRNUM  combines [PREADDRNUM] + " " + [ADDRNUM] + " " [ADDRNUMSUF]. I've found that this will update the existing ADDRNUM but append changed values making it incorrect. For example using a duplex with a 1/2 address: 123 1/2; change the prefix to R and ADDRNUM will then update to be R 123 1/2 1/2. I tried different means to compare text, or lengths but couldn't create a perfect solution. I think the ADDRNUM is really supposed to be the core part of the address number and should remain independent of the prefix and suffix. The solution I have is to do the combination in the FULLADDR expression. Trim([PREADDRNUM] + " " + [ADDRNUM] + " " + [ADDRNUMSUF] + " " + [FULLNAME] + " " + [UNITTYPE] + " " + [UNITID] + " " + [ALTUNITTYPE] + " " + [ALTUNITID]). For labeling you can use the VBS expression: Trim(replace([FULLADDR], [FULLNAME], "")) or Python: [FULLADDR].replace( [FULLNAME], '').strip() ... View more

That made me laugh! Thanks. ... View more

Getting familiar with the LGIM and addressing takes a little time and exploration. We've been working with this a bit and have some more to go, but for simplicity here's what I know so far: When creating a new address you click on a road centerline first to create the address point, then click on the location that the site address point will be. IF you don't double click then each location you click for a site address point will have the same address point number and related address point ID, then you can separately address each site address point with unit type and number. I've included a screen shot to help illustrate. To take this further, if you had building footprints and facility polygons you would also transfer information to these address sites such as if this site were called "Example Commons". ... View more

With the W3W service and API I think just being able to access W3W in an app can assist in locating an address and help with emergency services. If a caller says I'm at wrench.water.leaf then a dispatcher should be able to find that. At the least W3W will be part of our dispatching app. @Chris D and anyone else stating the vertical element: I contacted W3W and proposed they add a 4th ID to their spec. The 4th ID can be meter based and identify the height (use a - sign in front for below surface). A quad of info is just as easily parsed as a triplet, and the numeric part based on meter is easily 3D and converted to whatever local measurement. For example: wrench.water.leaf.4 is 4 meters above ground. Simple, easily parsed, and probably very quick to add/code into W3W. HOWEVER: when I spoke with someone from W3W about this they stated that so far the need for 3D was not significant?? Really W3W? ... View more

Yes. We would like to use AA to copy a feature ID from a layer to the Attachment table when an attachment is created. Glad you found a bug to squash. ... View more

Confirmed. AddIn was from one of the latest solution downloads, r/click on it and details properties say created 2/19/2016, just double checked; downloaded the UtilityNetworkEditing solution and checked the AddIn, same details. Opened Add-In-Manager and confirmed there too. Version 2.25.2016 ... View more