Latest Contributions by OscarSepulveda_III

I have developed an Operations Dashboard for our department.  Yet, I like the widgets that Web AppBuilder provides.  In OPS Dashboard, personnel in the field can easily see the active incidents on the listed on the left side of the screen (Shown Below).  Then they can click on an incident within the list, and the map will zoom to that location.  This allows for personnel to rapidly see which incident they have been assigned and the address.  Can this workflow be replicated in Web App Builder????  I need to be able to see all that info which is shown for each incident. ... View more

I have developed service areas within ArcGIS Pro (v.2.4.0) based upon the following settings: with Travel Settings: Restrictions Driving an Emergency Vehicle U-Turns All Advanced Use Hierarchy Simplify Output Geometry AND I imported a point layer (Fire Station Locations) I ran the analysis and the outcome rendered properly as shown below. Then, I published a feature service to AGOL that included all 5 cutoffs.  But, when I viewed the feature layer in AGOL the layers did not render properly.   I have tried sorting the table by Cutoff Time back in Pro without success.  Also, moving the layers in the symbology editing field in AGOL without success.  And I can't perform the network analysis in AGOL because I am using the 'Driving an Emergency Vehicle' restriction. ANY IDEAS???? ... View more

I have developed service areas within ArcGIS Pro (v.2.4.0) based upon the following settings: with Travel Settings: Restrictions Driving an Emergency Vehicle U-Turns All Advanced Use Hierarchy Simplify Output Geometry AND I imported a point layer (Fire Station Locations) I ran the analysis and the outcome rendered properly as shown below. Then, I published a feature service to AGOL that included all 5 cutoffs.  But, when I viewed the feature layer in AGOL the layers did not render properly.   I have tried sorting the table by Cutoff Time back in Pro without success.  Also, moving the layers in the symbology editing field in AGOL without success.  And I can't perform the network analysis in AGOL because I am using the 'Driving an Emergency Vehicle' restriction. ANY IDEAS???? ... View more

I have a .csv file that contains data with a line break already formatted within each corresponding answer.  Yet, when I use the pulldata function, nothing appears. I want my data to show in the survey like: ZONE: 4  (Title: H4)  CH: 3 ZONE: 10  (Title: H10)  CH: 1 ZONE: 11  (Title: H11)  CH: 1 ZONE: 12  (Title: H12)  CH: 1 Instead of what I had before, which was hard to view in the field: ZONE: 4 (Title: H4) CH: 3   ZONE: 10 (Title: H10) CH: 1  ZONE: 11 (Title: H11) CH: 1  ZONE: 12 (Title: H12) CH: 1 I've tried putting the formatting within the answers with no luck: "\t"  +  "\t"+"ZONE: 4  (Title: H4)  CH: 3"+"\n"+"\t"  +  "\t"+"ZONE: 10  (Title: H10)  CH: 1"+"\n"+"\t"  +  "\t"+"ZONE: 11  (Title: H11)  CH: 1"+"\n"+"\t"  +  "\t"+"ZONE: 12  (Title: H12)  CH: 1"+"\n"+"\t"  +  "\t"+"ZONE: 13  (Title: H13)  CH: 1" A select_one will grab the corresponding 'Zone' information. And some answers may contain 12 or more lines. ... View more

Have a survey that has 20 groups with a total of 69 questions spread out over the groups.  Each question is answered by a yes-no-n/a select one.  Each question has corresponding "Text" and "Image" field types with a relevant statement: ${name} does not equal "Yes".   Is there a way to reduce the number of "Text" and "Image" fields?  Because I am having difficulty utilizing the Beta Print function due to the number of NULL fields associated with the survey. I grouped the questions because it was overwhelming in the field to look at... ... View more

I recently had a need to modify a survey schema (Field Length from 1000 to 20000 DON'T ASK! HAHA!!) that had been originally developed using Survey123 Web Designer.  Of course, all the GeoNet posts state, this could not be accomplished once the survey had been published.   I developed a 'Test' Survey utilizing the exact same attributes and schema from the original survey and submitted numerous surveys through the browser, field app, and desktop app.  All the submission data was then exported into a .csv file to back up what had been submitted.  In the #survey123.com website 'Design' tab, I duplicated each question that needed to have it's schema modified.  The Web Designer automatically labeled the copies with the original name plus '- Copy'.  Each duplicated question's label was then edited to remove '- Copy'.  Thereby making a carbon copy of the original question including schema (For now). Then the old questions were deleted by previously identifying their number within the entire survey ensuring the new questions were not accidentally deleted.  A popup (Shown Below) wanted a confirmation of the deletion and then stated any previously captured data could be deleted or not during the publishing phase.  I clicked 'Yes' and did not check the 'Don't ask me to confirm again' box, because I always like a safety measure in place to stop potential accidental changes.    Once the new questions were in place, the old ones deleted, and the survey saved, I clicked the 'Publish' link and then clicked the 'Modify schema' link.  The schema for the survey now allowed me to modify the 'Field Length' for the new questions.  I then clicked on the 'Publish' link.   A popup appeared asking me if I wanted to keep or delete the previous answers for the old questions.  If I wanted to delete all previous answers for each question than I could have marked each individual question, but I just kept the fields unmarked and clicked the 'Publish' link. I opened this modified survey through the browser, field app, and desktop app and completed numerous submissions within each of them.  I ensured this new survey could handle the larger field length by pasting text that was greater than the previous 1,000 field length, text 1 character length less than the maximum, and text greater than the new schema.  Within the desktop app, any entries greater than the defined 'field length' could not be published, whereas the browser allowed entries greater than the defined schema to be copied/pasted and submitted.  This was an interesting find that the browser did not adhere to the survey's schema. Under the 'Collaborate' tab within the Survey123 website, all previously submitted surveys had harmoniously merged with the new submissions as though the changes never happened.  I verified this by exporting the new data set and comparing it against the first .csv.   ***SIDE NOTES*** Even though a new hyperlink was developed by the republishing of the survey, I found that the old hyperlink still worked and utilized the new schema.  Since I had just published the survey last week, this proved invaluable since personnel were already utilizing it within the various apps. The data was exported before modifying the schema to ensure none of the previous submissions were lost for the actual "Live" survey when I applied this modification. ... View more