Latest Contributions by DETCOG_GIS

@BlakeTerhune It would definitely depend on the specifics of the dataset, area, and coordinate systems involved. In my particular case, for the intended use case, at least in the area I tested it on, it didn't appear to cause distortion that was noticeable enough. But I can definitely see that being a bigger concern depending on the skew caused by reprojecting on the fly. Thanks for pointing that out.

@MDB_GIS Oh, make no mistake, I've already stolen your code and believe I have it modified for my coordinate system for use in Attribute Rules to keep dedicated Latitude and Longitude fields populated with the WGS84 coordinates rather than the feature's local coordinates that the Shape field stores! Unfortunately, my short-cut workaround is only good if its only in AGO. So, thank you again! And ESRI team, if you're reading this, let me reiterate... I didn't mean my post in any way to suggest this work-around was cause not to add this functionality to Arcade. I concur with the others, it's definitely needed. Especially since it appears all the workarounds that have been posted on this thread grind to a halt if you're trying to use a service in both ArcPro and AGO and your AGO Org uses the default out of the box basemap group.

I greatly appreciate all the work done by @MDB_GIS, @TomNeer, and others on this thread! And, while I completely agree this would still be very useful for there to be a function in Arcade to support this... I did want to provide another partial workaround I found for anyone else who ends up coming across this thread. As has been discussed above, the various formulas do no work the same in ArcGIS Pro and ArcGIS Online. A function built into the arcade would allow a single function to work seamlessly between the two platforms hopefully. And the formulas provide by other above appear to work in ArcGIS Pro (provided you update to your coordinate system and your coordinate system works with that formula). However, if you're going to use this in the context of an ArcGIS Online map exclusively (ex: in a feature's pop-up in a web-map), then you can also just change the basemap's projection and then access the geometry directly without any further manipulation. Ex: If you have data in a local projection but want the Lat/Long coordinates, such as in WGS 84, then you can also apparently just switch your basemap to a WGS 84 basemap. ESRI even provides WGS 84 versions of their core basemaps available at https://www.arcgis.com/home/group.html?sortField=relevance&sortOrder=desc&searchTerm=+wgs84&id=db3f9a18cc88461ab1b637136ec1dadb#content,. Even though I had a web-service with data in NAD83 based UTM 15N Meters, all I did was change the basemap to one of the WGS84 ones linked to above and then used Geometry($feature).x and Geometry($feature).y in an arcade expression in the pop-up and got the Lat/Long, and not the feature's actual native UTM15N coordinates. NOTE: This will NOT work the same in ArcGIS Pro, so you'll still need the previously provided conversion formulas if you're trying to do this in ArcGIS Pro or can't change your AGO basemap. Again, just providing this in case it helps someone else stuck with this same problem... at least until ESRI hopefully makes some changes to improve the workflow.

‎05-13-2025

I have a Portal organization, a primary ArcGIS Online organization, and an ArcGIS Online HUB Premium organization, all of which I'm an administrator of. There's a Partnered Collaboration between the main AGO and the HUB organization that appears to work and share access to data back and forth successfully. We also have set up a Distributed Collaboration between our main AGO org and our Portal org that appears to work successfully. I'm running into issues when I try and share something all the way through from the HUB site to AGO and then to the Portal and back. In this particular case, I have a Survey123 with a hosted Feature layer in the HUB organization. I have shared that to a partnered collaboration group and can access that from the main AGO group. I have tested and am successfully able to see and even edit records in the hosted Feature layer from both the HUB and main AGO org. I then created a workspace in the Portal <> main AGO org's Distributed Collaboration set to COPY with 2 way sync. It successfully created a copy of the Feature layer hosted in the Portal. If I make edits to features in the HUB copy of the layer from either the HUB org or the main AGO org users, I can sync the Distributed Collaboration and those edits are copied successfully into the Portal copy. If I make any edits with any Portal users to the Portal copy though, the Distributed Collaboration fails to sync those edits through back to the HUB copy. When I inspect the Distributed Collaboration in Portal, it shows the error: I've found a few old ESRI Community posts such as https://community.esri.com/t5/arcgis-online-questions/sharing-hosted-feature-layer-from-partnered/m-p/1095759 and https://community.esri.com/t5/arcgis-enterprise-portal-questions/agol-gt-portal-distributed-syncs-break-after-an/m-p/1112605, both from 2021, that seem to have related issues and say it was a known product limitation at the time, but seems to suggest that was supposed to be fixed in future releases. Well, now that it's 2025 and I'm clearly not the only one with multiple AGO organizations that wants to share content from each of them to a Portal, I'm hoping there's either a fix for this or a known work-round I'm not finding. Any recommendations would be appreciated.

‎06-14-2024

GIS County Maintenance Coordinator Department: Regional 9-1-1 Network General Description: The GIS County Maintenance Coordinator performs advanced technical work requiring specialized knowledge of GIS maintenance, physical addressing, and telecommunications routing principles. Responsible for reviewing and resolving identified data errors in GIS and 9-1-1 system databases maintained by the Regional 9-1-1 Network. Work involves frequent and regular interaction with the general public in locating structures in the GIS database and assigning physical addresses. Establishes and maintains good working relationships with various organizations, including City, County, and other government offices, as well as the general public, telephone companies, and area US Postal Service offices. Works under general direction with moderate latitude for the use of initiative and independent judgment. Essential Duties and Responsibilities: Serves as the program’s primary liaison with the general public and telcos related to determining, correcting, and maintaining county-level addressing data in compliance with relevant laws, regulations, and policies. Coordinate by phone, email, and/or in person with USPS, telephone companies, incorporated cities, adjoining counties, elected officials, the general public, DETCOG staff, and other relevant parties to identify and resolve errors and issues in 9-1-1 System Call-Routing Databases and GIS Databases. Perform data maintenance and editing in GIS & 9-1-1 system databases with exceptional attention to detail. Maintain the integrity of GIS maps and datasets per DETCOG, CSEC, and other relevant standards and requirements during job performance. Performs other GIS and 9-1-1 system-related tasks that may be assigned. Knowledge, Abilities, and Skills Required: To perform this job successfully, an individual must be able to perform each essential job duty satisfactorily. The requirements listed below are representative of the knowledge, skill, and/or ability required. Knowledge of local, state, and federal laws relating to the program area Proficiency with Microsoft Office software, including, but not limited to MS Word and Excel Experience with ESRI software, including ArcGIS Pro is preferred. Experience in data analysis, data quality assurance, and reporting. Ability to gather, assemble, correlate, and analyze data to devise solutions to problems. Excellent oral and written communication skills Excellent interpersonal skills Educational Requirements: Graduation from an accredited two-year college with major course work involving the use of GIS software and data analysis, or Two years of professional GIS and/or data analysis experience, or An equivalent combination of education, experience, and/or training to successfully perform the essential duties of the job, such as those listed above Additional Requirements, Personal Skills, and Attributes: Must have a VALID Texas driver’s license, proper vehicle insurance, and use of a vehicle to travel Work performed indoors with some outdoor exposure. Occasional travel within the DETCOG region for data collection and outside of the region to training events may be necessary. Ability to operate computers, a telephone, and office equipment for extended periods of time Utmost professional and personal integrity Personal values consistent with the Deep East Texas Council of Governments. Salary: $38,500 to $45,000 annually depending on experience. Benefits include retirement plan, health insurance, and other benefits. Dimensions: Position is Full-Time, Non-Supervisory Application Procedure: Submit completed application and resume or a request for more information about the position to the DETCOG Human Resource Director by one of the following methods: Application can be found and submitted online at https://www.detcog.gov/jobs Email lsargent@detcog.gov Mail to DETCOG Attn: Personnel, 1405 Kurth Drive, Lufkin TX 75904 Application Deadline: Interested and qualified persons are encouraged to apply without delay. This position is open until filled. Original Job Posting can be found at https://www.detcog.gov/jobs

‎11-15-2023

Thank you! That's great to hear the functionality is being migrated into the Append GP tool in the future and it definitely makes sense then not to add and retire a new tool. That said, YES PLEASE to sharing a toolbox in the meantime so we can maintain Append with Transformation functionality until then! Thanks again for the reply!

‎11-15-2023

That's awesome about the mainstreaming of the Data Loading Workspace related tools from DLT! However, what about the Append with Transformation tool, it appears to be missing from your description and from the ArcPro 3.2 documentation? I at least personally have found that to be an extremely useful tool. There are plenty of situations that are either one-off or just a single feature class to feature class scenario and so really don't warrant the time and complexity of creating an entire Data Loading Workspace, having to open and edit everything in Excel, and then return to pro. However, those same scenarios sometimes have field mappings that aren't able to be handled by the traditional Append GP tool. It's extremely convenient to be able to use simple python expressions (or even more complex with the code block section), to do more complex field mapping. For example, if an input dataset has values North, Northwest, Northeast, East, South, Southwest, etc..., it's really handy to be able to write a basic expression that replaces those to the appropriate N, NW, NE, E, etc... when appending into a field of field length 2 for example. There's not a way to do the same with the append tool that I know of without jumping through a whole lot of hoops or changing the schema of the target dataset at least temporarily (which of course defeats the purpose or isn't always an option). So, I'm just wondering if there's any plans for maintaining the Append with Transformation tool? If not, I need to know because it'd take some time to coming up with some alternatives for our internal workflows that currently rely on it.

‎09-16-2021

Thank you for the help. I was able to finally get DLT solution working I did have some issues getting it installed correctly though, so here are some notes incase someone else ends up on this page and it helps. I ended up, in the end, having to uninstall ArcGIS Pro, delete the conda folder in AppData\Local\ESRI, install Pro, upgrade to 2.8.3, create a new cloned environment, and add dltsolutions to it (I did this via the Python Package Manager in ArcGIS Pro, NOT conda command line). I tried initially just uninstalling dltsolutions and reinstalling, I tried uninstalling panda as well, and tried new cloned environment but those each ended up not working.

‎09-16-2021

Just wondering, what version is the new one and how do you get access to it. When I go to the package manager, all it lists are 2.7.0 & 2.7.1, which both have issues (though the errors show differently, as noted in my comment above).

‎09-16-2021

I am seeing the same error messages as MichaelStranovsky posted when I open ArcPro 2.8.3 with dltsolutions v 2.7.1 installed. If it helps diagnose the issue though, when I instead have dltsolutions v 2.7.0 installed, I am able to open the project normally, and the Data Loading Tools toolbox shows up in the Geoprocessing pane. However, when I try and open any of the tools from that toolbox, I get an error message, "Tool has failed to open". Upon opening a project, the first DLT Tool I try opening has the following details for the error. If I then close that tool and open a different tool from DLT toolbox, I also get "Tool has failed to open", but it has different details. The different error messages appear in that order, regardless of which DLT tool is opened first and second. This was not an issue prior to upgrading to ArcPro 2.8.3. And I'm almost positive I was on the immediate prior version, which I assume was 2.8.2, but I know I was at least on 2.8.1 with it working (though there were issues with that upgrade and DLTSolutions as well - see Esri Case #02839421 for details on that, which ended up being a Conda issue rather than a DLTSolutions issue).

‎10-06-2020

The ExecuteDataLoad tool, when run in python at least, appears to overwrite the datetime module imported by import arcpy. This sample code hopefully describes the issue: import arcpy‍ import datetime #import datetime appears to be part of import arcpy #but for readability of code, you can include it, though it's redundant #even if we exclude "import datetime", the following line shows it imports the module print(datetime) #returns <module 'datetime' from 'C:\\...\\ESRI\\conda\\envs\\arcgispro-py3-clone\\lib\\datetime.py'> #so you can do things like the following: print(datetime.datetime.now()) #Now lets run the data loading tools arcpy.dlt.ExecuteDataLoad(r'...\dataloadingworkspace\DataReference.xlsx') #However, after running the ExecuteDataLoad tool, datetime is modified, so now: print(datetime) #returns <class 'datetime.datetime'> #which means the code print(datetime.datetime.now()) #that previously worked, suddenly now #returns AttributeError: type object 'datetime.datetime' has no attribute 'datetime'‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The problem is, first off, this is confusing as can be, and makes reading/following the code rather confusing that there's an undocumented shift in what is defined as datetime. However, second, and more worrisome, is the fact that I have to assume import arcpy includes an import of datetime for a reason. What I'm getting at is, if arcpy assumes datetime will be the datetime module and calls like datetime.datetime.now() (and others) will work in that specific syntax. Then isn't there a potential that a tool, only callable within arcpy, modifying that core assumption, could cause issues with other parts of arcpy...? Am I over-thinking this or missing something?

‎09-17-2020

Thank you for the info! In this particular case, further info identified that the new datasets I was matching with were in different projection but the same datum (NAD83) as what I am already editing. So the skew introduced by projecting to WGS84 appears to be the same between the datasets, eliminating some of the need to know this for now. But this will likely greatly help in the future as other data sources get added to this project.

‎09-16-2020

In ArcMap, I regularly use the Append geoprocessing tool to append data from a dataset in one projection (in this case UTM 15 N, meters) into another dataset in a different projection (in this case WGS84). When you append between projections, as expected, there are slight shifts in the data. I'm fine with this as the shifts have always seemed to be consistent, meaning it appears to use a consistent transformation in the process. However, I'm now in a situation, due to some additional datasets in other projections that I am having to edge match against and other projections editing is being done in, that I need to know what transformations are actually being applied by the append tool. I know in the project tool, you can specify what transformation is used, so you could move data back and forth between coordinate systems in a predictable way. However, I've not been able to figure out what transformation the append tool is using, to let me and other users work out this cross-projection edge matching issue. And to note, I'm not talking about just the on-the-fly projecting done within ArcMap/ArcPro for display purposes. I'm talking about changing coordinate systems of the actual datasets themselves. If anyone has a lead on this, I'd appreciate!

My Ideas

Latest Contributions by DETCOG_GIS

Re: Arcade projectAs Geometry Function

Re: Arcade projectAs Geometry Function

Re: Arcade projectAs Geometry Function

AGOL > AGOL > Portal Partnered and Distributed Collaboration sharing issue

GIS County Maintenance Coordinator - Deep East Texas Council of Governments (Lufkin, TX)

Re: Data Loading Tools is now included with ArcGIS Pro - 3.2 and Beyond

Re: Data Loading Tools is now included with ArcGIS Pro - 3.2 and Beyond

Re: Is Data Loading Tools compatible with Pro 2.8.3?

Re: Is Data Loading Tools compatible with Pro 2.8.3?

Re: Is Data Loading Tools compatible with Pro 2.8.3?

Why does DLT modify datetime import definition

Re: Identify Transformation Used by Append Tool

Identify Transformation Used by Append Tool

GIS Jobs