{"labelingInfo":null,"renderer":{"description":"Survey Data Locations","label":"Consortium Member Survey 2024","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: false
Has Geometry Properties: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
summer_use (type: esriFieldTypeString, alias: How does your agency utilize the Aerial Photo Consortium's summer orthophotos?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
summer_spec (type: esriFieldTypeString, alias: The base Consortium orthophoto specification (leaf-on, 6-inch resolution, validated by third party) has been relatively consistent for the past 10 years. Which of the following statements are true for your agency?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
summer_service (type: esriFieldTypeString, alias: Select the option that best describes how your agency utilizes the orthophoto services available through Rest Service or ArcGIS Online, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [necessary: The preliminary and final Metro imagery services meet all of our needs, we don't build our own imagery service and we do not require the drive], [interim: The preliminary imagery service is a valuable interim solution. We utilize the Metro service while we are waiting to take delivery of the drive so that we can build our own imagery service.], [not_needed: We have minimal or no usage of either imagery service. We require the photo drive.])
summer_frequency (type: esriFieldTypeString, alias: What is your ideal leaf-on orthophoto capture frequency?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Once per year: Once per year], [Once every other year: Once every other year])
summer_priority (type: esriFieldTypeString, alias: Order the three variables from most important to least important., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
summer_comment (type: esriFieldTypeString, alias: If there's anything else you would like us to know about how leaf-on imagery is used at your organization, please write it here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
leafoff_participation (type: esriFieldTypeString, alias: Does your organization purchase leaf-off imagery, either through the Consortium or through another contract?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
leafoff_use (type: esriFieldTypeString, alias: How does your agency utilize LEAF-OFF orthophotos?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leafoff_spec (type: esriFieldTypeString, alias: Which of the following statements regarding the Consortium's leaf-off specification (6-inch, early spring true leaf-off conditions) are true for your agency?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leafoff_service (type: esriFieldTypeString, alias: Select the option that best describes how your agency utilizes the leaf-off orthophoto services available through Rest Service or ArcGIS Online, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [necessary: The preliminary and final Metro imagery services meet all of our needs, we don't build our own imagery service and we do not require the drive], [interim: The preliminary imagery service is a valuable interim solution. We utilize the Metro service while we are waiting to take delivery of the drive so that we can build our own imagery service.], [not_needed: We have minimal or no usage of either imagery service. We require the photo drive.])
leafoff_frequency (type: esriFieldTypeString, alias: What is your ideal leaf-off orthophoto capture frequency?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Once per year: Once per year], [Once every other year: Once every other year], [Once every five years: Once every five years])
leafoff_priority (type: esriFieldTypeString, alias: Order the three variables from most important to least important., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leafoff_comment (type: esriFieldTypeString, alias: If there's anything else you would like us to know about how leafoff imagery is used at your organization, please write it here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
aoi (type: esriFieldTypeString, alias: Which best describes the area your organization procures?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Consortium area only: Consortium area only], [Consortium area, adding non-Consortium area annually: Consortium area, adding non-Consortium area annually], [Consortium area, adding non-Consortium area every other year: Consortium area, adding non-Consortium area every other year], ... 2 more ...)
aoi_comment (type: esriFieldTypeString, alias: If you have any feedback to provide about the Consortium's Area of Interest, please write it here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
products (type: esriFieldTypeString, alias: Which other imagery products has your organization purchased in the past 5 years?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
portfolio (type: esriFieldTypeString, alias: Which of the following describes how this product(s) fits in your organization's portfolio?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
preventing_factors (type: esriFieldTypeString, alias: What are the key factors that prevent your organization from purchasing additional imagery products?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
product_add (type: esriFieldTypeString, alias: Which product(s) is your organization most interested in adding to the Consortium product list?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
oblique_priority (type: esriFieldTypeString, alias: For obliques, please order the three variables from most important to least important., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
high_res_priority (type: esriFieldTypeString, alias: For 3-inch ortho, please order the three variables from most important to least important., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
horizontal_lidar_priority (type: esriFieldTypeString, alias: For horizontal or ground-based lidar, please order the three variables from most important to least important., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
trial (type: esriFieldTypeString, alias: If we were able to offer a low or no cost trial of a supplemental subscription-based imagery product (Pictometry, NearMap, or something similar) within the next three years, would your organization be interested in trying it out?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No], [I'm not sure: I'm not sure])
new_products_open (type: esriFieldTypeString, alias: If there's anything else you would like the planning committee to consider about new or non-consortium products, please write it here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
funding (type: esriFieldTypeString, alias: Is your organization able to plan imagery purchases for a three-year cycle (2025-27)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes, we can confidently predict our imagery needs and budget for the next three years], [no: No, our needs are too unpredictable to commit three years out], [no_budget_only: No, we can only participate when we find excess budget, which is too hard to predict], ... 1 more ...)
planning (type: esriFieldTypeString, alias: In the current participation cost-sharing model, cost per section is determined by participation, number of sections purchased, and what the defined Consortium AOI is for the project. To reduce cost variability, the predictable cost model would also ask members to submit their AOI for a three-year cycle so we can better plan the Consortium AOI. Is your organization able to plan AOI needs for a three-year project cycle?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [Maybe: Maybe], [No: No])
planning_comment (type: esriFieldTypeString, alias: What would make it difficult for your organization to commit to AOI planning on a three-year cycle?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
planning_comment_other (type: esriFieldTypeString, alias: Please let us know any other questions or comments you have about the cost model, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
feedback (type: esriFieldTypeString, alias: Does your organization see any issues or want to share any feedback about this potential policy update?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
open_feedback (type: esriFieldTypeString, alias: If there are any other questions or comments you have about consortium policy, please write them here:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)