survey_intro1 (type: esriFieldTypeString, alias: The NSGIC Geospatial Maturity Assessment (GMA) provides NSGIC members, sponsors, and other partners with a summary of geospatial initiatives, capabilities, and issues within and across state governments. The GMA survey produces report cards for each state on central data themes and coordination topics., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro2 (type: esriFieldTypeString, alias: This information is intended to assist state governments with setting goals, identifying peer states for collaboration, identifying areas requiring attention, and connecting with opportunities and resources. Completing the GMA also offers state governments a chance to reflect on their geospatial strategy, operations, and progress., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro3 (type: esriFieldTypeString, alias: The assessment is performed every two years. The results of this assessment will be released in the second half of 2021., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_directions (type: esriFieldTypeString, alias: Survey Completion Directions:
Please complete the assessment in its entirety. Questions with a red asterisk are required. Most questions will have you choose one answer; questions with the option to select multiple answers will prompt you to choose all that apply. The theme PDFs have all of the questions in them; the survey will show you questions based on your answers. If you have any questions regarding the survey, please direct them to Jamie Chesser, Karen Rogers, or Emily Ruetz., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
coordination_descrip (type: esriFieldTypeString, alias: The first section gets to the heart of your state's geospatial maturity by how it supports a state program. This section will be graded based on the questions in part A. Part B is informational only and is commonly used by other state representatives or others looking for your data., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gis_prog_support_descrip (type: esriFieldTypeString, alias: In this survey, the geographic information officer (GIO) or equivalent position is referred to as the GIO, regardless of actual title., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
has_gio (type: esriFieldTypeString, alias: 1. Does your state have a GIO? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_official_gio: Yes - official state-level GIO], [yes_official_gio_also_cdo: Yes - an official state-level GIO who doubles as the CDO], [yes_official_coordinator: Yes - official statewide GIS coordinator (not officially called GIO, but authorized to perform statewide coordination work on a full-time basis)], ... 3 more ...)
gio_reports_to_whom (type: esriFieldTypeString, alias: 2. To whom does the GIO directly report? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [gov_or_assistant: Governor or governor's assistant], [state_cio_or_office: State CIO or other manager in the CIO's office], [state_dept_agency_head: Other state department or agency head], ... 1 more ...)
gio_abilities (type: esriFieldTypeString, alias: 3. What abilities does the GIO have? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gio_office_funded (type: esriFieldTypeString, alias: 2. How is the GIO office funded? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gio_office_soft_money (type: esriFieldTypeString, alias: 3. Is the GIO office able to accept "soft" money such as grants, fees for service, etc.? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_na: Yes], [no_na: No], [na_na: N/A])
gio_staff (type: esriFieldTypeString, alias: 4. Does the GIO have a full-time professional staff that works on the ongoing programs of the office? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
clearinghouse (type: esriFieldTypeString, alias: 1. Does your state have a clearinghouse? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
strategic_plan (type: esriFieldTypeString, alias: 2. Does your state have a strategic plan for GIS? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_less_5: Yes, less than 5 years old], [yes_5_10: Yes, but 5-10 years old], [yes_more_10: Yes, but more than 10 years old], ... 1 more ...)
active_coord_council (type: esriFieldTypeString, alias: 3. Does your state have an active GIS coordinating council that meets at least 4 times a year? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_official: Yes, an official GIS Council defined/recognized by statute, executive order, or administrative rule], [yes_unofficial: Yes, an unofficial but active council (could include state user group)], [council_no: No])
council_representation (type: esriFieldTypeString, alias: 4. Does the council have representation from all relevant stakeholders? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
clearinghouse_url (type: esriFieldTypeString, alias: 1. Enter the complete URL for your State GIS Data Clearinghouse website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gio_office_url (type: esriFieldTypeString, alias: 2. Enter the complete URL for your State's GIO office website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gis_council_url (type: esriFieldTypeString, alias: 3. Enter the complete URL for your state's GIS Council website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gis_statues_url_desc (type: esriFieldTypeString, alias: 4. Provide a very brief description and a full URL for any GIS-related statutes in your state. These can include the establishment of the coordination office, sustained funding sources, public record laws, or other relevant laws., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_descrip (type: esriFieldTypeString, alias: Answers harvested in this section are informational only. Gathering these data helps states gauge their relative progress and provides them with valuable references for guidance along the way. Questions in this section relate specifically to GIS data for NG9-1-1., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_coord_effort (type: esriFieldTypeString, alias: 1. Is there an effort in your state to coordinate the development, normalization, aggregation, and/or distribution of GIS data in support of NG9-1-1? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [yes_county_led: Yes, but the effort is led by counties], [no: No])
ng911_coord_body (type: esriFieldTypeString, alias: 2. Is there a state GIS coordinating body assigned with the responsibility for GIS data readiness for NG9-1-1? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
ng911_coord_relationship (type: esriFieldTypeString, alias: 3. Is there a relationship between the state GIS office or coordinating body and state 9-1-1 coordinating body? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [no_relat: No relationship with state 9-1-1 coordinating body], [informal_relat: Informal – some contact with state 9-1-1 coordinating body, but GIS coordinating body isn't anvactive participant], [formal_relat: Formal – GIS coordinating body is included in state 9-1-1 coordinating body])
ng911_data_fund (type: esriFieldTypeString, alias: 4. Is the development, normalization, aggregation, and/or distribution of GIS datasets required for NG9-1-1 funded? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_fund: Yes], [some_fund: Some funding is available but not enough to cover all needs], [no_fund: No])
ng911_processes (type: esriFieldTypeString, alias: 5. Are there processes in place to normalize and aggregate authoritative GIS datasets required for NG9-1-1 to statewide datasets? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
ng911_aggregator (type: esriFieldTypeString, alias: 5a. Is the designated aggregator public or private? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [public_partner: Public], [private_partner: Private], [pub_priv_partner: Public/private partnership], ... 1 more ...)
ng911_data_sharing (type: esriFieldTypeString, alias: 5b. Do data sharing agreements exist with authoritative data providers to support statewide data aggregation? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [unnecessary: Data sharing agreements are unnecessary])
ng911_standards (type: esriFieldTypeString, alias: 6. Does your state have or follow data standards for the following GIS datasets required for NG9-1-1? (pick one for each), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_update_cycle (type: esriFieldTypeString, alias: 7. Do you have a consistent update cycle for ensuring that the statewide GIS datasets required for NG9-1-1 are as current as possible? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
data_assessments (type: esriFieldTypeString, alias: 8. Please identify the data comparisons or assessments that you apply to your data: (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
dataset_completeness (type: esriFieldTypeString, alias: 9. For the following GIS datasets required for NG9-1-1, please indicate how complete (i.e., meet the standards and accuracy requirements for NG9-1-1 call routing) each is at a statewide extent?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_data_available (type: esriFieldTypeString, alias: 10. Are the statewide GIS datasets required for NG9-1-1 publicly available? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ngcs_ecrf (type: esriFieldTypeString, alias: 11. Are 9-1-1 calls in your state being spatially routed to the PSAP over an ESInet using Next Generation Core Services (NGCS) and the Emergency Call Routing Function (ECRF)? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statewide: Yes, statewide], [yes_not_statewide: Yes, but not statewide (regionally, or only some PSAPs)], [no: No])
elec_descrip (type: esriFieldTypeString, alias: Answers harvested in this section are informational only. Please answer the following questions regarding your state's use of GIS in elections., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elec_relationship (type: esriFieldTypeString, alias: 1. Does your office have a formal relationship (statute, administrative rule, formal agreement for services, or a standing coordination meeting) with your State's Election Director? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
voting_bdry_layer (type: esriFieldTypeString, alias: 2. Does your state manage or have easy access to an accurate, current statewide voting precinct boundary layer? (pick one) (Please note, that accuracy in this question means two things. First, accuracy indicates that the layer contains all of the most recent precinct boundary polygons. Second, accuracy also means that all the layers of information needed to do any election data management are in the right projection and at the appropriate scale.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
precinct_bdry_layer (type: esriFieldTypeString, alias: If so, which statement best describes the precinct boundaries layer? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [static: The precinct boundaries are static.], [as_changes: The precinct boundaries are updated as changes are made.], [archived_as_changes: The precinct boundaries are updated, and archived, as changes are made.], ... 2 more ...)
bdry_static_why (type: esriFieldTypeString, alias: Please explain why the boundaries are static in a couple of sentences, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geocode_web_service (type: esriFieldTypeString, alias: 3. Does your state use and maintain a state or commercial geocoding web service to locate voter addresses and voters? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
geocode_web_service_descr (type: esriFieldTypeString, alias: If so, which statement best describes how the geocoding web services are used? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [static_once_found: Geographic coordinates for addresses tend to be static once found.], [periodic_update: Geographic coordinates for addresses are periodically updated to reflect the location found using the most current geocoding reference data (roads and address GIS layers)], [routine_analyze: Geographic coordinates for addresses are routinely analyzed and updated selectively as needed])
gee_audit (type: esriFieldTypeString, alias: 4. Does your state have an audit process for precinct assignments within its election database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
gee_audit_staff (type: esriFieldTypeString, alias: If so, is your staff, data, and, and other geospatial resources involved? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
gee_statutes (type: esriFieldTypeString, alias: 5. Does your state have any statutes in place that regulate the following:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
precinct_bdry_clearinghouse (type: esriFieldTypeString, alias: 6. Will the new precinct boundaries be added to your state's clearinghouse after the 2021 redistricting process? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
upload_date (type: esriFieldTypeDate, alias: If so, please estimate the date of this upload?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_descr (type: esriFieldTypeString, alias: An address point consists of the building number, street, and XY coordinates for the structure. A primary use of address points is to support 9-1-1 response, but they can also be used as reference data for address geocoding and to support thematic mapping of data associated with those points. Addresses are typically assigned by local government, so significant coordination is required to create a state-level database., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_program (type: esriFieldTypeString, alias: 1. Does your state have a program for developing or maintaining an authoritative statewide address database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
addr_db_pct_contribute (type: esriFieldTypeString, alias: 2. What percent of local address-authorities contribute to your state's address point database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 2 more ...)
addr_data_update (type: esriFieldTypeString, alias: 3. How frequently is this data updated? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [daily: Daily], [weekly: Weekly], [monthly: Monthly], ... 5 more ...)
addr_data_quality (type: esriFieldTypeString, alias: 4. What is the quality of the state-level data? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_available (type: esriFieldTypeString, alias: 5. How widely available is your address point database? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_data_support (type: esriFieldTypeString, alias: 6. Is your address point data used to support the following? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_db_characteristics (type: esriFieldTypeString, alias: 7. Identify the characteristics of your address point database. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_descr (type: esriFieldTypeString, alias: In most states, authoritative parcel map data is developed at the county level. For this section of the NSGIC perspective, we are interested in the nature of digital parcel mapping in your state, whether in a central state database or only available at the county level., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
parcel_map_pct (type: esriFieldTypeString, alias: 1. What percentage of your counties have georeferenced digital parcel maps? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 2 more ...)
cadastre_program (type: esriFieldTypeString, alias: 2. Does your state have a program of collecting current digital parcel data from local jurisdictions? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
county_participate_pct (type: esriFieldTypeString, alias: 1. What percentage of your counties participate? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 2 more ...)
parcel_db_standard (type: esriFieldTypeString, alias: 2. What standard is maintained for the central database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [standard_qaqc: Published and adheres to a standard verified via QA/QC], [standard_no_verif: Published to a standard (no verification)], [standard_effort: Published, best effort at standardization], ... 1 more ...)
parcel_access (type: esriFieldTypeString, alias: 3. How accessible is data from this central database? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
parcel_characteristics (type: esriFieldTypeString, alias: 4. What are the characteristics of your state parcel program? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
parcel_county_data_pct (type: esriFieldTypeString, alias: 1. What percentage of your counties make their data available free or at a nominal cost? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 2 more ...)
transp_descr (type: esriFieldTypeString, alias: This graded section is designed to measure your state's progress toward implementation of a statewide road centerline database complete with address ranges.
We hope you can describe your efforts to build an authoritative statewide dataset that meets the majority of business requirements. Do not describe a situation where you have multiple non-authoritative datasets in use to meet the individual needs of different Agencies., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
road_cl_db_def (type: esriFieldTypeString, alias: Definition of road centerline database: the portrayal of physical roads and trails that allow the movement of goods and people between locations. These data must include road centerline geometry and basic road attributes (e.g., road names) and will generally include address ranges, LRS control, and network topology., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
road_cl_db_complete (type: esriFieldTypeString, alias: 1. How complete is your state's road centerline database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [100_complete: 100%], [86_99: 86-99%], [51_85: 51-85%], ... 3 more ...)
road_cl_db_update (type: esriFieldTypeString, alias: 2. How frequently is this data updated? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [near_real_time: Weekly, nightly, or near real-time], [monthly: Monthly], [quarterly: Quarterly], ... 3 more ...)
road_cl_db_quality (type: esriFieldTypeString, alias: 3. What is the quality of the state-level data? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [edgematched_standard: Edgematched and published to an approved state or national standard (verified/validated)], [standard_no_edgematch: Published to an approved state or national standard but not edgematched], [nonstate_natl_standard: Published to a nonstate or national standard], ... 2 more ...)
road_cl_db_access (type: esriFieldTypeString, alias: 4. How accessible is your road centerline database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [all_access: Open, free, viewable, downloadable, with API], [open_free_download: Open, free, downloadable], [open_free_view: Open, free, viewable], ... 3 more ...)
road_cl_db_characteristics (type: esriFieldTypeString, alias: 5. Identify the characteristics of your road centerline database. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_descr (type: esriFieldTypeString, alias: This graded section is designed to evaluate if the current National Hydrography Dataset (NHD) is meeting your state's needs, and if not, measure your state's progress toward implementation of a statewide hydrography dataset above and beyond the NHD provided by the federal government. With continued acquisition of data that can support improvements to accuracy and more detailed hydrography, such as LiDAR data, higher resolution imagery, and improved digital elevation models, many states are in the process or planning for updates to hydrography data to build upon what is currently in the NHD., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_descr_2 (type: esriFieldTypeString, alias: The 2021 survey uses a baseline C grade for states that are using the NHD as-is and that it meets the functional requirements for hydrography today. To recognize work being done to improve this particular data set, there are additional questions for your State to show additional progress to achieve a higher grade., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_dataset_def (type: esriFieldTypeString, alias: Definition of hydrography dataset: an authoritative representation of hydrographic features and characteristics, including classification, location, and extent of drainage network features such as rivers, streams, canals, lakes, ponds, coastline, dams and stream gages., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_nhd (type: esriFieldTypeString, alias: 1. Is NHD meeting your state's requirements for hydrography? If yes, the grade cannot be lower than C. If no, the grade can rise or decline. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
hydro_prog_status (type: esriFieldTypeString, alias: 2. Choose the answer that best describes the status of your state's program/initiative to improve your hydro dataset (this will imply a steward) (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [active: Active], [planning_phases: In the planning phases], [no_prog: No program])
hydro_improve_complete (type: esriFieldTypeString, alias: 3. Beyond NHD; are you actively working on an improved hydro dataset, and if so, how much has your state completed? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [100_complete: 100%], [more_50: 50+%], [less_50: Less than 50%], ... 1 more ...)
hydro_maintain (type: esriFieldTypeString, alias: 4. If you are actively working on an improved hydro dataset, how frequently is it being maintained? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [annually: Annually], [2_3_yrs: Every 2-3 years], [4_5_yrs: Every 4-5 years], ... 1 more ...)
usgs_coord (type: esriFieldTypeString, alias: 5. If you are actively working on an improved hydro dataset, are you coordinating with USGS so your updates will integrate with NHD? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
hydro_db_access (type: esriFieldTypeString, alias: 6. How accessible is your state's hydrography database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [all_access: Open, free, viewable, downloadable, with API], [open_free_download: Open, free, downloadable], [open_free_view: Open, free, viewable], ... 4 more ...)
hydro_steward (type: esriFieldTypeString, alias: 7. Does your state have a Data Steward for hydrography and are they actively engaged with USGS and with stakeholders in your state to make updates to the current NHD? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [steward_no_usgs: We have a steward designated but not actively engaged with USGS or stakeholders], [no_steward: No designated steward])
hydro_best_prac (type: esriFieldTypeString, alias: 8. Identify the best practices characteristics of your hydrography database. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ortho_descr (type: esriFieldTypeString, alias: Orthoimagery includes both leaf-on and leaf-off products, both of which are important to users of geospatial data in the states. The leaf-on product serves interests such as agriculture and forestry, while leaf-off serves tax assessors and the emergency response community, among others. Statewide coverage is important and the frequency of update is critical, particularly for areas that are growing and/or changing., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_on_descr (type: esriFieldTypeString, alias: Typically based on the National Agriculture Imagery Program (NAIP) of the US Department of Agriculture., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_on_cover (type: esriFieldTypeString, alias: 1. How much of your state is covered by leaf-on orthoimagery? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 3 more ...)
leaf_on_update_freq (type: esriFieldTypeString, alias: 2. Please indicate its update frequency. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [annually: Annually], [2_3_years: Every 2-3 years], [greater_3_years: Greater than 3 years], ... 1 more ...)
leaf_on_options (type: esriFieldTypeString, alias: 3. Please indicate if you opt for any additional options. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_on_access (type: esriFieldTypeString, alias: 4. Please indicate its accessibility. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [find_download: Findable and downloadable], [access_restrict: Accessible but with restrictions], [licensed_product: Licensed product not available to outside entities], ... 1 more ...)
leaf_on_characteristics (type: esriFieldTypeString, alias: 5. Identify the characteristics of your leaf-on orthoimagery database. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_off_descr (type: esriFieldTypeString, alias: The leaf-off product should be scored differently based on its uses and the typical frequency of update for this orthoimagery layer that is more controlled by state and local resources than federal programs., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_off_cover (type: esriFieldTypeString, alias: 1. How much of your state is covered by leaf-off orthoimagery? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [50_79: 50-79%], ... 3 more ...)
leaf_off_update_freq (type: esriFieldTypeString, alias: 2. Please indicate its update frequency. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [annual: Annual], [2_3_years: Every 2-3 years], [4_5_years: Every 4-5 years], ... 3 more ...)
leaf_off_options (type: esriFieldTypeString, alias: 3. Please indicate if you opt for any additional options. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
leaf_off_access (type: esriFieldTypeString, alias: 4. Please indicate its accessibility. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [find_download: Findable and downloadable], [service_entities: Available as a service to multiple or all entities (service available in app, data repository, only viewable)], [limit_avail: Limited availability (including state and local governments)], ... 2 more ...)
leaf_off_rgb (type: esriFieldTypeString, alias: 5. Does your program collect more than the three R-G-B bands of data? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
leaf_off_characteristics (type: esriFieldTypeString, alias: 6. Identify the characteristics of your orthoimagery database. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_units_descr (type: esriFieldTypeString, alias: This graded section will assess your state's requirement for and production of governmental units and your level of cooperation with the Census to provide these data.
Definition of governmental units: boundaries that delineate geographic areas for governance, notably the local government, counties, and tribal reservations. These are the focus on the Census Bureau's annual BAS (Boundary and Annexation Survey) and BVP (Boundary Validation Program) efforts., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
unincorp_areas (type: esriFieldTypeString, alias: 1. Does your state have >75% unincorporated areas (as measured by the number of entities, not by land mass)? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
unincorp_boundary_pct (type: esriFieldTypeString, alias: 2. Of your incorporated areas, what percentage have reliable boundaries? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [100_complete: 100%], [86_99: 76-99%], [51_85: 51-75%], ... 2 more ...)
boundary_auth_source (type: esriFieldTypeString, alias: 3. Does your state have an authoritative source for boundary data? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statute: Yes, in statute], [yes_admin: Yes, administrative], [no: No])
govt_update_freq (type: esriFieldTypeString, alias: 4. Update frequency (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [update_changes: Updated as changes occur], [infreq_census_report: Infrequent because of annual reporting expectation for the Census])
govt_data_publish (type: esriFieldTypeString, alias: 5. How are the data published? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fdgc_census_standard: Data published to the FGDC/Census standard], [different_standard: Data published in a different standard], [no_standard: Data published with no standard])
govt_data_available (type: esriFieldTypeString, alias: 6. Are the data publicly available? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [download_api: Downloadable, with API], [download: Downloadable], [fee_special_request: Available for a fee or special request], ... 1 more ...)
govt_characteristics (type: esriFieldTypeString, alias: 7. Identify the characteristics of your governmental boundaries activities. (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_descr (type: esriFieldTypeString, alias: This section is about efforts your state has to augment the National Spatial Reference System (NSRS) maintained by the National Geodetic Survey (NGS). Those efforts could include a variety of activities from adding new control points, to supporting Continuously Operating Reference Station (CORS), to supporting Real-Time Networks (RTN)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_prog (type: esriFieldTypeString, alias: 1. Does your state have any program activities focused on geodetic control? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
plss (type: esriFieldTypeString, alias: 2. Is your state included in the Public Land Survey System (PLSS)? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
geodet_activities (type: esriFieldTypeString, alias: 3. What specific program activities exist? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_efforts (type: esriFieldTypeString, alias: 4. What are the details of your state efforts? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ngs_2022 (type: esriFieldTypeString, alias: 5. How is your state preparing for NGS's 2022 vertical datum and terrestrial reference frames update? (NSRS Modernization), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_descr (type: esriFieldTypeString, alias: The questions in this graded section are designed to measure your state's progress toward implementation of a statewide elevation database. We hope you can describe your efforts to build an authoritative statewide dataset that meets the majority of business requirements. Do not describe a situation where you have multiple non-authoritative datasets in use to meet the individual needs of different agencies., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_def (type: esriFieldTypeString, alias: Definition of elevation data: the measured vertical position of the earth surface and other landscape or bathymetric features relative to a reference datum typically related to sea level. These points normally describe bare earth positions, but may also describe the top surface of buildings and other objects, vegetation structure, or submerged objects. Elevation data can be stored as a three-dimensional array or as a continuous surface such as a raster, triangulated irregular network, or contours. Elevation data may also be represented in other derivative forms such as slope, aspect, ridge and drainage lines, and shaded relief., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_complete (type: esriFieldTypeString, alias: 1. Indicate the level of completion of the elevation data layer as a percentage. (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 8 more ...)
elev_update_freq (type: esriFieldTypeString, alias: 2. What is the frequency of the updates? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [8_sooner: 8 years or sooner statewide], [8_12: 8-12 years], [greater_12: 12 years or greater], ... 1 more ...)
elev_publish (type: esriFieldTypeString, alias: 3. What standards are used for publishing state-collected data? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [qa_standard: Published to a standard (verified via QA)], [standard_no_verif: Published to a standard (no verification)], [standard_effort: Published, best effort at standardization], ... 1 more ...)
elev_quality (type: esriFieldTypeString, alias: 4. What is the quality level of the elevation database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [ql2: Quality Level 2 (QL2) or better as defined by USGS], [ql3: QL3 or better as defined by USGS], [ql4: QL4 or better as defined by USGS], ... 2 more ...)
elev_better_quality (type: esriFieldTypeString, alias: 5. Do you have any data within your state that is a better Quality Level than is stated in the previous question? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
elev_db_access (type: esriFieldTypeString, alias: 6. How accessible is your elevation database? (pick one), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [all_access: Open, free, viewable, downloadable, with API], [open_free_download: Open, free, downloadable], [open_free_view: Open, free, viewable], ... 3 more ...)
elev_state_effort (type: esriFieldTypeString, alias: 7. What are the details of your state efforts? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_data_use (type: esriFieldTypeString, alias: 8. How does your state use elevation data? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_support (type: esriFieldTypeString, alias: Please describe (in numbers and scope) how the GIS community and others in your state have leveraged lidar/elevation data in support of a variety of disciplines (e.g. transportation planning, flood risk mitigation, environmental management, etc.)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro4 (type: esriFieldTypeString, alias: •The survey will show you questions based on your answers., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro5 (type: esriFieldTypeString, alias: •The survey can be done in stages. Answers are saved automatically as long as you use the same browser every time., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro6 (type: esriFieldTypeString, alias: •It is OK to have others complete parts of your survey. Give them the same link you received., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro7 (type: esriFieldTypeString, alias: •When finished, use the "Submit" button at the end, after Section 12 of 12., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro8 (type: esriFieldTypeString, alias: •Questions? Contact Jamie Chesser, Director of Programs at jamie.chesser@nsgic.org, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
transp_descr2 (type: esriFieldTypeString, alias: We hope you can describe your efforts to build an authoritative statewide dataset that meets the majority of business requirements. Do not describe a situation where you have multiple non-authoritative datasets in use to meet the individual needs of different agencies., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_units_def (type: esriFieldTypeString, alias: Definition of governmental units: boundaries that delineate geographic areas for governance, notably the local government, counties, and tribal reservations. These are the focus on the Census Bureau's annual BAS (Boundary and Annexation Survey) and BVP (Boundary Validation Program) efforts., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
Templates:
Name: New Feature
Description:
Drawing Tool: esriFeatureEditToolPoint
Prototype: