POST
|
Philip, Thank you for the quick response. Is there a way to reinstall the iOS 2.8.2 version which works with our surveys? Lance From: Philip Wilson <geonet@esri.com> Sent: Friday, October 12, 2018 1:06 AM To: Lance Cole <lcole@woosteroh.com> Subject: Re: - Re: Calculations not working in repeats GeoNet <https://community.esri.com/?et=watches.email.thread> Re: Calculations not working in repeats reply from Philip Wilson <https://community.esri.com/people/Philip.Wilson-esristaff?et=watches.email.thread> in Survey123 for ArcGIS - View the full discussion <https://community.esri.com/message/805729-re-calculations-not-working-in-repeats?commentID=805729&et=watches.email.thread#comment-805729>
... View more
10-12-2018
06:45 AM
|
0
|
7
|
1723
|
POST
|
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
10-11-2018
07:27 PM
|
0
|
9
|
2041
|
POST
|
The count-selected(${PIPE_AREA}) only provides the number of items selected in your select_mutiple. For your example above, it would be '3'. You need to sum all your velocities then divide by the count such as shown below but utilizing your velocity names. I also included a round statement to clean it up a little. round((${velT1} + ${velT2} + … + ${velB3}) div count-selected(${PIPE_AREA}), 2) I put together a quick example showing this with just three values. In doing so, I found a bug/issue, the default value of '0' in survey123 only will apply on load. So, if someone accidently clicks a wrong entry in the select_mutiple then unselects the value it will be set to NaN and the calculation is now broken for the average. I did find a hack to fix this using a conditional statement in the sum portion of the calculation. For nine values, the calculation of the average will be long and hopefully will be accepted by survey123. Please try the following utilizing all nine of your velocity values and the corresponding multi_select value. I abbreviated PIPE_AREA as PA to keep the sample simple. round((if(selected(${PA}), '1'), ${velT1}, 0) + … + if(selected(${PA}), '9'), ${velB3}, 0)) div count-selected(${PA}), 2) The attached sample shows both the first "broken" calculation and the second revised working equation for the average of just three values. You will note as long as you do not unselect a value once selected everything works. Please take a look at Formulas—Survey123 for ArcGIS | ArcGIS - "Empty Values" section of the Survey123 documentation which explains the NaN issue in calculations.
... View more
05-23-2018
09:01 PM
|
0
|
0
|
4933
|
POST
|
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
05-22-2018
07:47 PM
|
5
|
31
|
12926
|
POST
|
Kevin, You should be able to get the sum of all your velocity boxes, whether displayed or not, divided by the count of the multi select. This assumes the non-displayed values of the velocity boxes are zero or null. You may want to set the default for the velocity boxes to 0. The count of a multiselect is count-selected(${select_multi}) replacing "select_multi" with the name of the select_multi on your form.
... View more
05-21-2018
10:30 AM
|
1
|
0
|
4934
|
POST
|
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
05-21-2018
09:51 AM
|
2
|
1
|
1047
|
POST
|
I have a simple survey form with a repeat section. When I set the repeat_count to a previous integer value input on the form ${counter} the select_one dropdowns display strike-out text once a value is selected. If I use a fixed value for the repeat_count or leave it blank and use the Add/Delete functionality of the repeat the dropdows are fine. I also tried setting using string(${counter}) and int(${counter}) for the repeat_count with the same result. The appearance of the select_one filed are set to minimal. Any input? repeat_count set to ${counter} an integer field value, strikeout text displayed in dropdowns: repeat_count set to fixed value of 2, normal text displayed in dropdown: I attached a sample file that demonstrates the issue. I did find a few workarounds; 1) place a non-zero value in for the default on the ${counter}, 2) turn off required on the select_one and 3) use a fixed value or do not set the value for the repeat_count.
... View more
05-21-2018
08:11 AM
|
0
|
2
|
1131
|
POST
|
Try using a single selected(${PIPE_AREA}, '2') for the T2_D text box and see if that works. If so, repeat for each individually for each text box. If you need to use multiple conditions it should be selected(${PIPE_AREA}, '1') or selected(${PIPE_AREA}, '2') and selected(${PIPE_AREA}, '3') etc. The "or" can be changed to an "and" depending upon your conditions.
... View more
05-21-2018
04:19 AM
|
0
|
0
|
4934
|
POST
|
A few more questions/suggestions: Do you get the same error for linear features that references the appropriate abandon feature class, ie lines for lines? From the MXD you are using to abandon the features to the SDE connection: enter an edit session to the SDE database. select a single linear feature, a water line segment for example. from the edit menu select cut, then select paste in the paste dialog select the water abandoned lines layer as the target and click OK. You may need to zoom into the a level the abandoned features are visible, for it to display in the dialog drop down Did this paste into the abandoned FC? If not, you have a permissions issue with the DB. Try the same for a point feature and the abandon point layer When you are using the abandoned feature tool, try dragging the abandoned line layer and abandoned point layer from your TOC to the appropriate drop down on the tool and drop them. Then try and abandon a single feature. The path name in the error message you provided does not look correct for an SDE connection. I am working on a production system at the moment so I cannot experiment to get a error message for comparison.
... View more
02-28-2018
01:10 PM
|
0
|
1
|
579
|
POST
|
Alex, Does the tools work when you have just a single water main or a single fitting selected to be abandoned?
... View more
02-15-2018
08:40 AM
|
0
|
3
|
579
|
POST
|
Allyson, The most recent version is available at Esri/local-government-desktop-addins
... View more
11-08-2017
04:52 PM
|
0
|
0
|
579
|
POST
|
Paul, Thanks for the updated tools, they appear to be working. I did find one other sudo glitch. When you unabandon Water Hydrant Valves or Water System Valves they do not initially show. The “HYDRFLAG” comes back in as NULL and will not display because of the Definition Query on these two layers. I reset one layer to include “OR HYDRFLAG IS NULL” so it will at least display.
... View more
05-03-2017
02:01 PM
|
0
|
0
|
1567
|
POST
|
I received a phone call from ESRI Utilities Team regarding this question. As Howard pointed out above there is not a one size fits all answer, however, the utilities team did have some excellent input. The basis for separating the water data from the LGIM core is for future direction of utility networks. With the proposed release of utility networks in the first quarter of 2018, there will be a need to eventually separate the data as the deployment continues to evolve over the next few years. Our plan is to move our water, sewer and storm data onto a separate geodatabase and into geospatial networks. This is the first major change to our LGDM schema in almost eight years and positions us to migrate to utility networks in the future once the new networks are well established.
... View more
05-03-2017
10:46 AM
|
0
|
0
|
1300
|
POST
|
I just ran into this on the newest version (2/2017) as well, on both GBD and SDE enterprise databases. After looking into the issue further found the python scripts AbandonFeatures.py and UnAbandonAssets.py were trying to modify the GlobalID fields which are not editable. If your database is not utilizing Global id's the script works great. To correct this three lines of code need to be modified to exclude modifying the GlobalID values. In AbandonFeatures.py lines 203 and 244 by appending code to exclude GlobalID. 202 for fieldName in fieldListLines:
203 if fldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID":
204 arcpy.AddMessage("fieldName: " + fieldName)
205 newRow.setValue(fieldName, row.getValue(fieldName))
...
243 for fieldName in fieldListPoints:
244 if fldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID":
245 newRow.setValue(fieldName, row.getValue(fieldName))
And in line 205 of UnAbandonAssets.py the same. 204 for fieldName in fieldList:
205 if targetFldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID":
206 newRow.setValue(fieldName, row.getValue(fieldName))
... View more
05-03-2017
09:04 AM
|
0
|
4
|
1567
|
POST
|
George, Thanks for the quick reply. The whitepaper "The Road Ahead for Network Management" is a great overview of what is forthcoming in network management. I am looking for information that goes a little deeper. Currently we have a single SDE geodatabase that is roughly based upon a very early schema version of LGIM. We are going to migrate this data over to the newest version of the LGIM as well as create networks for water, storm and sewer systems. Should we continue to maintain this on a single SDE database, break the database into two or more databases such as - LGIM core data and a separate database(s) for networks, etc. Currently we are only utilizing the ArcGIS desktop environment with a single ArcGIS Server running an informational website but are planning on establishing an ArcGIS Portal and expanding into ArcGIS Pro using the numerous readily available resources.
... View more
05-01-2017
08:18 AM
|
0
|
1
|
1300
|
Title | Kudos | Posted |
---|---|---|
1 | a week ago | |
1 | 2 weeks ago | |
1 | 04-10-2019 07:02 PM | |
1 | 08-17-2019 05:19 AM | |
1 | 06-21-2024 04:40 AM |
Online Status |
Offline
|
Date Last Visited |
a week ago
|