Latest Contributions by LanceCole

We are using Attribute Assistant with the local government water utilities model and everything has been working great.  We recently noted that some field s are not populating when using Attribute Assistant such as the DIAMETER or LOCDESC.  Other values such as FACILITYID, LASTUPDATE and LASTEDITOR are working fine.  No changes have been made to the schema or DynamicValue Table.  Attached is a Debug log for startup and adding a valve to a main water line.  The following are the sections for DIAMETER or LOCDESC for adding a System Valve to a 12" Water Main.  Both fields were populated with a <NULL>. ------------------------------------------------ Row Info Row Number 11 TableName: wSystemValve FieldName: LOCDESC ValueInfo: wMain|FACILITYID ValueMethod: INTERSECTING_FEATURE_DISTANCE On Create: 1 On Change: 0 Checking for Subtype Restriction Field Name: Location Description was found at index: 5 Trying: INTERSECTING_FEATURE_DISTANCE ERROR: System.__ComObject: field: FACILITYID was not found Finished: INTERSECTING_FEATURE_DISTANCE ------------------------------------------------ ------------------------------------------------ Row Info Row Number 13 TableName: wSystemValve FieldName: DIAMETER ValueInfo: wMain|DIAMETER ValueMethod: INTERSECTING_FEATURE On Create: 1 On Change: 1 Checking for Subtype Restriction Field Name: Diameter was found at index: 7 Trying: INTERSECTING_FEATURE Starting to process rule Value Info is: wMain|DIAMETER Layer Found: Main DIAMETER: at 4 map tolerance: 0.781250000000252 spatial tolerance: 0.0328083333333333 Size of search polygon: 0.00338156866484717 in Foot_US ref NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet Using Feature ClasswMain Searching on feature Class Feature matching query: 0 Cursor created Starting Loop of found features Feature count: 0 Option: First Finished: INTERSECTING_FEATURE ------------------------------------------------ We are running ArcGIS Desktop 10.6.1 and Attribute Assistant 2018.1.17 dated 1/17/2018.   ... View more

We deployed several surveys on the 2.8 version of Survey123 which have calculations in the repeats.  This worked fine until I just updated to a newer version of Survey123.  Now the calculations do not work in the repeats.  Simple sample attached.  Any ideas? ... View more

We have been testing a high accuracy GNSS GPS with Collector (Aurora and 18.0.1) in a development environment and utilizing ArcGIS online as our Portal.  As we plan to move to the production environment questions have arose pertaining to minimizing data translations to maintain accuracy.  The GPS utilizes and outputs in  the GCS NAD 1983 2011 coordinate system from our State VRS network.  We have been translating this to WGS 1984 Web Mercator Auxiliary Sphere for use with ArcGIS Online and its related basemaps.  Our production system also utilizes the GCS NAD 1983 2011 coordinate system, specifically the NAD 1983(2011) State Plane and no translations are needed between the GPS and production servers; however, we plan on continuing to utilize ArcGIS online as our Portal for collector.  What is the best or recommend approach to maintain the collected coordinate data accuracy? We are considering: 1) generating our own basemaps on our local servers using the GCS NAD 1983 2011 coordinate system and pushing these up to ArcGIS online and sideloading them directly onto our Collector systems (when/if they will fit).  This would save on credits used for building the tiles but we will still be utilizing credits for storage.  Subsequently, we would publish our features utilizing the same coordinate system. This is currently our preferred approach as there would not be any translations required. 2) continue with the current approach of collecting GPS data using GCS NAD 1983 2011, translating to WGS 1984 Web Mercator Auxiliary Sphere on ArcGIS Online and then translating back to the NAD 1983(2011) State Plane we utilize internally.  We have noted a definite shift in the data collected utilizing this method when compared to data collected by our surveyor utilizing a total station or survey grade GPS on our own local network.  I have experimented with different translations but the WGS_1984_(ITRF08) to NAD_1983_2011 we are utilizing provides the best match.   3) a question for the ESRI team is it possible to utilize the ArcGIS online basemaps without Collector automatically using the WGS 1984 Web Mercator.  We did try and publish a feature using the GCS NAD 1983 2011 coordinate system but the Maps/Collector automatically adopts the basemap coordinate system.  We were also not positive on how the point data was being handled with a mixed coordinate system and most likely introducing further translations and potential errors.   It is ironic that a few years ago GIS data that was accurate to a couple of meters we considered fantastic and now we are looking at a target accuracy of 10cm and achieving an actual accuracy of less then 2cm ... View more

We are in the process of setting up collector to be utilized with a high accuracy GNSS GPS.  Our GPS utilizes the GCS NAD 1983 2011 coordinate system and we are currently performing a transformation to WGS 1984 Web Mercator Auxiliary Sphere for use with ArcGIS Online in Collector.  When the GNSS metadata is captured in collector are the latitude, longitude and altitude values from the non-transformed GNSS coordinate system or transformed values in the WGS WEB Mercator?   We have concerns about our data undergoing multiple transformations and introducing potential errors between the GPS, Collector, ArcGIS Online and eventually on our data stores.  If the metadata values are the original GNSS data we will simple utilize that information once the data is back on our local systems for processing. ... View more