Latest Contributions by mpboyle

Melita Kennedy‌, I stumbled across this thread when searching for a way to convert state plane coordinates to lat,lon values on the fly in Sql Server.  I have found the guidance note 7.2 document you noted and am overwhelmed by the math Before I dive too deep into trying to understand it, I first wanted to check and make sure that we can/should be able to convert our data to lat,lon values using the formulas provided. Below is a screenshot of the coordinate system properties most of our data is within (Iowa State Plane NAD 1983 2011, wkid: 6463). If I had an x,y coordinate pair (below), can we use the formulas in note 7.2 to conver to lat,lon?...if yes, what formula exactly would we need to use? Any help you can provide is much appreciated! x: 5402473.342 y: 3421155.895 ... View more

Coming back to this thread nearly 2 years after original posting... finally had some time dive into Sql Server sequences, and they are surprisingly easy to understand, even for someone like me who is not a DBA, or Sql Server expert. I have been testing out using a sequence within a Sql Server trigger and have found some success.  Below are some template screenshots others may find useful. Some quick notes about our environment: ArcGIS version: 10.4.1 DBMS: Sql Server 2014 Standard Step 1: create your sequence --- some background reading on their arguments is probably useful... t-sql examples are provided in the above link can also use SSMS --- expand database | Programmability | Sequences | New Sequence Step 2: apply your sequence to a Sql trigger Notes: The trigger template was provided to us by an Esri solution engineer; I'm not a DBA ... so the t-sql written may be improved upon without my knowing  Line 14: if using a versioned dataset, your table name will need to be the associated 'add' (a) delta table Line 15: this trigger ONLY runs after an insert (create) Line 25: this trigger ONLY runs on the inserted record, not all records Step 3: test Sql trigger The highlighted fields in the screenshot below were all generated from Sql triggers Seq = next value within my sequence (sequence started at 1001) --- only on inserts Seq String = concatenation of 'WS-' and sequence value --- only on inserts Random = random 10-character string --- only on inserts Result Display = concatenation of Collection Date, Test, Result Value, and Result Unit --- on inserts and updates ... View more

This also got me thinking that perhaps it's our base map that needs to be adjusted. Since our production data is in Iowa State Plane North projection, is it best practice to keep our data in State Plane and set the data frame to a transformation when creating cached base maps?...rather than what we are currently doing which is loading our State Plane data into feature classes with Web Mercator as the projection. ... View more

Melita Kennedy‌, Thanks for the reply!  I did some testing on my end, re-publishing the service with various transformations (I didn't go through the entire list of possible transformations).  Below are my results. Based on the resulting alignments of each, is there any reason NOT to use None as a transformation? Transformations that still resulted in an offset: 1) WGS_1984_(ITRF08)_To_NAD_1983_2011 2) WGS_1984_(ITRF00)_To_NAD_1983_2011 Transformations that resulted in alignment: 1) None 2) NAD_1983_HARN_To_NAD_1983_2011 + NAD_1983_HARN_To_WGS_1984 ... View more

ichivite-esristaff‌, Thanks for the quick reply!  I guess my idea would be that Survey123 would be used to populate a related table from the feature within Collector, is that kind of the same track as a Custom URL Scheme pop-up?  Would the feature and table relationship keys auto-populate within the gdb? Thanks again! ... View more

That was easy, and makes sense ... View more