{"labelingInfo":null,"renderer":{"description":"Survey Data Locations","label":"Survey Point","symbol":{"angle":0,"color":[255,0,0,255],"outline":{"color":[255,255,0,255],"width":1},"size":8,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"},"transparency":0}
HasZ: false
HasM: false
Has Attachments: true
Has Geometry Properties: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
field_0 (type: esriFieldTypeString, alias: How many times has your organization used the Data Prep Tools to pre-process your data contribution? , SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: What are the Data Prep Tools? ], [choice1: We have never used the Data Prep Tools], [choice2: Used 1 time], ... 3 more ...)
field_1 (type: esriFieldTypeString, alias: Does the same person in your organization run the Data Prep Tools each time?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Yes, always], [choice1: Yes, mostly], [choice2: No, it changes each time], ... 1 more ...)
field_2 (type: esriFieldTypeString, alias: Do you re-use the previously downloaded Data Prep Tools or do you download a new copy of the tools before each use?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Re-use previous download], [choice1: Download tools each time before use])
field_3 (type: esriFieldTypeString, alias: How long does it typically take for you to completely run the Data Prep Tools for your contribution?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Less than a day], [choice1: 1 to 2 days], [choice2: 3 to 5 days], ... 2 more ...)
field_4 (type: esriFieldTypeString, alias: What are your general impressions of the Data Prep Tools, and is there anything we can do to make them better?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_5 (type: esriFieldTypeString, alias: The next Prep Tools version will save the tool parameters in a way that makes re-running the tools significantly easier. For instance, when you re-run the tool, the queries and other information from the previous run will pre-populate the form. This means you can re-run the tool without needing to remember the previous settings. How useful would saving these tool parameters be for your organization?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Extremely useful], [choice1: Somewhat useful], [choice2: Neutral], ... 2 more ...)
field_6 (type: esriFieldTypeString, alias: Would saving these tool parameters make you more likely to update your data contribution every 6-months to a year?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Yes, it would make my organization much more likely to provide data updates], [choice1: It would make us somewhat more likely to provide updates], [choice2: It would not impact our frequency of providing updates])
field_7 (type: esriFieldTypeString, alias: We are also considering updating the Data Prep Tools to add re-run history, such that your previous contribution’s FinalGDB will be archived on your local system. Would having this historical contribution data be useful for you?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice0: Yes, having an archive of historical contribution data would be useful], [choice1: Not sure if having our historical contribution data would be useful], [choice2: This historical contribution data would NOT be useful])
field_8 (type: esriFieldTypeString, alias: If you would like to be contacted about this survey, or help us Beta Test the next version of the Data Prep Tools, please leave your name and email here so that we can contact you., SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_10 (type: esriFieldTypeString, alias: If you have never used the Data Prep Tools, why not?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_16 (type: esriFieldTypeString, alias: What were the most helpful resources when you were learning how to use the Prep Tools?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_16_other (type: esriFieldTypeString, alias: Other (Please Specify) - What were the most helpful resources when you were learning how to use the Prep Tools?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
field_12 (type: esriFieldTypeString, alias: Some contributors provide data updates every two to three years. Ideally, we receive updates more often than that. What is the single biggest barrier for you re-submitting data every six months to a year?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [choice4: We already provide data updates every 6-months to a year], [choice0: We're too busy (or don't have the resources) to provide updates every 6-months to a year], [choice1: We dont have the resources to be able to provide data that often], ... 3 more ...)
field_12_other (type: esriFieldTypeString, alias: Other (please explain) - Some contributors provide data updates every two to three years. Ideally, we receive updates more often than that. What is the single biggest barrier for you re-submitting data every six months to a year?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
field_13 (type: esriFieldTypeString, alias: If the Data Prep Tools are too difficult or time comsuming, do you have any suggestions to make them easier or faster?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
field_11 (type: esriFieldTypeString, alias: If saving Prep Tool parameters would not impact your update frequency, why not? And what enhancement WOULD make you more likely to contribute more often?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
Templates:
Name: New Feature
Description:
Drawing Tool: esriFeatureEditToolPoint
Prototype: