Latest Contributions by LanceCole

‎01-25-2019

Like you we have not been able to isolate the issue causing the crash. One other workaround we have found sometime alleviates the crash is to create a new MXD for the project or at least test using the Excel sheet in a blank/minimal MXD. One other comment, we have found if another user is editing or has a lock on the excel file it always causes an issue. We have been making a copy of the file for GIS use and storing it in another location. As for updating the GDB table from the Excel worksheet, this can easily be scripted in Python or Model Builder and scheduled to run on demand, hourly, daily, etc. The easiest way is to manually insert the table manually the first time then write the script/model to Truncate the table and reimport the excel sheet. As long as you do not change the file/table names your joins will remain in place. We do this regularly for data we receive from third parties.

‎01-25-2019

Yes, Collector needs the correct NEMA settings you also need to set up the profile for your GPS to use it with collector. Here is link for the setup of a high accuracy GPS with Collector Classic: Use high-accuracy GPS—Collector for ArcGIS (Classic) | ArcGIS. Also here is a list of supported NEMA strings: GPS receiver support—Collector for ArcGIS (Classic) | ArcGIS. Below are screen shots on my NEMA settings and the profile settings in collector. Keep in mind these are for a Leica GPS (your screen will look different) and the VRS network I am using for the profile. Our VRS network is using GCS NAD 1983 2011 and ArcGIS Collector is using WGS_1984_Web Mercator Auxliary Sphere with the appropriate transformation applied. Sorry I cannot be more helpful as I am not familure with the Trimble units. It took me a good bit of time and a lot of testing to get our system working with the Leica unit.

‎01-24-2019

I have only used iPads with a Leica GPS but will offer some direction. No idea if android and Trimble are the same. Exit all apps on your android Power on your GPS Pair the GPS to your android device via BlueTooth Start the Trimble Status App Open Collector and go to Settings In settings select Provider There should be a “+” in the top corner, press Your Trimble unit should now be listed, select Input required info, press Done Most important, select the GPS you just added so the check mark is next to it. It does not do this when added. Press Settings to go back to Collector You may need to change the order depending upon your hardware.

‎01-24-2019

It looks like you have the image extraction down using How To: Batch export attachments from a feature class in ArcMap. You need to modify your cursor to include the other attribute data you would like to include in the image metadata You then need to write this information as metadata to each image file using an additional Python module such as piexif · PyPI or py3exiv2 · PyPI depending which version of Python you are running. There are only a limited number of valid EXIF tags so you may need to concatenate the data into a JASON string and save it to the UserComment tag. Example of using pyexif to write JASON data: Writing complex custom metadata on images through python - Stack Overflow

‎01-24-2019

With the limited info you have given it sounds like you have done the hard part of identifying the strings and creating the urls. You just need to wrap those into a HTML string for the pop-up dialog in ArcGIS Online. This can be completed in the custom attribute display. We have done this using text separated with a comma and split the string using attribute expressions in the pop-up configuration to generate the HTML dynamically. For your example, you can wrap the info in HTML: <p><a href="url_link_for_development_ activities_from_expression_or_data">Development Activities</a> are prohibited as per the <a href="url_link_for_parks_art"> Parks Art</a>.</p> will display: Development Activities are prohibited as per the Parks Art. Use the button in the Custom Attribute Display to show your dialog in HTML. A list of supported HTML is available at Supported HTML—ArcGIS Online Help | ArcGIS and a blog is also available at Using URL parameters in pop-ups with a simple singe line example.

‎01-24-2019

Display filter simply filters what is displayed on the screen dependent upon the settings configured for the feature. The feature data is still available and will show in attribute tables, can be used in calculations, selections can be made, etc. Whereas a definition query removes the data as if it does not exist. It does not show in the attribute tables nor can it be accessed for calculations or other processes without removing the definition query for that feature layer.

‎01-24-2019

We have also noted this issue and have found a few workarounds that seem to help, sometimes. 1) Use the Add Data Tool and add the XLSX file to your MXD. Once added it will appear in your Table of Contents under the List by Source tab. Try opening/joining it from there. You will also see better performance using this method. 2) From Excel, save the XLSX file as the older version XLS version or CSV (MS DOS) and try using the method noted above with these file versions. 3) Add the excel sheet data to a GDB as a table from catalog by right clicking a GDB and selecting Import>Table(single). Add this datatable to your MXD. Once added to the MXD using one of the methods above, then perform the join pointing to the reference in your MXD not the actual excel file path. It should show in the join table list drop down as the excel sheet that was added.

‎01-24-2019

This has been fixed in the beta version 3.2.264 which is scheduled to be released for production use the end of January 2019.

‎01-24-2019

We were able to confirm the latitude, longitude, and altitude values stored in the attribute tape for GNSS GPS data when using Collector are stored in the raw data format for which the GPS is configured. Do note, the altitude values are stored as height above ellipsoid and need to be converted to elevation post collection.

‎01-24-2019

Follow-up 1) we did end up creating our own base maps and side loaded them onto our collector devices. Not only did this save on credit usage for our ArcGIS online storage but the side loaded maps are substantially faster especially in areas with poor cellular connectivity. 2 & 3) collecor still does not fullly support x,y,z transformations so we have remained with the native coordinate system for collector. This is being worked on by ESRI and hopefully will be available in the near future. We also were apple to confirm the latitude, longitude and altitude attribute values stored when using a GNSS GPS are in the raw data coordinate system for the GPS utilized. Do note the altitude values are currently height above ellipseoid and need to be transform to actual elevation.

‎01-24-2019

Philip, Sorry for the delay. I tested the calculation issue in version 3.2.264 and the nested repeat calculations appear to be working correctly. Also noted the app is now checking for missing repeats such as there are suppose to be three repeats and only two were completed. This was not caught previously. Thanks for you and your teams continued assistance and support. We are planning on substantially increasing our utilization of 123 survey this year for many different applications. Lance

‎01-22-2019

We are using a high accuracy GPS (Leica GG04 plus) with an iPAD and obtaining high accuracy corrections via the State VRS network. The system has worked great and data has been within a few centimeters for X and Y data for the data collected this past summer. We recently converted the Altitude values to elevations and noted errors began to occur midday on July 5th of 2018. This was about when we believe we upgraded to version 18.0.2 of Collector and/or a new iOS version. As you look though the data Altitude values appear to repeat in the collected data despite being of sufficient elevation change to be a new value. We have tickets in with both ESRI and Leica but they have not been able to repeat this issue. We do not have the issue with the newest Collector for ArcGIS (18.1.0) just the Classic versions (18.0.2 and 18.0.3). Has anyone else seen the tendency when using a high accuracy GPS with Collector? I have attached an excel file that has a sample of our data before and after July 5th. There is a marked increase in repeated altitude values (highlighted) after 7/5/2018 17:22 staring at row 463 on our sample data. It almost appears as the altitude values are not updating when posting.

‎01-21-2019

After trying everything else we could think of, we created a new MXD for the project and everything appears to be working now. Possible corrupted MXD file somehow affecting portions of Attribute Assistant (??). We then ran a series of Manual Attribute Assistant rules to check/correct the attributes that had not been running correctly.

‎01-21-2019

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.

‎11-28-2018

Johnathan, the calculations still do not appear to be working in our forms with calculations inside repeats. Do these need to be rebuilt and republished? Please see simple sample provided above in original post. Also noted conditional statements are not correctly validating. Receiving a message, for example, field value of 9.0 is not less than or equal to 10.0. It was last time I checked. Testing on version 3.1.160. Lance

Online Status	Offline
Date Last Visited	‎08-21-2024 01:01 AM

My Ideas

Latest Contributions by LanceCole

Re: ArcMap 10.6.1 crash when opening a joined attribute table

Re: Collector with Trimble R2- record correct GNSS Receiver name to metadata?

Re: Collector with Trimble R2- record correct GNSS Receiver name to metadata?

Re: Export pop-up info with attachment from geodatabase

Re: Format a text field in a pop-up to display multiple hyperlinks based on specific text

Re: What is the difference between "Display Filters" and "Definition Queries"?

Re: ArcMap 10.6.1 crash when opening a joined attribute table

Re: repeat_count resulting in strikeout text showing in select_one dropdowns

Re: Collector GNSS Metadata source of lat/log and altitude

Re: Cordinate systems and transformations with collector and high accuracy GNSS GPS - best practice

Re: Calculations not working in repeats

Altitude Values with ArcGIS Collector (Classic)

Re: Portions of Attribute Assistant Have Stopped Working

Portions of Attribute Assistant Have Stopped Working

Re: Calculations not working in repeats

City of Wooster, Ohio - GIS Project Manager/Coordi...

Re: ArcGIS Pro Python - A row with this OID alread...

Re: ArcGIS Pro 3.2 - Drawing Alerts - Returning ST...

Re: Cordinate systems and transformations with col...

Re: Edit related table records in Survey123 and we...