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: •Questions are a mix of single response, multiple response, and text., 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. However, please strongly consider collecting all of your answers using the PDFs/Word documents that were distributed ahead of time and filling out this Survey123 in one session., 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. Have them record their answers in the PDFs/Word documents that were distributed ahead of time, and note their name, job title, agency/organization, email address, and phone number., 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? Post in the GMA My.NSGIC community or reach out to the GMA Working Group. Questions can also be directed to info@nsgic.org., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
survey_intro9 (type: esriFieldTypeString, alias: Please see theme PDFs for complete information and descriptions of each theme, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
coordination_descrip (type: esriFieldTypeString, alias: This is a graded section. The first section gets to the heart of your state's geospatial maturity by how it supports a state program., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
has_gio (type: esriFieldTypeString, alias: 1. Does your state have a GIO (or equivalent … note this applies to all uses of the term GIO in this survey)?, 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_yn (type: esriFieldTypeString, alias: 5. Is the GIO office funded (is there funding for a GIS program outside of salary for GIO position)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
gio_office_funded (type: esriFieldTypeString, alias: 6. How is the GIO office funded? (choose all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gio_staff (type: esriFieldTypeString, alias: 7. 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: [full_time_employees: Full-time employees], [part_time_staff_interns: Part-time staff or interns], [staff_none: None])
clearinghouse (type: esriFieldTypeString, alias: 8. 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: 9. 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: 10. 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)], [yes_official_inactive: Yes, an official GIS Council defined/recognized by statute, executive order, or administrative rule that is inactive (could include state user group)], ... 1 more ...)
council_representation (type: esriFieldTypeString, alias: 11. 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: 12. Enter the complete URL for your State GIS Data Clearinghouse website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
gio_office_url (type: esriFieldTypeString, alias: 13. Enter the complete URL for your State's GIO office website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
gis_council_url (type: esriFieldTypeString, alias: 14. Enter the complete URL for your state's GIS Council website. (Include http:// or https://), SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
gis_statues_url_desc (type: esriFieldTypeString, alias: 15. Any new legislation? If so, please provide a very brief description and a full URL for any newly enacted 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: 1000, nullable: true, editable: true)
ng911_note1 (type: esriFieldTypeString, alias: The following survey questions are divided into two distinct parts to reflect the dual nature of NG9-1-1 implementation efforts:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_note2 (type: esriFieldTypeString, alias: Part 1: NG9-1-1 Program Overview. This section focuses on the statewide programmatic elements of your state's NG9-1-1 efforts. It includes questions about program presence, governance, funding, infrastructure, partnerships, and the operational status of Public Safety Answering Points (PSAPs). These questions provide essential context about how NG9-1-1 is being implemented, but they are not GIS-specific., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_note3 (type: esriFieldTypeString, alias: Part 2: NG9-1-1 GIS and Data Maturity. This section dives into the geospatial foundation required for NG9-1-1 to function. It focuses exclusively on the NG9-1-1-Ready Data your state develops or uses. These are authoritative, standardized, validated, and aggregated GIS datasets that support core NG9-1-1 services like the Emergency Call Routing Function (ECRF) and Location Validation Function (LVF)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_note4 (type: esriFieldTypeString, alias: Together, these two parts will provide a comprehensive picture of your state's NG9-1-1 maturity — both organizationally and technically. Please answer each section to the best of your knowledge. You may wish to consult your State 9-1-1 Office, State Geospatial Information Office (GIO), or equivalent, and local or regional partners as needed., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_state_effort (type: esriFieldTypeString, alias: 1. Is your state engaged in a statewide effort to support the transition to a Next Generation 9-1-1 (NG9-1-1) environment?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_active: Yes – a NG9-1-1 program is active and operational], [yes_dev: Yes – a NG9-1-1 program is in development, procurement, or pilot phase], [yes_plan: Yes – a NG9-1-1 program is in an early planning phase (e.g., exploratory meetings, volunteer-led, no formal funding)], ... 1 more ...)
ng911_current_progress (type: esriFieldTypeString, alias: 2. What phase best describes your state's current progress toward implementing NG9-1-1?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [statewide: Statewide Implementation – All PSAPs are using NG9-1-1, consistent with FCC Phase 2 guidelines], [partial: Partial Implementation – Some PSAPs are actively using NG9-1-1 services], [infra_deploy: Infrastructure Deployment – Implementation is underway, but no PSAPs are yet live with NG9-1-1 call-routing], ... 4 more ...)
ng911_responsible (type: esriFieldTypeString, alias: 3. Is there a designated agency or entity responsible for managing the NG9-1-1 program in your state (e.g., a State 9-1-1 Office or 9-1-1 Authority)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_specific_agency: Yes – a specific agency or entity is officially responsible], [no_informal: No – the NG9-1-1 program is managed informally or collaboratively], [no_clear: No – there is no clear responsibility], ... 1 more ...)
ng911_prog_gio_coord (type: esriFieldTypeString, alias: 4. Is there coordination between the NG9-1-1 program and the State Geospatial Information Office (GIO), or equivalent? (This identifies whether collaboration exists between the 9-1-1 and geospatial programs.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes – formal collaboration (e.g., shared governance, MOUs, working groups, reporting structure)], [yes_informal: Yes – informal collaboration (e.g., ad hoc meetings, project-based coordination)], [no_aware: No coordination, but the GIO and the NG9-1-1 programs are aware of each other], ... 1 more ...)
ng911_gov_relat (type: esriFieldTypeString, alias: 5. Is there a governance relationship between the State Geospatial Information Office (GIO), or equivalent, and the State 9-1-1 Office? (This refers to cross-representation in decision-making bodies.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [formal: Formal – Either the GIO is a member of the 9-1-1 governing body, or the 9-1-1 Office is a member of the State Geospatial Coordinating Body, or another formal relationship], [informal: Informal – There is contact or collaboration, but no formal structure], [no_relationship: No relationship – The GIO and 9-1-1 Office do not coordinate on NG9-1-1 matters])
ng911_prog_engage (type: esriFieldTypeString, alias: 6. In what ways does your NG9-1-1 program engage with the State Geospatial Information Office (GIO), or equivalent? (Select all that apply — skip if no coordination), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_psap_pct (type: esriFieldTypeString, alias: 7. If your state is currently implementing NG9-1-1, what percentage of the PSAPs have migrated to NG9-1-1 services (PSAPs are connected to an ESInet and using NGCS)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_more: 90% or more], [70_89: 70–89%], [50_69: 50–69%], ... 3 more ...)
ng911_legislation (type: esriFieldTypeString, alias: 8. Is there any legislation in your state specific to 9-1-1?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_specify: Yes (Specify)], [no_specify: No])
ng911_gov_mech (type: esriFieldTypeString, alias: 9. Is the NG9-1-1 program supported by any formal governance mechanism?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statute_eo: Yes – statute or executive order], [yes_agency_policy: Yes – agency policy or administrative rule], [yes_informal: Yes – informal coordination or voluntary agreements], ... 2 more ...)
ng911_strategy (type: esriFieldTypeString, alias: 10. Does the NG9-1-1 program have a documented long-term strategy or implementation plan (e.g., a formal business plan)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal_complete: Yes – a formal plan was used and is complete], [yes_formal_active: Yes – a formal, written plan is in place and actively used], [yes_exists: Yes – a plan exists, but it is outdated or not actively used], ... 3 more ...)
ng911_dedicated_fund (type: esriFieldTypeString, alias: 11. Is there dedicated funding for your state's implementation of NG9-1-1?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_sufficient: Yes – ongoing and fully sufficient to support the implementation], [yes_partial: Yes – ongoing, but not fully sufficient (partial funding)], [yes_once: Yes – one-time or grant-based funding only], ... 1 more ...)
ng911_geo_fund (type: esriFieldTypeString, alias: 12. Is there dedicated state-level funding specifically for the geospatial components of your NG9-1-1 implementation?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_sufficient: Yes – ongoing and fully sufficient to support GIS activities], [yes_partial: Yes – ongoing, but not fully sufficient (partial GIS funding)], [yes_once: Yes – one-time or grant-based GIS funding only], ... 3 more ...)
ng911_fund_source (type: esriFieldTypeString, alias: 13. What funding sources have been used for NG9-1-1 GIS data development?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_fund_gio (type: esriFieldTypeString, alias: 14. Does the NG9-1-1 program provide funding or resources to the State Geospatial Information Office (GIO), or equivalent, for any of the following activities?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_spatial_route (type: esriFieldTypeString, alias: 15. Are 9-1-1 calls currently being spatially routed in your state using NG9-1-1 technology? (This refers to routing over an ESInet using Next Generation Core Services (NGCS) and the Emergency Call Routing Function (ECRF)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_fully: Yes – spatial call routing is fully implemented statewide], [yes_parts: Yes – spatial routing is in use in parts of the state], [no_ready: No – spatial routing is not in use yet, but the GIS data is ready], ... 1 more ...)
ng911_spatial_route_pct (type: esriFieldTypeString, alias: 15.1 Approximately what percentage of PSAPs currently receive spatially routed calls?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [less_25: Less than 25%], [26_50: 26% to 50%], [51_75: 51% to 75%], ... 1 more ...)
ng911_national_coord (type: esriFieldTypeString, alias: 16. Does the NG9-1-1 program coordinate with any national-level initiatives or organizations? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_note5 (type: esriFieldTypeString, alias: The second half of this survey focuses entirely on the geospatial data infrastructure that supports NG9-1-1. High-quality, standardized GIS data is essential to the success of NG9-1-1—particularly the Emergency Call Routing Function (ECRF) and Location Validation Function (LVF)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_note6 (type: esriFieldTypeString, alias: This section focuses on how your state coordinates the development and maintenance of GIS data that supports Next Generation 9-1-1 (NG9-1-1). We refer to this as NG9-1-1-Ready Data — authoritative, standardized, and aggregated datasets like road centerlines, address points, PSAP boundaries, and emergency service boundaries. Coordination can occur at many levels, including the state, regional, local, and even across state lines. Coordination may involve the State Geospatial Information Office (GIO), or equivalent, as well as the State 9-1-1 Office., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_effort_ready (type: esriFieldTypeString, alias: 17. Is there an effort in your state to coordinate or produce and maintain NG9-1-1-Ready Data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statewide: Yes – a statewide, state-led effort is underway], [yes_state_led: Yes – a state-led effort exists, but not all areas are participating], [yes_non_state: Yes – but the effort is led by a non-state-level entity (e.g., regional, county, or tribal group)], ... 1 more ...)
ng911_primary_coord (type: esriFieldTypeString, alias: 18. Who is the primary coordinating body responsible for NG9-1-1 GIS data readiness in your state?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [gio: State Geospatial Information Office (GIO), or equivalent — leads coordination and readiness efforts], [joint_coord: Joint coordination — responsibilities are shared between the State Geospatial Information Office (GIO), or equivalent, and the State 9-1-1 Office], [911_lead_leverage: State 9-1-1 Office leads the effort and leverages the state GIS office], ... 4 more ...)
ng911_primary_collab (type: esriFieldTypeString, alias: 19. Does the primary coordinating body responsible for NG9-1-1 GIS data readiness in your state collaborate with local governments (e.g., local 9-1-1 offices or GIS departments) to support GIS data development and integration?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [unsure: Unsure])
ng911_neighbor_coord (type: esriFieldTypeString, alias: 20. Does your state coordinate with neighboring states for NG9-1-1 GIS data? (Examples include aligning PSAP or service boundaries, resolving overlaps, or participating in multi-state working groups.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_specify: Yes (Specify)], [no_specify: No])
ng911_state_mech (type: esriFieldTypeString, alias: 21. Is the state 9-1-1 effort supported by any formal governance mechanism specifically guiding the integration of GIS into 9-1-1 services?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statute_eo: Yes – statute or executive order], [yes_agency_policy: Yes – agency policy or administrative rule], [yes_informal: Yes – informal coordination or voluntary agreements], ... 3 more ...)
ng911_data_rely (type: esriFieldTypeString, alias: 22. Which of the following GIS datasets does your 9-1-1 program rely on? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_dedicated_staff (type: esriFieldTypeString, alias: 23. Does your state's NG9-1-1 program have dedicated GIS staff (either directly or through partnerships)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_by_gio: Yes – full-time GIS staff provided by the State Geospatial Information Office (GIO), or equivalent], [yes_joint_support: Yes – GIS staff jointly supported by both the NG9-1-1 program and the State Geospatial Information Office (GIO), or equivalent], [yes_by_ng911: Yes – full-time GIS staff hired directly by the NG9-1-1 program or provided via a consultant], ... 3 more ...)
ng911_document_process (type: esriFieldTypeString, alias: 24. Does your state have a documented process in place to combine local GIS data into a statewide dataset for NG9-1-1 (i.e., normalization, validation, aggregation)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_fully: Yes – fully implemented and followed statewide], [yes_implemented: Yes – implemented, but only followed in parts of the state], [in_dev: In development – a statewide process is being designed or piloted], ... 2 more ...)
ng911_aggregate_gis (type: esriFieldTypeString, alias: 25. Who is primarily responsible for aggregating GIS data into a statewide NG9-1-1 dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [state_led: State-led – the State Geospatial Information Office (GIO), or equivalent, or the State 9-1-1 Office leads aggregation internally], [public_private: Public-private partnership – aggregation is shared between the state and a contractor/vendor], [vendor_led: Vendor-led – external contractor performs aggregation on behalf of the state], ... 2 more ...)
ng911_share_formal (type: esriFieldTypeString, alias: 26. Are there formal data-sharing agreements with local governments or authoritative data providers to support NG9-1-1 aggregation?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal_agree: Yes – formal agreements exist and are implemented statewide], [yes_agree_exist: Yes – agreements exist, but not all jurisdictions participate], [in_progress: In progress – agreements are being developed or negotiated], ... 2 more ...)
ng911_follow_standards (type: esriFieldTypeString, alias: 27. Does your state follow data standards for the GIS layers required for NG9-1-1? For each of the following GIS datasets, indicate which level of standardization best describes your current approach. (Pick one per layer), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_defs_none (type: esriFieldTypeString, alias: None – This dataset does not follow any standard or does not exist, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_defs_not_nena (type: esriFieldTypeString, alias: Not NENA Compliant – Dataset exists but does not follow NENA standards, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_update_cycle (type: esriFieldTypeString, alias: 28. Does your state follow a regular update cycle for maintaining the statewide GIS datasets required for NG9-1-1? (Select one per layer), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_data_discrep (type: esriFieldTypeString, alias: 29. Does your state have a formal process (with a documented workflow) to address data discrepancies in NG9-1-1 GIS datasets? A "formal process" refers to a defined and repeatable method for identifying and resolving discrepancies such as mismatched boundaries, incorrect attributes, or inconsistent formats., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – formal, documented, and available statewide], [partial: Partial – some processes exist, but not documented or not used consistently], [no: No – no defined process is in place])
ng911_qa_checks (type: esriFieldTypeString, alias: 30. What types of quality assurance checks or data comparisons are regularly applied to NG9-1-1 GIS datasets? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_data_complete (type: esriFieldTypeString, alias: 31. How complete are your statewide NG9-1-1 GIS datasets? (Pick one per layer — not graded), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
ng911_gis_public (type: esriFieldTypeString, alias: 32. Which of the following NG9-1-1 GIS datasets are publicly available at the statewide level? (Select all that apply) "Publicly available" means the dataset can be accessed without restriction by external users (e.g., via download, open data portal, or public map service)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_instructions (type: esriFieldTypeString, alias: Please complete this section if GIS is used in your state government to support any aspect of election administration, including voter address validation, boundary management, interactive public election maps or dashboards, or use of state GIS technology or other GIS resources. You may need to consult with your State Election Director or Secretary of State's Office, or your State Geospatial Information Office (GIO). If GIS is not currently used to support elections in your state, you may still complete this section by selecting "No," "Not applicable," or "Unsure" where appropriate., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_effort (type: esriFieldTypeString, alias: 1. Does your state have a state-level programmatic effort to support Geo-Enabled Elections? (In other words, is there a state-scale initiative or formal program aimed at integrating Geographic Information Systems (GIS) into election management processes?), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_active: Yes – the program is active and operational], [yes_development: Yes – the program is in development or pilot phase], [yes_early_plan: Yes – the program is in an early planning phase (e.g., exploratory meetings, volunteer group, no formal funding)], ... 1 more ...)
gee_responsible_agency (type: esriFieldTypeString, alias: 2. Is there a designated agency(s) or entity(s) responsible for managing the Geo-Enabled Elections Program in your state?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_specific_agency: Yes – a specific agency(s) or entity(s) is officially responsible], [no_informal: No – the program is managed informally or collaboratively], [no_stewardship: No – there is no clear stewardship], ... 1 more ...)
gee_extent (type: esriFieldTypeString, alias: 3. At what scale is the Geo-Enabled Elections Program currently implemented?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [statewide: Statewide], [pilot_program: Pilot program (limited to a few jurisdictions)], [local_effort: Local led effort], ... 1 more ...)
gee_governance (type: esriFieldTypeString, alias: 4. Is your Geo-Enabled Elections Program supported by any formal governance mechanism guiding the integration of GIS into election management?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_statute_eo: Yes – statute or executive order], [yes_agency_policy: Yes – agency policy or administrative rule], [yes_informal: Yes – informal coordination or voluntary agreements], ... 3 more ...)
gee_governance_descr (type: esriFieldTypeString, alias: (Optional) Please briefly describe the governance structure or policy backing your program:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
gee_statutes (type: esriFieldTypeString, alias: 5. Does your state have any statute(s) in place that regulate the following:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_distr_data_statute (type: esriFieldTypeString, alias: District map or geospatial data creation and maintenance, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
precinct_data_statute (type: esriFieldTypeString, alias: Precinct map or geospatial data creation and maintenance, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
admin_bdry_statute (type: esriFieldTypeString, alias: Administrative boundary map or geospatial data creation and maintenance (such as cities, towns, school districts, etc.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
creation_authority (type: esriFieldTypeString, alias: Does your state have overarching authority to create geospatial data infrastructure (SDI)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
gee_program_strategy (type: esriFieldTypeString, alias: 6. Does your Geo-Enabled Elections Program have a documented long-term strategy or implementation plan (i.e., a formal business plan)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal_plan: Yes – a formal, written plan is in place and actively used], [yes_plan_exists: Yes – a plan exists, but it is outdated or not actively used], [no_in_dev: No – a plan is currently in development], ... 2 more ...)
gee_funding (type: esriFieldTypeString, alias: 7. Is there currently dedicated funding for your state's Geo-Enabled Elections work?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_ongoing_funding: Yes – ongoing funding], [yes_one_time: Yes – one-time or grant-based funding], [no_dedicated_fund: No – dedicated GIS funding])
gee_geospatial_fund (type: esriFieldTypeString, alias: 8. Is there dedicated funding specifically for the geospatial components of your state's Geo-Enabled Elections work?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_ongoing_funding: Yes – ongoing funding], [yes_one_time: Yes – one-time or grant-based funding], [no_general_ops: No – GIS is absorbed into general operations], ... 1 more ...)
gee_coordinate_funding (type: esriFieldTypeString, alias: 9. Does the Geo-Enabled Elections program or work coordinate funding or resources with the State GIO, or equivalent?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_shared_budgets: Yes – shared budgeting or cost sharing], [no_separate_budgets: No – separate budgets], [not_applicable: Not applicable])
gee_data_usage (type: esriFieldTypeString, alias: 10. How are geospatial data and tools used in your Geo-Enabled Elections program/initiative?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_mapping_tools (type: esriFieldTypeString, alias: 12. Are there statewide public-facing mapping tools available to help voters access information (e.g., precinct look-up, polling place finder, ballot preview tools)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_interactive_tools: Yes – state government provides interactive, map-based tools are publicly available and up to date], [yes_tools_exist: Yes – tools exist, but functionality is limited or not updated regularly], [no_tools_local: No - these tools are run by local government], ... 2 more ...)
gee_architecture (type: esriFieldTypeString, alias: 13. Does your Geo-Enabled Elections program/initiative rely on state centralized or an enterprise geospatial architecture?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_integrated: Yes – fully integrated], [partially: Partially – some components use it], [no_standalone: No – our systems are standalone], ... 1 more ...)
gee_analytics_note1 (type: esriFieldTypeString, alias: This section explores how your state uses GIS to support the spatial validation and geocoding of voter addresses—a foundational component of a Geo-Enabled Elections program. Spatial analytics help ensure that voter addresses are correctly placed within the appropriate precincts and districts, reducing ballot errors and improving assignment accuracy., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_analytics_note2 (type: esriFieldTypeString, alias: You'll be asked about the tools and processes used to validate addresses, the presence and type of geocoding services, how those services are applied within election workflows, and how geocoded data is maintained over time. These insights can help assess the technical maturity of your state's Geo-Enabled Elections program and the role of GIS in maintaining its accuracy., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_addr_validation (type: esriFieldTypeString, alias: 14. Are voter addresses spatially validated using a GIS-enabled process?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_local: Yes – At the local government level, GIS tools are used to validate addresses against authoritative data], [yes_state: Yes – At the state government level, GIS tools are used to validate addresses against authoritative data], [both: Both - At the both the local & state government levels, GIS tools are used to validate addresses against authoritative data], ... 3 more ...)
gee_web_geocode (type: esriFieldTypeString, alias: 15. Does your state use a geocoding web service to locate voter addresses and assign voters to precincts or districts?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_commercial: Yes – via a commercial service], [yes_state_service: Yes – via a state-managed service], [yes_both: Yes – via both commercial and state], ... 2 more ...)
gee_web_geocode_no (type: esriFieldTypeString, alias: If no geocoding service is used, please briefly explain why:, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
gee_geocoding_use (type: esriFieldTypeString, alias: 16. How is the geocoding service used within the voter address management process?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_data_maintain (type: esriFieldTypeString, alias: 17. How is the geocoded address data maintained over time in the voter management system?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_coord_note1 (type: esriFieldTypeString, alias: Effective implementation of a Geo-Enabled Elections program depends on strong coordination among state and local stakeholders, as well as with national initiatives. This section explores the working relationships between election offices and GIS teams, including how your program engages with local jurisdictions, the State Geospatial Information Office (GIO, or equivalent), and national partners., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_coord_note2 (type: esriFieldTypeString, alias: Whether your program is led by election officials, GIS professionals, or a mix of both, this section is designed to capture the nature and depth of those collaborations. Your responses will help identify successful partnership models, as well as areas where further support or guidance could strengthen statewide integration of geospatial tools into election administration., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_prog_collab (type: esriFieldTypeString, alias: 18. Does your Geo-Enabled Elections program involve collaboration with local election offices or local GIS teams to support data aggregation and/or sharing?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes – formal agreements or partnerships are in place statewide], [yes_local: Yes – local governments participate through informal or voluntary collaboration], [no_collab: No – there is no local collaboration at this time], ... 2 more ...)
gee_prog_coordinate (type: esriFieldTypeString, alias: 19. Does the state election's program coordinate with the State Geospatial Information Office (GIO) or equivalent?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes – formal collaboration (e.g., shared governance, MOUs, working groups, etc)], [yes_informal: Yes – informal collaboration (e.g., ad hoc meetings, project-based coordination)], [no_coord_use_services: No coordination and the state election's office uses services (data, software, etc) from the GIO's office (or equivalent)], ... 2 more ...)
gee_prog_engage (type: esriFieldTypeString, alias: 20. In what ways does the state election's program engage with the State GIO?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_prog_natl_coord (type: esriFieldTypeString, alias: 21. Does your Geo-Enabled Elections program coordinate with any national-level initiatives or organizations?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_data_note1 (type: esriFieldTypeString, alias: Your program either produces or relies on foundational geospatial datasets that contribute to the strength of your state's overall geospatial ecosystem. These datasets—such as address points, precinct boundaries, and administrative districts—are often supported or stewarded, directly or indirectly, by the State Geospatial Information Office (GIO). In some states, the GIO plays a central role in developing and maintaining these layers; in others, the GIO may designate stewardship to other agencies or partners., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_data_note2 (type: esriFieldTypeString, alias: Because of this connection, your Geo-Enabled Elections program plays a critical role in shaping the maturity and sustainability of your state's geospatial infrastructure. As part of the broader Geospatial Maturity Assessment (GMA), the following questions are designed to better understand how your program depends on and contributes to this shared foundation., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_dataset_rely (type: esriFieldTypeString, alias: 22. Which of the following geospatial datasets does your Geo-Enabled Elections program rely on?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_dataset_prod (type: esriFieldTypeString, alias: 23. Which of the following datasets are produced and maintained, in whole or in part, as a result of your state's effort to geo-enable elections?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_dataset_access (type: esriFieldTypeString, alias: 24. Which of the following datasets are publicly accessible?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_precinct_reassign (type: esriFieldTypeString, alias: 25. Is the precinct boundary layer used to spatially reassign voters within the voter registration system?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – the GIS layer directly informs voter assignment], [partially: Partially – it is used in some counties or in coordination with other tools], [no: No – voter assignment is managed separately], ... 2 more ...)
gee_manage_precinct (type: esriFieldTypeString, alias: 26. Who is responsible for managing the statewide precinct boundary layer?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [state_election_office: State election office], [state_gis_office: State GIS office (GIO or equivalent)], [local_gov: Local governments (e.g., counties submit their own data)], ... 3 more ...)
gee_precinct_update (type: esriFieldTypeString, alias: 27. How frequently is the precinct boundary layer updated?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [static: It is static (not updated regularly)], [as_changes: It is updated as changes are made], [regular_schedule: It is updated on a regular schedule (e.g., annually, monthly, quarterly)], ... 2 more ...)
gee_precinct_archive (type: esriFieldTypeString, alias: 28. Are previous versions of the precinct boundaries archived or versioned?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_archive: Yes – each version is archived], [yes_snapshot: Yes – at least one snapshot of the data is archived annually], [no_archive: No – prior versions are overwritten or not stored], ... 2 more ...)
gee_precinct_standard (type: esriFieldTypeString, alias: 29. Are your precinct boundaries developed using a standard, best practice, or guidelines?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_nat_standard: Yes – follow national standard, best practice, or guidelines (e.g., NSGIC)], [yes_nat_state: Yes – national standards, adapted or enhanced for state-specific use], [yes_state_only: Yes – based solely on state or agency-specific standards], ... 4 more ...)
gee_precinct_web_portal (type: esriFieldTypeString, alias: 30. Is there a public mapping web portal to visually explore the precinct boundary dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [unsure: Unsure])
gee_api (type: esriFieldTypeString, alias: 31. Is an API or web service available for access to the precinct boundaries?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [unsure: Unsure])
gee_api_url (type: esriFieldTypeString, alias: 32. If you answered yes to #31, please provide a URL where more information or access to the precinct boundary dataset is available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
gee_additional (type: esriFieldTypeString, alias: 33. What additional information would you like to share to help improve NSGIC's support of the GeoEnabled Elections Initiative? We appreciate any additional information., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_description (type: esriFieldTypeString, alias: This graded section assesses your state's progress in developing and maintaining an authoritative, statewide Address Theme dataset that is curated, maintained, and shared by a responsible agency or designated steward. The ultimate goal for states is to establish a formalized program that ensures the dataset meets a consistent level of quality, is regularly updated, and supports decision-making needs across multiple sectors., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_effort (type: esriFieldTypeString, alias: 1. Is there an effort in your state to develop an authoritative, statewide Address Theme dataset? Statewide, in this case, refers to all authoritative data under the sovereignty of the United States. If a program is "Statewide" the program's intent is that all authoritative local government sources are able and willing to participate (i.e. this does not mean that in order to be statewide, all authorities are currently participating). Tribal Nations' and Military Installations' data is not considered to be required as part of the statewide dataset, but if it is, can be acknowledged in questions 2 and 3., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
addr_cooperate_tribal (type: esriFieldTypeString, alias: 2. Does your state cooperate with Tribal Nations to populate this theme? *Note that Tribal Nations are sovereign over their data. While beneficial in many cases for States to coordinate with Tribal Nations to share data, at this time, the presence of that coordination is not being graded., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_regularly: Yes, regularly], [yes_intermittently: Yes, intermittently], [no: No], ... 2 more ...)
addr_cooperate_mil (type: esriFieldTypeString, alias: 3. Does your state cooperate with military installations to populate this theme? *Note that military installations' data sharing agreements with their states are extremely variable across the nation. While beneficial for States to coordinate with the military to share data, at this time, the presence of that coordination is not being graded, as it may be inconsistent., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_regularly: Yes, regularly], [yes_intermittently: Yes, intermittently], [no: No], ... 2 more ...)
addr_program (type: esriFieldTypeString, alias: 4. Does your state have a program in place to support the Address Theme dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
addr_prog_characteristics (type: esriFieldTypeString, alias: 5. Which of the following characteristics apply to your state's Address Theme data/program? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_extra_intelligence (type: esriFieldTypeString, alias: 6. Is your state's authoritative Address Theme dataset attributed with additional intelligence beyond the full address, such as but not limited to sub-address information (e.g., unit numbers), land use (e.g., residential, commercial), or point placement type (e.g., parcel centroid, front door)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_intelligence: Yes], [no_intelligence: No, it is not attributed with additional intelligence])
addr_attributes (type: esriFieldTypeString, alias: 7. Which of the following attributes are included in your state's authoritative Address Theme dataset? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_attributes_applied (type: esriFieldTypeString, alias: 8. How consistently are the added intelligence (attributes such as those above) applied across the statewide dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [consistently: Consistently], [inconsistently: Inconsistently])
addr_complete (type: esriFieldTypeString, alias: 9. What percentage of your state is currently covered in your authoritative Address Theme dataset? (Select one) *Note this percentage should not include sovereign Tribal Nation or military installation data, and is based on jurisdictions, not actual addresses., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [100_complete: 100%], [90_99: 90-99%], [80_89: 80-89%], ... 8 more ...)
addr_maintained (type: esriFieldTypeString, alias: 10. How is your state's Address Theme dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
addr_update_freq (type: esriFieldTypeString, alias: 11. What is the frequency of updates by local authorities to the state for your statewide Address Theme dataset? *Note that this is the collection of data, not necessarily the publication of the statewide dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [as_needed: As needed (i.e. varies based on the local authority's frequency of updates but is "up to date")], [daily: Daily], [weekly: Weekly], ... 6 more ...)
addr_standardization (type: esriFieldTypeString, alias: 12. What level of standardization is used in developing your state's Address Theme data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [nena_verif: Published to the NENA GIS Data Model (Site/Structure Address Points), or a state-level standard that is compatible with and can be integrated into the NENA model, and verified via stakeholder/in-house QA/QC], [nena_no_verif: Published to the NENA GIS Data Model (Site/Structure Address Points), or a state-level standard that is compatible with and can be integrated into the NENA model, but not verified via stakeholder/in-house QA/QC], [non_nena_verif: Published to a non-NENA based standard (state-level, ISO ie. USPS28, FGDC) and verified via stakeholder/in-house QA/QC], ... 3 more ...)
addr_metadata (type: esriFieldTypeString, alias: 13. Does your state's Address Theme dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
addr_public_domain (type: esriFieldTypeString, alias: 14. What percentage of your statewide Address Theme dataset is currently in the public domain (ie. Published for public access)? *Note this percentage includes coverage of your statewide Address Theme dataset but should not include sovereign Tribal Nation or military installation data. Additionally, the percentage is based on jurisdictions, not actual addresses., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [100_complete: 100%], [90_99: 90-99%], [80_89: 80-89%], ... 8 more ...)
addr_remainder_access (type: esriFieldTypeString, alias: 15. If you answered less than 100%, to what extent are the remainder of the Addresses in the state accessible? *Note: There are many nuances to accessibility of data. For this question, respondents should choose the option that best describes the level of accessibility in most cases for their dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], [restricted: Restricted - Available only to specific government agencies (e.g., emergency management, NG9-1-1, local governments, internal agency use)], ... 1 more ...)
addr_nad_contribute (type: esriFieldTypeString, alias: 16. Do you contribute your public domain statewide Address Theme dataset to the National Address Dataset (NAD)? *Note: this assumes that the percentage of publication is the same as that for the publication into the public domain., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
addr_redaction_rules (type: esriFieldTypeString, alias: 17. Are there rules for redaction of addresses in your state that are applied to your statewide Address Theme dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
addr_publish_freq (type: esriFieldTypeString, alias: 18. What is the publication frequency of the aggregated statewide data to the public?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [daily: Daily], [weekly: Weekly], [monthly: Monthly], ... 3 more ...)
addr_access_cost (type: esriFieldTypeString, alias: 19. Is your statewide Address Theme dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
addr_download (type: esriFieldTypeString, alias: 20. Is your statewide Address Theme dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
addr_web_portal (type: esriFieldTypeString, alias: 21. Does your state provide a web interface (ex. ESRI web application) where users can view the Address Theme dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
addr_api (type: esriFieldTypeString, alias: 22. Does your state provide an API or web service to interact with the Address Theme dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
addr_url (type: esriFieldTypeString, alias: 23. Please provide a URL where more information about your state's Address Theme data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_single_multi_use (type: esriFieldTypeString, alias: 24. Is your state's Address Theme dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
addr_state_use (type: esriFieldTypeString, alias: 25. How does your state use the statewide Address Theme data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
addr_additional (type: esriFieldTypeString, alias: 26. Use this space to share any additional details about your state's Address Theme data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Address Theme program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
cadastre_note1 (type: esriFieldTypeString, alias: We are requesting states respond to this section using a template geodatabase (a.k.a. 'gdb'). This allows NSGIC and other stakeholders to visualize the maturity of cadastral programs across the country., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_note2 (type: esriFieldTypeString, alias: Special Note: If your state completed the GMA Parcels geodatabase in 2023, your 2025 geodatabase will be pre-populated with your 2023 responses, so you can simply review and update as needed—no need to start from scratch!!!, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_confirm_gdb (type: esriFieldTypeString, alias: I confirm that I (or someone in my state) has calculated values in our state's GDB, zipped up the completed GDB, and uploaded it to the Completed folder in the GMA Google Drive., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
cadastre_note3 (type: esriFieldTypeString, alias: Most questions found in the theme PDF are answered in the gdb. Additional questions are asked here in the survey and will reference the completed gdb; please have it pulled up for reference while completing this section., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_program_details (type: esriFieldTypeString, alias: 3. If you answered No to geodatabase field name "PROGRAM, 2-Central Program": Additional information requested if there is no formal program in your state: is there an effort in to develop an authoritative, statewide Cadastre/Parcel dataset? (Select one option and add additional details if needed), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes, an effort is underway to develop a statewide dataset], [no_but_plan: No there is no current effort to develop a statewide dataset, but we are planning to do so in the future.], [no_plans: No, there is no current effort to develop a statewide dataset, and there are no plans to do so in the future.], ... 1 more ...)
cadastre_cadstand (type: esriFieldTypeString, alias: 10. Please select one of the following options about your State Cadastral Standard that you provided in geodatabase field "CADSTAND, Cadastral Standard URL", SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fgdc: Federal Geographic Data Committee (FGDC) Cadastral Data Content Standard], [nsdi: National Spatial Data Infrastructure (NSDI) Cadastre Framework], [iaao: Parcel-Level Data Standards from the International Association of Assessing Officers (IAAO)], ... 2 more ...)
cadastre_metadata (type: esriFieldTypeString, alias: 11. Does your state's Cadastre/Parcel dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
cadastre_contrib_fed (type: esriFieldTypeString, alias: 12. Would your state be willing to contribute your statewide Cadastre/Parcel dataset regularly to a federal level effort to create a nationwide Cadastre/Parcel dataset (e.g. the Bureau of Land Management (BLM) Cadastral Survey Data, the Federal Emergency Management Agency (FEMA) Parcel Data efforts, or the National Geospatial-Intelligence Agency (NGA) Parcel Data Initiative)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
cadastre_funding (type: esriFieldTypeString, alias: 16. If you selected Yes to geodatabase field name "FUNDING, 11-Funding", please provide details on where this funding comes from. (If local governments contribute, simply indicate 'cities' and/or 'counties'—no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_state_use (type: esriFieldTypeString, alias: 17. How does your state use Cadastre/Parcel data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
cadastre_additional (type: esriFieldTypeString, alias: Use this space to share any additional details about your state's Cadastre/Parcel data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Cadastre/Parcel program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
rcl_effort (type: esriFieldTypeString, alias: 1. Is there an effort in your state to develop an authoritative, statewide Road Centerline dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
rcl_program (type: esriFieldTypeString, alias: 2. Does your state have a program in place to support the Road Centerline dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
rcl_attr (type: esriFieldTypeString, alias: 3. Is your state's authoritative Road Centerline dataset attributed with additional attributes that allow it to serve use cases beyond a single agency?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
rcl_attr_include (type: esriFieldTypeString, alias: 4. Which of the following attributes are included in your state's authoritative Road Centerline dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
rcl_pct_coverage (type: esriFieldTypeString, alias: 5. What percentage of your state is currently covered by Road Centerline data in your authoritative dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
rcl_maintained (type: esriFieldTypeString, alias: 6. How is your state's Road Centerline dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
rcl_update_freq (type: esriFieldTypeString, alias: 7. What is the frequency of updates for your statewide Road Centerline dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [daily: Daily], [weekly: Weekly], [monthly: Monthly], ... 8 more ...)
rcl_data_quality (type: esriFieldTypeString, alias: 8. What is the quality of the data? (pick one in each category), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
rcl_qual_standards (type: esriFieldTypeString, alias: Standards, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [published_valid: Published to an approved state or national standard and is validated to ensure consistency of both geometry and attributes], [published_not_valid: Published to an approved state or national standard but not validated against that standard to ensure consistency of both geometry and attributes], [not_published_valid: Not published to a state or national standard but is validated against another standard or data model for consistency of both geometry and attributes], ... 1 more ...)
rcl_qual_metadata (type: esriFieldTypeString, alias: Metadata, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [metadata: Data has metadata], [no_metadata: Data does not have metadata])
rcl_qual_workflow (type: esriFieldTypeString, alias: Workflow, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [workflow: Maintenance process follows a consistent workflow], [no_workflow: Maintenance process does not follow a consistent workflow])
rcl_qual_usage (type: esriFieldTypeString, alias: Single or Multi Use, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multi_use_data: The data has a broad set of attributes and can be used for more than one purpose], [specific_data: The data is designed for specific purpose and does not have utility beyond that])
rcl_qual_usage_more (type: esriFieldTypeString, alias: Please share what use cases your agency has for the road centerlines?, SQL Type: sqlTypeOther, length: 1000, nullable: true, editable: true)
rcl_qual_addr (type: esriFieldTypeString, alias: Address Ranges, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [addr_ranges: Data contains address ranges], [no_addr_ranges: Data does not have address ranges])
rcl_qual_route (type: esriFieldTypeString, alias: Routing Capability, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [routable: Data contains topology and connectivity and is can be used as a routable network in a GIS system], [not_routable: Data is not topologically correct and not routable])
rcl_metadata (type: esriFieldTypeString, alias: 9. Does your state's Road Centerline dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
rcl_contrib_safety (type: esriFieldTypeString, alias: 10. Do you contribute your statewide Road Centerline dataset to the safety efforts, HPMS, ARNOLD, etc.?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [other: Other (Provide explanation below)])
rcl_available (type: esriFieldTypeString, alias: 11. How is your statewide Road Centerline dataset accessible to the public?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
rcl_access_cost (type: esriFieldTypeString, alias: 12. Is your statewide Road Centerline dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
rcl_download (type: esriFieldTypeString, alias: 13. Is your statewide Road Centerline dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
rcl_web_portal (type: esriFieldTypeString, alias: 14. Does your state provide a web portal where users can view the Road Centerline dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
rcl_api (type: esriFieldTypeString, alias: 15. Does your state provide an API or web service to interact with the Road Centerline dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
rcl_url (type: esriFieldTypeString, alias: 16. Please provide a URL where more information about your state's Road Centerline data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
rcl_characteristics (type: esriFieldTypeString, alias: 17. A Road Centerline Program is defined as the formalized effort to develop, maintain, standardize, and share the authoritative dataset. A program typically includes governance structures, funding, data-sharing agreements, staff, workflows, outreach/education/training efforts, and quality control processes to ensure long-term sustainability and usability. Which of the following characteristics apply to your state's Road Centerline data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
rcl_single_multi_use (type: esriFieldTypeString, alias: 18. Is your state's Road Centerline dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
rcl_state_use (type: esriFieldTypeString, alias: 19. How does your state use Road Centerline data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
rcl_additional (type: esriFieldTypeString, alias: 20. Use this space to share any additional details about your state's Road Centerline data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Road Centerline program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
hydro_description (type: esriFieldTypeString, alias: Because 3DHP is a new and evolving program, the Hydrography Theme is a non-graded section of the 2025 GMA. The survey responses gathered are intended to inform a broader audience on where states are in their efforts to transition to the 3DHP framework., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_data_effort (type: esriFieldTypeString, alias: 1. Does your state currently have (or is in the process of developing) an authoritative, statewide hydrography dataset that meets 3DHP specifications? Note: This refers specifically to your state's authoritative 3DHP-aligned dataset. It may be fully developed, partially complete, under active development, or still in the planning stage., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_dataset: Yes – A fully developed, authoritative statewide dataset exists and is actively maintained.], [yes_exists: Yes – A dataset exists, but it is incomplete or inconsistently maintained.], [not_yet: Not yet – We are in the planning phase and exploring or designing an approach from legacy data to a 3DHP-aligned framework.], ... 2 more ...)
hydro_program (type: esriFieldTypeString, alias: 2. Does your state have a program in place to support the 3DHP elevation derived Hydrography dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
hydro_connect_attr (type: esriFieldTypeString, alias: 3. Does your state plan to connect attributes to the authoritative 3DHP data for your State?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
hydro_pct_acceptance (type: esriFieldTypeString, alias: 4. What percentage of your state hydrography is currently accepted in the USGS authoritative 3DHP database?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
hydro_to_3dhp (type: esriFieldTypeString, alias: 5. Do you plan to contribute your statewide Elevation-Derived Hydrography dataset to the USGS 3DHP?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [other: Other (Provide explanation below)])
hydro_available (type: esriFieldTypeString, alias: 6. Is your statewide Elevation-Derived Hydrography dataset that is not in the 3DHP dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 3 more ...)
hydro_access (type: esriFieldTypeString, alias: 7. Is your statewide Elevation-Derived Hydrography dataset that is not in the 3DHP dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
hydro_download (type: esriFieldTypeString, alias: 8. Is your statewide Elevation-Derived Hydrography dataset that is not in the 3DHP dataset available for download directly from your State?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
hydro_web_portal (type: esriFieldTypeString, alias: 9. Does your state provide a web portal where users can view the Elevation-Derived Hydrography dataset that is not in the 3DHP dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available – Users can explore, search, and view Hydrography data online.], [limited_portal: Yes, but limited – A web portal exists, but it only provides limited or static views of the data.], [no_portal: No, there is no web portal available.], ... 1 more ...)
hydro_api (type: esriFieldTypeString, alias: 10. Does your state provide an API or web service to interact with the 3DHP-aligned Hydrography dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
hydro_url (type: esriFieldTypeString, alias: 11. Please provide a URL where more information about your state's Elevation-Derived Hydrography data, program or 3DHP acquisition program can be accessed. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset. This helps other states find and learn from your program., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_characteristics (type: esriFieldTypeString, alias: 12. Which of the following characteristics apply to your state's 3DHP Hydrography data/program? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_state_use (type: esriFieldTypeString, alias: 13. How does your state use Hydrography data? (Select all that apply – use cases may reflect state, regional, or local activities), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_additional (type: esriFieldTypeString, alias: 14. Use this space to share any additional details about your state's Hydrography data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Hydrography program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
hydro_3dhp_transition_note (type: esriFieldTypeString, alias: Note: The following questions are for informational purposes only. They are intended to help NSGIC and national partners better understand your state's future direction, interest in participating in the 3D Hydrography Program (3DHP), and any funding considerations. Your candid input is appreciated., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
hydro_3dhp_support (type: esriFieldTypeString, alias: 15. Do you believe that the 3D Hydrography Program (3DHP) will adequately support your state's hydrography needs?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – 3DHP aligns well with our needs and use cases], [partially: Partially – It may meet some needs but not all], [no: No – It does not appear to meet our state's needs])
hydro_3dhp_participate (type: esriFieldTypeString, alias: 16. Does your state plan to participate (if not participating already) in the 3D Hydrography Program (3DHP)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – We plan to actively participate and provide data], [no: No – We do not plan to contribute], [undecided: Undecided – Still evaluating or need more information])
dca_funding (type: esriFieldTypeString, alias: 17. Has your state previously applied for hydrography funding through a USGS Data Collaboration Announcement (DCA, formerly known as the Broad Agency Announcement or BAA)? Note: The DCA is a USGS funding opportunity that supports collaborative projects to improve hydrography data, including elevation-derived flowlines, attribution enhancements, or contributions to the 3D Hydrography Program (3DHP)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_success: Yes – Our state has submitted a DCA application in a previous cycle and it was successfully awarded], [yes_submitted: Yes – Our state has submitted a DCA application in a previous cycle and it was not awarded or the status is unknown at this time], [no: No – Our state has not applied], ... 1 more ...)
dca_funding_fy2526 (type: esriFieldTypeString, alias: 18. Does your state plan to apply for hydrography funding through a DCA in the FY25–26 cycle?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – We plan to apply], [no: No – We do not plan to apply], [undecided: Undecided – Still evaluating], ... 1 more ...)
hydro_3dhp_connect (type: esriFieldTypeString, alias: 19. Does your state plan to connect its own attribute data to 3DHP features? Note: This may include linking local or state-maintained information (e.g., stream names, regulatory classifications, permits, monitoring stations) to 3DHP flowlines using methods such as events, joins, relates, addressing, or linear referencing., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – We plan to integrate our attribute data with 3DHP], [no: No – We do not plan to integrate attributes], [undecided: Undecided – Still evaluating options or need more information])
nhd_3dhp_perspective (type: esriFieldTypeString, alias: 20. What is your state's perspective on the national transition from the National Hydrography Dataset (NHD) to the 3D Hydrography Program (3DHP)?, SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
ortho_which_types (type: esriFieldTypeString, alias: 1. Based on your state's ecosystem and imagery needs, which types of orthoimagery are relevant and necessary for your statewide program? Regardless of which option you choose, please fill out both sections with the context that imagery in each category may exist in smaller areas, especially metropolitan or industrial regions., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [leaf_on_only: Leaf-On only – Our state does not have significant seasonal leaf variation or canopy coverage that obscures infrastructure or hinders tax assessment and administration. Only leaf-on imagery is necessary to meet our needs.], [both: Both Leaf-On and Leaf-Off – Our state has seasonally variable vegetation that necessitates both types of imagery to meet mapping, emergency response, infrastructure visibility, or other operational needs.], [unsure: Unsure – We are not certain which types of imagery are required in our state.])
lon_naip_enhance (type: esriFieldTypeString, alias: 1. Does your state enhance the baseline NAIP imagery provided by USDA in any way (e.g., resolution, accuracy, delivery speed, frequency, or format)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – Our state purchases enhancements (buy-ups) through USDA's NAIP contracting vehicle or supplements NAIP with additional state-funded efforts.], [no: No – Our state uses NAIP imagery as-is, with no enhancements or supplemental acquisition.], [other: Other (Provide explanation below)])
lon_enhance_ways (type: esriFieldTypeString, alias: 2. In what ways has your state enhanced the baseline NAIP imagery offering?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_program (type: esriFieldTypeString, alias: 3. Does your state have a program in place to support your enhanced NAIP leaf-on orthoimagery?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
lon_buyups (type: esriFieldTypeString, alias: 4. Does your state facilitate a contracting mechanism that further enables local governments to enhance or supplement the state's already enhanced NAIP leaf-on orthoimagery offering (often referred to as enabling 'buy-ups')?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_naip: Yes – We facilitate access to the USDA NAIP contracting mechanism to help local governments purchase imagery enhancements.], [yes_coop: Yes – We offer a cooperative procurement vehicle, master agreement, or shared contract outside of NAIP that local governments can use to purchase enhancements or additional imagery.], [no: No – Local governments must procure imagery independently.], ... 2 more ...)
lon_attr (type: esriFieldTypeString, alias: 5. Is your state's enhanced NAIP leaf-on orthoimagery dataset attributed with additional intelligence (e.g., thematic overlays, classifications, or contextual data)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
lon_attr_include (type: esriFieldTypeString, alias: 6. Which of the following attributes are included in your state's enhanced NAIP leaf-on orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_pct_coverage (type: esriFieldTypeString, alias: 7. What percentage of your state is currently covered by the enhanced NAIP leaf-on orthoimagery upgrades you've purchased?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
lon_maintained (type: esriFieldTypeString, alias: 8. How is your state's enhanced NAIP leaf-on orthoimagery dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
lon_update_freq (type: esriFieldTypeString, alias: 9. What is the frequency of updates for your enhanced NAIP leaf-on orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [annually: Annually], [2_3_yrs: Every 2-3 years], [more_3_years: Every >3 years], ... 3 more ...)
lon_standardization (type: esriFieldTypeString, alias: 10. What level of standardization is used in developing your state's enhanced NAIP leaf-on orthoimagery data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
lon_metadata (type: esriFieldTypeString, alias: 11. Does your state's enhanced NAIP leaf-on orthoimagery dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
lon_available (type: esriFieldTypeString, alias: 12. Is your enhanced NAIP leaf-on orthoimagery dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open – Anyone can access the data without an account.], [partially_free: Partially free – Some access is free, but certain data layers, formats, or higher-resolution versions require payment or are restricted.], [requires_account: Requires account creation – Users must create an account but are automatically granted access.], ... 3 more ...)
lon_download (type: esriFieldTypeString, alias: 13. Is your statewide enhanced NAIP leaf-on orthoimagery dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
lon_web_portal (type: esriFieldTypeString, alias: 14. Does your state provide a web portal where users can view the enhanced NAIP leaf-on orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
lon_api (type: esriFieldTypeString, alias: 15. Does your state provide an API or web service to interact with the enhanced NAIP leaf-on orthoimagery dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
lon_url (type: esriFieldTypeString, alias: 16. Please provide a URL where more information about your state's enhanced NAIP leaf-on orthoimagery data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_characteristics (type: esriFieldTypeString, alias: 17. Which of the following characteristics apply to your state's enhanced NAIP leaf-on orthoimagery data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_state_use (type: esriFieldTypeString, alias: 18. How does your state use your enhanced NAIP leaf-on orthoimagery data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
lon_additional (type: esriFieldTypeString, alias: 19. Use this space to share any additional details about your state's enhanced NAIP leaf-on orthoimagery data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its enhanced NAIP leaf-on orthoimagery program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
loff_add_options (type: esriFieldTypeString, alias: 20. Please indicate if you opt for any additional options such as a buy up or other product., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_effort (type: esriFieldTypeString, alias: 21. Is there an effort in your state to develop an authoritative statewide leaf-off orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
loff_spectral_bands (type: esriFieldTypeString, alias: 22. Which spectral bands are collected as part of your state's Leaf-Off orthoimagery program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_program (type: esriFieldTypeString, alias: 23. Does your state have a program in place to support the leaf-off orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
loff_buyups (type: esriFieldTypeString, alias: 24. Does your state facilitate a contracting mechanism that enables local governments to enhance or supplement the statewide leaf-off imagery offering (often referred to as enabling 'buy-ups')?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – We offer a cooperative procurement vehicle, master agreement, or shared contract that local governments can use to purchase enhancements or additional imagery.], [no: No – Local governments must procure imagery independently.], [in_development: In development – We are actively exploring or building a statewide procurement option.], ... 1 more ...)
loff_attr (type: esriFieldTypeString, alias: 25. Is your state's leaf-off orthoimagery dataset attributed with additional intelligence (e.g., thematic overlays, classifications, or contextual data)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
loff_pct_coverage (type: esriFieldTypeString, alias: 26. What percentage of your state is currently covered by leaf-off orthoimagery data in your authoritative dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
loff_maintained (type: esriFieldTypeString, alias: 27. How is your state's leaf-off orthoimagery dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
loff_update_freq (type: esriFieldTypeString, alias: 28. What is the frequency of updates for your statewide leaf-off orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [annually: Annually], [2_3_yrs: Every 2-3 years], [more_3_years: Every >3 years], ... 3 more ...)
loff_standardization (type: esriFieldTypeString, alias: 29. What level of standardization is used in developing your state's leaf-off orthoimagery data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
loff_metadata (type: esriFieldTypeString, alias: 30. Does your state's leaf-off orthoimagery dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
loff_available (type: esriFieldTypeString, alias: 31. Is your statewide leaf-off orthoimagery dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open – Anyone can access the data without an account.], [partially_free: Partially free – Some access is free, but certain data layers, formats, or higher-resolution versions require payment or are restricted.], [requires_account: Requires account creation – Users must create an account but are automatically granted access.], ... 3 more ...)
loff_download (type: esriFieldTypeString, alias: 32. Is your statewide leaf-off orthoimagery dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
loff_web_portal (type: esriFieldTypeString, alias: 33. Does your state provide a web portal where users can view the leaf-off orthoimagery dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
loff_api (type: esriFieldTypeString, alias: 34. Does your state provide an API or web service to interact with the leaf-off orthoimagery dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
loff_url (type: esriFieldTypeString, alias: 35. Please provide a URL where more information about your state's leaf-off orthoimagery data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_characteristics (type: esriFieldTypeString, alias: 36. Which of the following characteristics apply to your state's leaf-off orthoimagery data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_single_multi_use (type: esriFieldTypeString, alias: 37. Is your state's leaf-off orthoimagery dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
loff_state_use (type: esriFieldTypeString, alias: 38. How does your state use leaf-off orthoimagery data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
loff_additional (type: esriFieldTypeString, alias: 39. Use this space to share any additional details about your state's leaf-off orthoimagery data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its leaf-off orthoimagery program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
govt_effort (type: esriFieldTypeString, alias: 1. Is there an effort in your state to develop an authoritative, statewide Municipalities dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
govt_program (type: esriFieldTypeString, alias: 2. Does your state have a program in place to support the Municipalities dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
govt_attr (type: esriFieldTypeString, alias: 3. Is your state's authoritative Municipalities dataset attributed with additional intelligence, such as legal status (e.g., incorporation date), jurisdictional codes (e.g., FIPS or GEOID), land area, population estimates, or boundary authority/source?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
govt_attr_include (type: esriFieldTypeString, alias: 4. Which of the following attributes are included in your state's authoritative Municipalities dataset? (Select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_maintained (type: esriFieldTypeString, alias: 5. How is your state's Municipalities dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
govt_update_freq (type: esriFieldTypeString, alias: 6. What is the frequency of updates for your statewide Municipalities dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [monthly: Monthly], [quarterly: Quarterly], [2_x_year: 2 times per year], ... 3 more ...)
govt_standardization (type: esriFieldTypeString, alias: 7. What level of standardization is used in developing your state's Municipalities data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
govt_metadata (type: esriFieldTypeString, alias: 8. Does your state's Municipalities dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
govt_bas_process (type: esriFieldTypeString, alias: 9. Does your state participate in the U.S. Census Bureau's Boundary and Annexation Survey (BAS) process—either by submitting boundary changes directly, coordinating with local governments, or providing statewide boundary data? Note: Participation in BAS does not require formal enrollment in the State Certification Program (see next question). This question is intended to capture any state-level role in submitting, reviewing, coordinating, or supporting the BAS process, even informally., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes, my state actively participates in the BAS process in one or more of the following ways: submitting boundary updates directly to the Census Bureau, coordinating or aggregating submissions from local governments, verifying data, or providing a statewide authoritative boundary dataset.], [no: No, my state does not directly engage in the BAS process in any capacity. Local governments may submit individually, but there is no state-level coordination, review, or contribution.], [other: Other (Provide explanation below)])
govt_scp (type: esriFieldTypeString, alias: 10. Does your state formally participate in the Census' BAS process through the State Certification Program, where a designated State Certified Official (SCO) verifies and/or submits local government BAS submissions?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes, my state has an appointed SCO who works with the Census Bureau and local governments during the BAS process.], [no: No, my state does not participate in this formal role, and BAS submissions are made directly from local governments without centralized state review.])
govt_available (type: esriFieldTypeString, alias: 11. Is your statewide Municipalities dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
govt_access_cost (type: esriFieldTypeString, alias: 12. Is your statewide Municipalities dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
govt_download (type: esriFieldTypeString, alias: 13. Is your statewide Municipalities dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
govt_web_portal (type: esriFieldTypeString, alias: 14. Does your state provide a web portal where users can view the Municipalities dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
govt_api (type: esriFieldTypeString, alias: 15. Does your state provide an API or web service to interact with the Municipalities dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
govt_url (type: esriFieldTypeString, alias: 16. Please provide a URL where more information about your state's Municipalities data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_characteristics (type: esriFieldTypeString, alias: 17. Which of the following characteristics apply to your state's Municipalities data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_single_multi_use (type: esriFieldTypeString, alias: 18. Is your state's Municipalities dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
govt_state_use (type: esriFieldTypeString, alias: 19. How does your state use Municipalities data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_additional (type: esriFieldTypeString, alias: 20. Use this space to share any additional details about your state's Municipalities data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Municipalities program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
govt_counties_note1 (type: esriFieldTypeString, alias: For the purposes of this section, counties (or county equivalents) are defined as local government entities with legally established boundaries that serve as administrative subdivisions of the state. These entities are typically responsible for delivering regional services such as law enforcement, courts, public health, infrastructure maintenance, and tax assessment., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_counties_note2 (type: esriFieldTypeString, alias: Depending on your state, counties may be referred to as counties, parishes (e.g. Louisiana), boroughs (e.g. parts of Alaska), census areas (e.g. parts of Alaska) or independent cities ( e.g. Baltimore, MD and Carson City, NV). Please use your best judgment in identifying which entities in your state align with this definition, and answer the following questions based solely on that dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_county_active_units (type: esriFieldTypeString, alias: 21. Does your state have county-level or equivalent entities that function as active units of government? (This includes counties, parishes, boroughs, townships, or other equivalents that provide governance or regional services like law enforcement, courts, public health, tax administration, or infrastructure management.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
county_effort (type: esriFieldTypeString, alias: 22. Is there an effort in your state to develop an authoritative, statewide County (or equivalent) dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
county_program (type: esriFieldTypeString, alias: 23. Does your state have a program in place to support the County (or equivalent) dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
county_attr (type: esriFieldTypeString, alias: 24. Is your state's authoritative County (or equivalent) dataset attributed with additional intelligence, such as legal status (e.g., incorporation date), jurisdictional codes (e.g., FIPS or GEOID), land area, population estimates, or boundary type?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
county_attr_include (type: esriFieldTypeString, alias: 25. Which of the following attributes are included in your state's authoritative County (or equivalent) dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_maintained (type: esriFieldTypeString, alias: 26. How is your state's County (or equivalent) dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
county_update_freq (type: esriFieldTypeString, alias: 27. What is the frequency of updates for your statewide County (or equivalent) dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [quarterly: Quarterly], [2_x_year: 2 times per year], [annually: Annually], ... 2 more ...)
county_standardization (type: esriFieldTypeString, alias: 28. What level of standardization is used in developing your state's County (or equivalent) data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
county_metadata (type: esriFieldTypeString, alias: 29. Does your state's County (or equivalent) dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
county_access_sharing_note1 (type: esriFieldTypeString, alias: While the Boundary and Annexation Survey (BAS) primarily collects updates to municipal and minor civil division boundaries, county-level boundary changes are also accepted—though they are rare. These changes must be legally enacted at the state level and accompanied by official documentation, such as statutes or resolutions., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_access_sharing_note2 (type: esriFieldTypeString, alias: If your state participates in the State Certification Program, the State Certified Official (SCO) can review and verify county boundary changes submitted through BAS. This certification ensures the updates are accurate, legally valid, and aligned with state records—helping to maintain consistency between state and federal datasets., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_bas_process (type: esriFieldTypeString, alias: 30. Does your state participate in the U.S. Census Bureau's Boundary and Annexation Survey (BAS) process—either by submitting boundary changes directly, coordinating with local governments, or providing statewide boundary data? Note: Participation in BAS does not require formal enrollment in the State Certification Program see next question). This question is intended to capture any state-level role in submitting, reviewing, coordinating, or supporting the BAS process, even informally., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes, my state actively participates in the BAS process in one or more of the following ways: submitting boundary updates directly to the Census Bureau, coordinating or aggregating submissions from local governments, verifying data, or providing a statewide authoritative boundary dataset.], [no: No, my state does not directly engage in the BAS process in any capacity. Local governments may submit individually, but there is no state-level coordination, review, or contribution.], [other: Other (Provide explanation below)])
county_available (type: esriFieldTypeString, alias: 31. Is your statewide County (or equivalent) dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
county_access_cost (type: esriFieldTypeString, alias: 32. Is your statewide County (or equivalent) dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
county_download (type: esriFieldTypeString, alias: 33. Is your statewide County (or equivalent) dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
county_web_portal (type: esriFieldTypeString, alias: 34. Does your state provide a web portal where users can view the County (or equivalent) dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
county_api (type: esriFieldTypeString, alias: 35. Does your state provide an API or web service to interact with the County (or equivalent) dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
county_url (type: esriFieldTypeString, alias: 36. Please provide a URL where more information about your state's County (or equivalent) data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_characteristics (type: esriFieldTypeString, alias: 37. Which of the following characteristics apply to your state's County (or equivalent) data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_single_multi_use (type: esriFieldTypeString, alias: 38. Is your state's County (or equivalent) dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
county_state_use (type: esriFieldTypeString, alias: 39. How does your state use County (or equivalent) data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
county_additional (type: esriFieldTypeString, alias: 40. Use this space to share any additional details about your state's County (or equivalent) data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its County (or equivalent) program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
tribal_note1 (type: esriFieldTypeString, alias: For the purposes of this section, Tribal Government Units are defined as geographic areas with legally established boundaries that are governed by federally recognized Native American tribes. These lands may include reservation, fee or trust lands and are managed by tribal governments with varying degrees of sovereignty recognized by the federal government and, in some cases, by states., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_note2 (type: esriFieldTypeString, alias: Tribal Government Units typically have their own governance structures, land use regulations, and jurisdictional authority. Boundaries maintained or published outside of Tribal Nations are considered authoritative only when developed in consultation with Tribal Nations. If no formal consultation has occurred, they should not be considered authoritative for the purposes of this assessment., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_note3 (type: esriFieldTypeString, alias: Note: Tribal areas may appear in federal datasets under different names or classifications (e.g., "Tribal Statistical Areas" or "Trust Lands"), but for this section, please focus on federally recognized Tribal Government Units with governing authority., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
govt_tribal (type: esriFieldTypeString, alias: 41. Does your state include federally recognized Tribal Government Units with active tribal governments? (These are areas where tribes have legal authority over reservation, fee or trust lands and exercise governance functions such as land use regulation, law enforcement, or service delivery.), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – Proceed with this next set of questions. (e.g., Arizona, New Mexico, Oklahoma, and Washington have multiple federally recognized tribes with active governments and defined lands)], [no: No – Skip to the next section of the Geospatial Maturity Assessment (e.g., Vermont, West Virginia, and New Jersey)], [other: Other – (e.g. the Georgia Tribe of Eastern Cherokee is state-recognized or self-identified, but not federally recognized, and does not have lands acknowledged by the Bureau of Indian Affairs.)])
tribal_effort (type: esriFieldTypeString, alias: 42. Is there an effort in your state to develop an authoritative, statewide Tribal Government Units dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
tribal_program (type: esriFieldTypeString, alias: 43. Does your state have a program in place to support the Tribal Government Units dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
tribal_attr (type: esriFieldTypeString, alias: 44. Is your state's authoritative Tribal Government Units dataset attributed with additional intelligence (e.g., FIPS or GEOID, land area, population estimates, or boundary type)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
tribal_attr_include (type: esriFieldTypeString, alias: 45. Which of the following attributes are included in your state's authoritative Tribal Government Units dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_maintained (type: esriFieldTypeString, alias: 46. How is your state's Tribal Government Units dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
tribal_update_freq (type: esriFieldTypeString, alias: 47. What is the frequency of updates for your statewide Tribal Government Units dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [quarterly: Quarterly], [2_x_year: 2 times per year], [annually: Annually], ... 2 more ...)
tribal_standardization (type: esriFieldTypeString, alias: 48. What level of standardization is used in developing your state's Tribal Government Units data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
tribal_metadata (type: esriFieldTypeString, alias: 49. Does your state's Tribal Government Units dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
tribal_access_sharing_note1 (type: esriFieldTypeString, alias: Note: The Tribal Boundary and Annexation Survey (T-BAS) is conducted annually by the U.S. Census Bureau to allow federally recognized tribes to review and update the legal boundaries of their reservations and trust lands. Participation ensures tribal lands are accurately represented in federal datasets, which supports funding allocations, emergency response, public health programs, and other federal services. While participation is optional and varies by tribe, accurate tribal boundaries are an essential part of national geospatial infrastructure., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_access_sharing_note2 (type: esriFieldTypeString, alias: It is assumed that the state GIO, or equivalent, or other may complete this portion of the GMA, and as such will not have the authority or expertise to speak on behalf of all your state's tribal communities., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tbas_process (type: esriFieldTypeString, alias: 50. To the submitter's knowledge, do any federally recognized tribes within your state participate in the U.S. Census Bureau's Tribal Boundary and Annexation Survey (T-BAS)? Note: This question is intended to assess the state's awareness of tribal participation in the T-BAS process, including whether any tribal governments submit, review, or maintain their reservation or trust land boundaries for Census use. You are not expected to speak on behalf of the tribes, but please answer based on your knowledge or coordination efforts., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes – One or more tribes in our state actively participate in the T-BAS process (e.g., submit updates, review boundaries, or engage with the Census Bureau on tribal land data).], [no: No – To the best of our knowledge, no tribes in our state currently participate in T-BAS.], [unsure: Unsure – We do not have information on tribal participation in T-BAS.], ... 1 more ...)
tribal_available (type: esriFieldTypeString, alias: 51. Is your statewide Tribal Government Units dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
tribal_access_cost (type: esriFieldTypeString, alias: 52. Is your statewide Tribal Government Units dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
tribal_download (type: esriFieldTypeString, alias: 53. Is your statewide Tribal Government Units dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
tribal_web_portal (type: esriFieldTypeString, alias: 54. Does your state provide a web portal where users can view the Tribal Government Units dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
tribal_api (type: esriFieldTypeString, alias: 55. Does your state provide an API or web service to interact with the Tribal Government Units dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
tribal_url (type: esriFieldTypeString, alias: 56. Please provide a URL where more information about your state's Tribal Government Units data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_characteristics (type: esriFieldTypeString, alias: 57. Which of the following characteristics apply to your state's Tribal Government Units data/program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_single_multi_use (type: esriFieldTypeString, alias: 58. Is your state's Tribal Government Units dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
tribal_state_use (type: esriFieldTypeString, alias: 59. How does your state use Tribal Government Units data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
tribal_additional (type: esriFieldTypeString, alias: 60. Use this space to share any additional details about your state's Tribal Government Units data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Tribal Government Units program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)
geodet_description (type: esriFieldTypeString, alias: This section evaluates efforts your state has made to augment and maintain the National Spatial Reference System (NSRS), the foundational coordinate system maintained by the National Geodetic Survey (NGS). NSRS provides the consistent, accurate geodetic framework upon which all spatial data depend., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_program (type: esriFieldTypeString, alias: 1. Does your state have a statewide effort/program in place to actively enhance the NSRS Geodetic Control framework? (informational only), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
geodet_plss_guide1 (type: esriFieldTypeString, alias: Guidance: The Public Land Survey System (PLSS) is a method used to subdivide and describe land in the United States. It is primarily used in the central and western states, though portions of some eastern states also participate. The system is based on townships, ranges, and sections., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_plss_guide2 (type: esriFieldTypeString, alias: States entirely within the PLSS include: Nebraska, Iowa, Colorado, Utah, and Arizona. States partially within the PLSS include: Ohio (northwestern part), Texas (western portion), and Minnesota (excluding the southeast corner). States not included in the PLSS include: the original 13 colonies (e.g., Georgia, Virginia), as well as Kentucky, Tennessee, and Hawaii., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_plss_guide3 (type: esriFieldTypeString, alias: If you are unsure, you may consult the Bureau of Land Management (BLM) or your state geodetic or cadastral office., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_plss (type: esriFieldTypeString, alias: 2. Is any part of your state included in the Public Land Survey System? (informational only), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
geodet_activities (type: esriFieldTypeString, alias: 3. What specific activities are part of your state's statewide Geodetic Control program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_attr_guidance (type: esriFieldTypeString, alias: Guidance: Additional descriptive information may include monument type, stability classification (e.g., NGS A–D), condition/recovery notes, vertical or horizontal order/class, source agency, observation date, or positional accuracy metadata., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_attr (type: esriFieldTypeString, alias: 4. Are your state's Geodetic Control points attributed with additional descriptive information beyond basic coordinates and elevation?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_consistent: Yes, consistently across the dataset], [yes_inconsistent: Yes, but inconsistently applied], [no: No, it is not attributed with additional intelligence], ... 1 more ...)
geodet_cover_guidance (type: esriFieldTypeString, alias: Guidance: Include both passive (monuments) and active (CORS/RTN) control points that are part of your state's authoritative program. Estimates should reflect spatial distribution and accessibility—not just total number of points. If unsure, provide your best approximation., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_pct_coverage (type: esriFieldTypeString, alias: 5. What percentage of your state is currently covered by Geodetic Control points that are part of your authoritative, statewide dataset and tied to the National Spatial Reference System (NSRS)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
geodet_maintained (type: esriFieldTypeString, alias: 6. How is your state's Geodetic Control maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
geodet_update_guidance (type: esriFieldTypeString, alias: Guidance: Consider all aspects of Geodetic Control maintenance, including monument recovery, metadata updates, GNSS data submission, CORS/RTN infrastructure maintenance, and integration with NGS systems., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_update_freq (type: esriFieldTypeString, alias: 7. What is the frequency of updates to your statewide Geodetic Control dataset or network?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [live: Live – Updates occur continuously as new control points, GNSS observations, or CORS/RTN data are submitted or integrated.], [weekly: Weekly], [monthly: Monthly], ... 8 more ...)
geodet_standard_guidance (type: esriFieldTypeString, alias: Guidance: Nationally recognized standards may include NSRS guidelines, NGS Bluebook requirements, NGS Datasheet formats, or specifications tied to CORS, RTN, or GPS on Benchmarks. State-level standards may include agency-specific protocols for survey-grade data., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_standardization (type: esriFieldTypeString, alias: 8. What level of standardization is used in developing your state's Geodetic Control data or network?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
geodet_metadata_guidance (type: esriFieldTypeString, alias: Guidance: Metadata may include monument type, stability classification, positional accuracy, observation date, source agency, or linkage to NSRS/NAD83/NATRF2022. Format may vary, but standardization helps ensure discoverability and usability., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_metadata (type: esriFieldTypeString, alias: 9. Does your state's Geodetic Control dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
geodet_contribute (type: esriFieldTypeString, alias: 10. Does your state contribute Geodetic Control data to the National Spatial Reference System (NSRS) through the National Geodetic Survey (NGS)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [other: Other (Provide explanation below)])
geodet_available (type: esriFieldTypeString, alias: 11. Is your statewide Geodetic Control dataset or network data openly accessible to the public?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
geodet_access_cost (type: esriFieldTypeString, alias: 12. Is access to your state's Geodetic Control data or services free?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free – No cost to view, download, or use data/services], [partially_free: Partially free – Some access is free, but other components (e.g., Data available to view, but not download) require payment], [paid_access_only: No, paid access only – Access requires purchase, subscription, or licensing fee], ... 1 more ...)
geodet_download (type: esriFieldTypeString, alias: 13. Is your statewide Geodetic Control dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
geodet_web_portal (type: esriFieldTypeString, alias: 14. Does your state provide a web portal where users can view Geodetic Control data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
geodet_api (type: esriFieldTypeString, alias: 15. Does your state provide an API or web service to interact with Geodetic Control data programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
geodet_url (type: esriFieldTypeString, alias: 16. Please provide a URL where more information about your state's Geodetic Control data or program can be found., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_characteristics (type: esriFieldTypeString, alias: 17. Which of the following characteristics apply to your state's Geodetic Control program?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
geodet_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
nsrs_modern_guidance (type: esriFieldTypeString, alias: Guidance: NSRS Modernization refers to NGS's nationwide effort to replace the North American Datum of 1983 (NAD83) and the North American Vertical Datum of 1988 (NAVD88) with the new reference systems NATRF2022 and NAPGD2022. These changes will affect all geospatial and engineering workflows that depend on consistent positional or elevation data., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
nsrs_modernization (type: esriFieldTypeString, alias: 18. How is your state preparing for the National Geodetic Survey's (NGS) NSRS Modernization, including the adoption of the new vertical datum (NAPGD2022) and terrestrial reference frame (NATRF2022)? Select the option that best describes your current status, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [no_nsrs_prep: No action taken – Our state has not started preparing for NSRS Modernization.], [nsrs_todo: Planning stage – It's on our "To Do" list; we recognize the need and are beginning to assess requirements.], [nsrs_legisl_ip: Legislation in progress – Legislation is currently being drafted or introduced to support the transition.], ... 4 more ...)
geodet_additional (type: esriFieldTypeString, alias: 19. Use this space to share any additional details about your state's Geodetic Control efforts/program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Geodetic Control program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, 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: Elevation data represents the measured vertical position of the Earth's surface and other landscape or bathymetric features relative to a reference datum, typically sea level. These datasets are foundational to a broad range of applications, including topographic mapping, hydrologic modeling, infrastructure planning, and disaster preparedness., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_forms (type: esriFieldTypeString, alias: Elevation datasets can take various forms, including: raster surfaces (e.g., Digital Elevation Models - DEMs), point clouds (e.g., Light Detection and Ranging (LiDAR), phtogrammetric data), contours (e.g., topographic contour lines), Triangulated Irregular Networks (TINs), and other derived spatial products (e.g., slope, aspect, hillshade, floodplain delineations)., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_what_report (type: esriFieldTypeString, alias: Because Elevation data is often collected through coordinated state and federal initiatives, collaboration across agencies and local governments is essential to maintain consistency, completeness, and usability. Do not report on multiple, non-authoritative datasets that different stakeholders (e.g., local governments or independent agencies) may use separately. Base your response on the single dataset that best represents your state's official, statewide Elevation dataset, regardless of its current state of development. Whether your dataset is non-existent, partially complete, or fully covering your state, report on the dataset your state considers the most authoritative., SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_effort (type: esriFieldTypeString, alias: 1. Is there an effort in your state to develop an authoritative, statewide Elevation dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_full: Yes, a fully developed, authoritative statewide dataset exists and is actively maintained], [yes_incomplete: Yes, a dataset exists, but it is incomplete or inconsistently maintained], [no_dataset_effort: No, there is no effort to develop a statewide dataset (Please go to the next theme)], ... 1 more ...)
elev_program (type: esriFieldTypeString, alias: 2. Does your state have a program in place to support the Elevation dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_formal: Yes, formal], [yes_informal: Yes, informal (Provide explanation below)], [no_program: No, there is no program], ... 1 more ...)
elev_attributed (type: esriFieldTypeString, alias: 3. Is your state's authoritative Elevation dataset attributed with additional intelligence above 3DEP requirements, such as Vegetation Type?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No])
elev_complete (type: esriFieldTypeString, alias: 4. What percentage of your state is currently covered by Elevation data in your authoritative dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [90_100: 90-100%], [80_89: 80-89%], [70_79: 70-79%], ... 7 more ...)
elev_maintained (type: esriFieldTypeString, alias: 5. How is your state's Elevation dataset maintained?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [systematically: Systematically Maintained - The dataset follows a defined process/workflow and update schedule], [inconsistently: Inconsistently Maintained - Updates occur, but there is no formalized process/workflow or schedule], [not_actively: Not Actively Maintained - The dataset is not regularly updated.])
elev_update_freq (type: esriFieldTypeString, alias: 6. What is the frequency of updates for your statewide Elevation dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [5_years_sooner: Every 5 years or sooner], [6_8_years: Every 6-8 years], [9_12_years: Every 9-12 years], ... 4 more ...)
elev_standardization (type: esriFieldTypeString, alias: 7. What level of standardization is used in developing your state's Elevation data?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [national_standard_verif: Published to a nationally recognized standard and verified via stakeholder/in-house QA/QC], [national_standard_no_verif: Published to a nationally recognized standard but not verified via stakeholder/in-house QA/QC], [state_verif: Published to a state-level standard and verified via stakeholder/in-house QA/QC], ... 3 more ...)
elev_metadata (type: esriFieldTypeString, alias: 8. Does your state's Elevation dataset include metadata?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_metadata: Yes - Metadata is documented and maintained], [no_metadata: No - Metadata is not documented and/or maintained for this dataset])
elev_aggregation (type: esriFieldTypeString, alias: 9. Do you contribute your statewide Elevation dataset to a national level aggregation effort/program (e.g. USGS 3DEP)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes: Yes], [no: No], [other: Other (Provide explanation below)])
elev_availability (type: esriFieldTypeString, alias: 10. Is your statewide Elevation dataset fully open to the public, or does it require an account or approval for access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_open: Fully open - Anyone can access the data without an account], [requires_account: Requires account creation - Users must create an account but are automatically granted access], [requires_approval: Requires approval - Users must request access, which is manually reviewed before approval, which is not guaranteed], ... 2 more ...)
elev_access_cost (type: esriFieldTypeString, alias: 11. Is your statewide Elevation dataset free to access?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_free: Yes, fully free - There are no costs associated with viewing or downloading the data], [partially_free: Partially free - Some access is free, but certain data layers, formats, or higher-resolution versions require payment], [paid_access_only: No, paid access only - Access requires a purchase, subscription, or licensing fee], ... 1 more ...)
elev_download (type: esriFieldTypeString, alias: 12. Is your statewide Elevation dataset available for download?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [fully_downloadable: Yes, fully downloadable - Users can download the full dataset], [partially_downloadable: Partially downloadable - Some portions of the dataset are available, but full downloads are restricted], [view_only: No, view-only - The dataset can be accessed online but cannot be downloaded], ... 1 more ...)
elev_web_portal (type: esriFieldTypeString, alias: 13. Does your state provide a web portal where users can view the Elevation dataset?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [interactive_portal: Yes, interactive web portal available - Users can explore, search, and view data online], [limited_portal: Yes, but limited - A web portal exists, but it only provides limited or static views on the data], [no_portal: No, there is no web portal available])
elev_api (type: esriFieldTypeString, alias: 14. Does your state provide an API or web service to interact with the Elevation dataset programmatically?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [yes_api: Yes, API available - The dataset can be accessed programmatically via an API or web service], [no_api: No, API is not available])
elev_url (type: esriFieldTypeString, alias: 15. Please provide a URL where more information about your state's Elevation data or program can be found. This could include a public webpage, data portal, or any other resource where users can access or learn more about the dataset, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_characteristics (type: esriFieldTypeString, alias: 16. Which of the following characteristics apply to your state's Elevation data/program? (select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_steward_name (type: esriFieldTypeString, alias: Agency/entity name (e.g., Department of __, State Geospatial Information Office, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_steward_link (type: esriFieldTypeString, alias: Direct website link, if available:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_funding_source (type: esriFieldTypeString, alias: Where does this funding come from? (If local governments contribute, simply indicate 'cities' and/or 'counties' - no need to list specific names. If state or federal agencies contribute, please specify their sector, such as 9-1-1, emergency management, natural resources, transportation, etc.):, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_budget (type: esriFieldTypeString, alias: What is your current approximate annual budget (in dollars)?:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_single_multi_use (type: esriFieldTypeString, alias: 17. Is your state's Elevation dataset designed for single or multiple uses?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [multiuse: Multiuse: The data has a broad set of attributes and can be used for multiple purposes], [single_use: Single Use: The data is designed for a specific purpose and does not have utility beyond that])
elev_state_use (type: esriFieldTypeString, alias: 18. How does your state use Elevation data? (select all that apply), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
elev_additional (type: esriFieldTypeString, alias: 19. Use this space to share any additional details about your state's Elevation data or program that were not captured elsewhere in this section. Ideas include: further explanations of responses given in previous questions, challenges or barriers your state faces in maintaining or expanding its Elevation program, or any other relevant insights you'd like to provide. Please note - the information shared in this question will be for INTERNAL USE ONLY and will NOT be shared publicly. Please feel free to share candid information., SQL Type: sqlTypeOther, length: 2000, nullable: true, editable: true)