# Please note that changes have been made to this announcement on 1/19/2006. See changes in red on pages 3, 4, and 11.

# 

# 2006 National Spatial Data Infrastructure

# Cooperative Agreement Program

![](media/image1.jpeg){width="3.376388888888889in"
height="3.0284722222222222in"}

**Program Announcement Number 06HQPA0007**

**For Fiscal Year 2006**

**Issue Date: December 8, 2005**

+-----------------------------------------------------------------------+
| **CLOSING DATE & TIME:**                                              |
|                                                                       |
| **February 1, 2006 2:00 p.m. EDT**                                    |
+-----------------------------------------------------------------------+

**TABLE OF CONTENTS**

[Page Number]{.underline}

Description of Funding
Opportunity...................................................... 3

Award
Information.......................................................................\...
4

Applicant
Eligibility\.........................................................................
5

Project
Requirements..............................................................\.........
5

Application and Submission
Information................................................7

Application
Review.....................................................................\....
10

Award Administration
Information..................................................\..... 10

Agency
Contacts............................................................................
11

CAP Category
Information................................................................
12

Category 1: Metadata Training and
Outreach..........................................12

Category 2: Framework Client
Development...........................................17

Category 3: Fifty-States
Initiative........................................................ 21

Category 4: Joint Canadian-US Spatial Data Infrastructure
Project................. 28

Category 5: Geographic Information Integration and
Analysis.......................43

Attachment A - Special Terms and Conditions

Attachment B - General Provisions

Attachment C - Metadata Training & Outreach Project Report Format

Attachment D - Framework Client Development Project Report Format

Attachment E - Fifty State Initiative Project Report Format

Attachment F - Canadian-US Spatial Data Infrastructure Project Report
Format

Attachment G - Geographic Information Integration and Analysis Project
Report Format

Attachment H - Canadian-US Participation Agreement

### For all technical questions about applying through Grants.gov, call the Grants.gov Help Desk at: 1-800-518-GRANTS

**For questions concerning this Program Announcement, call Ms. Desiree
Santa, Grant Specialist, at (703) 648-7382 or via email at
dsanta@usgs.gov.**

**2006 National Spatial Data Infrastructure (NSDI) Cooperative
Agreements Program (CAP)**

**Program Announcement Number 06HQPA0007**

**Introduction and General Information**

**[I. Description of Funding Opportunity]{.underline}**

The purpose of the National Spatial Data Infrastructure (NSDI)
Cooperative Agreements Program (CAP) is to fund innovative projects in
the geospatial data community to build the infrastructure necessary to
effectively discover, access, share, manage, and use digital geographic
data.

The NSDI consists of the technologies, policies, organizations, and
people necessary to promote cost-effective production, and the ready
availability and greater utilization of geospatial data among a variety
of sectors, disciplines, and communities. Specific NSDI areas of
emphasis include: metadata documentation, clearinghouse establishment,
framework development, standards implementation, and geographic
information system (GIS) organizational coordination.

Since 1994, the Federal Geographic Data Committee (FGDC) has funded
projects that advance the NSDI in partnership with the geospatial data
community. The FGDC, now as part of the new National Geospatial Program
Office (NGPO), will continue to support these projects.

## A. Fiscal Year (FY) 2006 NSDI Cooperative Agreements Program

A total of \$1,150,000 in funds is available for the FY 2006 program.
The projects will be funded for one year. Award notification will be
made on or about March 1, 2006. [Project work must commence by September
30, 2006]{.underline} (the end of the 2006 Federal fiscal year). Start
dates on or after October 1, 2006 are not authorized under this
announcement.

**B. Summary of 2006 CAP Funding Categories**

Category 1: ***Metadata Trainer and Outreach Assistance*** provides
assistance to organizations with NSDI expertise knowledge and experience
in assisting other organizations with the training and implementation of
metadata, clearinghouse or web mapping services. Maximum award \$20,000
(50% in-kind match), approximately 5 projects.

Category 2: ***Framework Client Development:*** Developing Software
Clients for Framework Data Services provides assistance to advance the
development of client software to exploit online Framework Data to
support operational needs of an application community. Software will be
distributed freely through an established community as an extension to
an existing geographic information system or as an open-source software
solution that can be integrated into specific decision- support or data
management processes. Maximum award \$75,000 (50% in-kind match),
approximately 3 projects.

Category 3: ***Fifty States Initiative:*** Strategic and Business Plan
Development in Support of the NSDI Future Directions Fifty States
Initiative. Projects will develop and implement statewide strategic and
business plans that will facilitate the coordination of programs,
policies, technologies, and resources that enable the coordination,
collection, documentation, discovery, distribution, exchange and
maintenance of geospatial information in support of the NSDI and the
objectives of the Fifty States Initiative Action Plan. Maximum award
\$50,000 (50% in-kind match), approximately 10 projects.

Category 4: ***Canadian-US Spatial Data Infrastructure Project*** will
support one collaborative project between organizations in the U.S. and
Canada that have an interest in creating, maintaining, and sharing
geospatial data over a common geography. This is a collaborative funding
opportunity sponsored by GeoConnections Canada and the FGDC. U.S lead
award up to \$75,000; Canadian lead award up to \$100,000 CDN, (100%
in-kind match).

Category 5: ***Geographic Information Integration & Analysis*** category
provides assistance to organizations and consortia that maintain, update
and make available data, in collaborating with the National Geospatial
Program Office and *The National Map*. Funds are provided to help new
participants overcome initial impediments to participation and to help
existing participants improve their web services and provide them
through The National Map. Maximum award \$50,000 (100% in-kind match),
approximately 5 projects.

# [II. Award Information]{.underline}

Under the 2006 CAP program, a total of not to exceed \$1,150,000 is
available for funding. Approximately 24 awards are anticipated.

  --------------------------- --------------- ------------ ---------------
  **CAP Funding Categories**  **Award         **In-kind    **Approximate
                              Amount**        Match**      Number of
                                                           Awards**

  1\. Metadata Training &     Up to \$20,000  50%          5
  Outreach                                                 

  2\. Framework Client        Up to \$75,000  50%          3
  Development                                              

  3\. Fifty States Initiative Up to \$50,000  50%          10

  4\. Canadian/US Spatial     Up to \$75,000  100%         1
  Data Infrastructure                                      
  Development                                              

  5\. Geographic Information  Up to \$50,000  100%         5
  Integration Analysis                                     
  --------------------------- --------------- ------------ ---------------

This assistance is provided through a *cooperative agreement*, which is
neither a contract nor a grant. As a cooperative agreement, there will
be *substantial involvement* on the part of the FGDC and the NGPO with
the project organization to promote the objectives of the program,
monitor progress, and agree on milestones and accomplishments for work
performed as part of this agreement. The FGDC will manage all queries,
technical resources, and assistance requests.

Note on Method of Payment: The U. S. Geological Survey (USGS) is using
the Health and Human Services (HHS) Payment Management System (PMS) to
provide electronic invoicing and payment for assistance award
recipients. The Recipient has established or will establish an account
with PMS. With the award of each cooperative agreement, a sub-account
will be set up from which the Recipient can draw down funds

The FGDC will provide, through its website (http://www.fgdc.gov), a wide
range of information on Geospatial One-Stop, metadata, clearinghouse,
and standards, as well as contact information for the FGDC and its
participating organizations at the national, State, and local level. On
its website, the FGDC provides information on the metadata standard, and
metadata trainers, training opportunities, and NSDI news. The FGDC will
attempt to address all queries and assistance requests, including
referral to suitable software solutions.

# [III. Applicant Eligibility]{.underline}

> \(1\) In general, Federal, State, and local government, academia,
> private sector, non-profit and tribal organizations, as well as
> consortia of organizations may apply.
>
> See funding category for specific eligibility information.
>
> \(2\) Applying to more than one category: Organizations may submit
> proposals for more than one category if the applicant meets
> eligibility requirements. [However, a complete and separate
> application package is required for each category
> submission]{.underline}.

**[IV. Project Requirements]{.underline}**

**A. In-Kind Resource Match**

> \(1\) All categories require an in-kind resource match on the part of
> the applicant for the long-term sustainability of project outcomes. An
> in-kind resource match may include:
>
> \- salaries
>
> \- funds
>
> \- equipment dedicated to the project
>
> \- other resources.
>
> \(2\) [The value of geospatial data holdings is not considered
> appropriate for in-kind matches for categories 1, 2, 3 and
> 4]{.underline}. See category 5 for spatial data in-kind match.
>
> \(3\) Match calculation: For example, with an request for an award of
> \$5,000 of Federal assistance, a 50% in-kind match contribution by the
> applicant would be \$2,500 in value for a total of \$7,500 value
> committed to the project (\$5,000 and \$2,500 Federal and applicant,
> respectively).
>
> \(4\) See funding category for specifics in-kind match information.

**B. Reporting and Presentation**

## (1) The following reports will be required from all award recipients:

  ----------------------------------- -----------------------------------
  **Report**                          **Due Dates**

  **Interim Project Report**          6 months after the start of the
                                      project

  **Final Project Report**            On or before 90 working days after
                                      the expiration of the agreement

  Quarterly **SF-272** Federal Cash   On or before 15 working days after
  Transactions Report                 the end of each three-month
                                      performance period

  **SF-269** Financial Status Report  On or before 90 working days after
                                      the expiration of the agreement
  ----------------------------------- -----------------------------------

\(2\) The specific content for the reports can be found in the Report
Format attachments:

Attachment C - Metadata Training & Outreach Project Report Format

Attachment D - Framework Client Development Project Report Format

Attachment E - Fifty State Initiative Project Report Format

Attachment F - Canadian-US Spatial Data Infrastructure Project Report
Format

Attachment G - Geographic Information Integration and Analysis Project
Report Format

\(3\) Financial Reporting Requirements:

Standard Form 272 (SF-272), Federal Cash Transaction Report is required
quarterly for each Payment Management System (PMS) subaccount. Quarterly
reports are due 15 working days after the end of each fiscal quarter and
will be submitted to the contracting officer, unless otherwise
instructed.

Final Financial Status Report (SF-269) recipient will liquidate all
obligations incurred under the award and submit a final SF 269 Financial
Status Report no later than 90 calendar days after the grant/cooperative
agreement completion date. Recipient will promptly return any unused
federal cash advances or will complete a final draw from PMS to obtain
any remaining amounts due.

Forms may be found at: www.whitehouse.gov/omb/grants/grants_forms.html.

### 

### (4) Project Presentation: To spread and promote knowledge of the NSDI, CAP participants are requested to make formal presentation of their activities. Presentation can be at a local, state, regional, national conference or meeting. The applicant is requested, if necessary, to budget sufficient funds to travel to the meeting or conference. An alternative is to publish a paper or article in a professional journal or newsletter.

### **C. Participation in CAP orientation workshop**

The orientation workshop is an opportunity for project leaders, CAP
category leads and others to plan and share information. See specific
category for information on the orientation meeting. Be sure to budget
travel funds and plan for attendance.

  -------------------------------- ---------------------- ----------------
  **Category**                     **Location**           **Date**

  1\. Metadata Training & Outreach Denver Federal Center  Spring, 2006

  2\. Framework Client Development TBD                    Spring, 2006

  3\. Fifty State Initiative       Annapolis, MD          March 19, 2006

  4\. Canadian-US SDI              Proposed by applicant  Spring, 2006

  5\. Geographic Info. Integ. &    Annapolis, MD          March 19, 2006
  Analysis                                                
  -------------------------------- ---------------------- ----------------

# [V. Application and Submission Information]{.underline}

In preparation for using only the [www.grants.gov]{.underline} website
for future electronic submission of all proposals, the USGS will follow
a two-pronged approach for submission of proposals for the FY2006
funding cycle.

[All applicants are required to submit 10 hardcopy
proposals]{.underline}. In addition, the proposals must also be
submitted using the Federal Government\'s [www.grants.gov]{.underline}
website for electronic submission of the same material.

The traditional hard copy method of submission will take precedence over
the electronic submission, therefore, all proposals must be received in
hard copy form by the due date of February 1, 2006.

**A. Hardcopy Application (required)**

[Applicants are required to submit 10 hard copies of the proposal
to:]{.underline}

U.S. Geological Survey

Office of Acquisition and Grants

12201 Sunrise Valley Drive, Mail Stop 205

Reston, VA 20192

Attn: Desiree Santa, Grant Specialist

Hard copies must include the following:

-   Your project narrative.

-   completion of form SF-424 (found at: www.grants.gov)

-   completion of form SF 424a (found at: www.grants.gov)

-   budget breakdown attachment

-   completion of form SF 424b (found at: www.grants.gov)

-   completion of DOI certification forms (found at:
    http://www.usgs.gov/contracts/grants/certs.pdf)

Applications delivered by hand:

1.  An application that is hand delivered shall be taken to the USGS,
    Office of Acquisition and Grants -- Room 6A333, 12202 Sunrise Valley
    Drive, Reston, VA 20192.

2.  The Office of Acquisition and Grants will accept hand delivered
    applications between 8:00am and 4:00pm daily, from December 1, 2005,
    to the closing time of 2:00p.m. EDT, on February 1, 2006, except
    Saturdays, Sundays, and Federal holidays.

3.  An application that is hand delivered will not be accepted by the
    Office of Acquisition and Grants after 2:00p.m. EDT on the closing
    date.

**B. Electronic submissions (required)**

Proposals must also be submitted electronically at http://www.grants.gov
/. Apply, no later than **February 1, 2006 at 2:00 p.m. EDT.** A
proposal received after the closing date and time will not be considered
for award. If it is determined that an application will not be
considered because it was late, the applicant will be so notified
immediately.

Please be aware that the electronic submission system is relatively
complex for first-time users and involves several preliminary steps to
be taken before the proposal information can actually be submitted (go
to [www.grants.gov.]{.underline} and click on the "Get Started" tab for
the steps). [Be advised that it is virtually impossible to begin the
process of electronic submission for the first time if you start just a
few days before the due date]{.underline}. If you are from a university,
contact your Office of Sponsored Programs. They may already have
completed the registration process and should work with you to submit
the application.

Additional instructions and information for electronic submissions:

1\. Electronic applications must be made through the
[www.grants.gov]{.underline} website.

2\. The due date for electronic submission will be the same as that for
the hard copy of the proposals, **February 1, 2006**. The requirements
for the contents of the material submitted electronically are identical
to that required by the hard copy detailed below, except that allowances
for total number of pages can be made for figures.

3\. Your electronic submission will consist of completion of:

-   Your project narrative

-   form SF-424

-   form SF-424a

-   Budget Breakdown Attachment

-   SF-424b Any information that is not contained in the SF-424 forms
    will be pasted together as one file and submitted in the Project
    Narrative Attachment section.

4\. It is recommended that the application narrative be converted to PDF
format for easiest submission. Also, when completing the SF-424 forms,
all blocks in yellow must be filled out or the application submission
will be rejected by grants.gov.

Please arrange your application according to the format provided below.
Following this format ensures that every proposal contains all essential
information and is evaluated equitably.

**C. Proposal Forms**

Begin by downloading the PureEdge Viewer at http://www.grants.gov under
the "Get Started" tab in the upper right corner of the screen. The
PureEdge Viewer will enable applicants to view and complete the
following required forms:

1\. **SF-424 Application for Federal Assistance**

Follow instructions provided with SF-424. In addition please note the
below:

Item 8. Type of Application - **New**

Item 10. Catalog of Federal Domestic Assistance Number - **15.809**.
Title - **NSDI-CAP**

Item 11. Descriptive Title of Applicant\'s Proposal - Please preface
your proposal\'s unique title (e.g. Missouri metadata outreach) with
\"**2006 CAP - Category N**\" where N is the specific funding category
1, 2, 3, 4 or 5.

Item 16. Is Application Subject to Review By State Executive Order 12372
Process?

Check 16. B. - **No**. (CDFA #15.809 is not covered by this order, see
http://12.46.245.173/pls/portal30/CATALOG.EXE_12372_RPT.show)

2\. **SF-424a Budget Information**

Follow instructions provided with SF-424a. In addition please note the
below:

Fill out [Section B - Budget Categories]{.underline}

Column 1 indicate cost category allocation of Federal funds.

Column 2 indicate cost category allocation of applicant in-kind match.

3\. **Budget Breakdown Attachment**

In addition please provide more details than are required under the SF
424A form. Please include the following information:

> \(1\) [Salaries and Wages]{.underline}. List names, positions, and
> rate of compensation. If contract employees are hired, include their
> total time, rate of compensation, job titles, and roles.
>
> \(2\) [Field Expenses]{.underline}. Briefly itemize the estimated
> travel costs (i.e., destination, number of people, number of travel
> days, transportation costs, and other travel costs).
>
> \(3\) [Other Direct Cost Line Items]{.underline}. (This is not an
> inclusive list; add other categories as appropriate.)
>
> \- Supplies. Itemize costs. Software maybe indicated here.
>
> \- Equipment. Itemize name, units and cost.
>
> \- Other contract services.

\(4\) [Total Direct Charges]{.underline}. Totals for items a - h.

\(5\) [Indirect Charges (Overhead)]{.underline}. Show proposed rate and
amount.

4\. **SF-424b Assurances -- Non-Construction Programs**

(The DI-2010 U.S. Department of the Interior Certifications Regarding
Debarment, Suspension and Other Responsibility Matters, Drug-Free
Workplace Requirements and Lobbying are required and are available at
the following site: http://www.usgs.gov/contracts/grants/certs.pdf.
Please complete this form and submit it with the hard copy of your
proposal).

**D. Proposal Narrative**

The applicant\'s proposal narrative is the primary evaluation document
that is scored. For more information see specific category for narrative
content requirements.

# [VI. Application Review]{.underline}

**A. Review and Selection Process**

Applications are considered based on the completeness of documentation,
meeting of stated basic eligibility, and in-kind match and other
category requirements. Specific evaluation factors are identified in the
proposal narrative. Budget information is evaluated for reasonableness
and appropriateness to the CAP program as well as to applicant project
goals.

In addition to the above criteria, [the factors of geographic and
organizational diversity, as well as reaching new organizations and new
geographic regions, will be taken into consideration in selecting
awards.]{.underline}

Proposals are reviewed by a peer group of professionals that are
knowledgeable in the GIS discipline and in the NSDI. Individual
proposals are evaluated and scored. Through peer consensus process,
proposals are ranked for meriting award. The slate of selected proposals
will be submitted to the senior leadership of NGPO and FGDC for final
approval. The senior leadership will consult with the FGDC Coordination
Group in approving and advertising final selections.

**[VII. Award Administration Information]{.underline}**

Award recipients are responsible for managing the day-to-day operations
of the grant/cooperative agreements and sub-award supported activities
to assure compliance with applicable Federal requirements and that
performance goals are being achieved. Recipient monitoring must cover
each program, function, or activity.

# 

# [VIII. Agency Contacts]{.underline}

**A. Grants.gov**

Technical questions concerning the application process at Grants.gov:

Grants.gov Help Desk at:

Phone: 1-800-518-GRANTS

Email: support@grants.gov

**B. Program Announcement**

Applicants are strongly urged to submit questions via email to:

Ms. Desiree Santa, Grant Specialist

U.S. Geological Survey

Grants Branch

12201 Sunrise Valley Drive, MS 205

Reston, VA 20192

Phone: (703) 648-7382

Email: dsanta@usgs.gov

**C. CAP Program**

For technical questions concerning the content, goals, and objectives of
the CAP program categories, please contact:

Ms. Alison Dishman (née Kiernan), CAP Coordinator

Federal Geographic Data Committee (FGDC)

FGDC Interagency Liaison

Email: adishman@fgdc.gov

Phone: 703 648 5086

Fax: 703 648 5089

U.S. Geological Survey

Mail Stop 590

12201 Sunrise Valley Drive

Reston, Virginia 20192

**[IX. 2006 NSDI CAP Category 1: Metadata Trainer and Outreach
Assistance]{.underline}**

**A. Background**

Geospatial information applications have become commonplace in the
management, planning, and use of land resources. Good data management
practices allow datasets created for one project to be used by another
through documentation of critical information of a dataset allowing one
to confidently reuse exiting data. However, due to unawareness or other
limitations, many organizations often do not record the dataset
characteristics, developmental processes, or simply the data's
repository. Dataset characteristics, documented in a structured form to
allow effective information search and discovery, is metadata.
Implementing metadata as a program enables organizations to effectively
manage data resources and to experience cost savings by eliminating
repetitive data creation.

The FGDC calls upon the metadata community, through this CAP, to reach
out to organizations without established metadata programs and share
their expertise in metadata implementation with under or less served
communities.

The FGDC encourages assistance proposals to support rural, local,
regional, and state level metadata training, metadata publishing, and
metadata program implementation.

This category encourages metadata-enabled organizations to extend their
programs to assist other organizations to implement metadata as an
internal data resource management instrument and ultimately share data
resources in support of the NSDI.

**B. Goals**

This category provides funding to organizations skilled in metadata
implementation and willing to assist [other organizations]{.underline}
by providing metadata training, metadata creation assistance, and
metadata program implementation and support. Outcomes from this category
focus on establishing a sustained resource as metadata creators: to
inventory and document data (metadata), support data sharing, and
ultimately participate in the NSDI, and for those managing data
resources, to implement metadata programs in their respective
organizations or agencies.

Recipients in this category are asked to also extend their training
services outside of proposal partners at the recipient's regularly
scheduled and located workshops. Trainers in this category are highly
encouraged to register on the FGDC Metadata Trainer Registry and
contribute to the FGDC's distributed training network. The trainer may
limit their geographic and administrative scope to meet restrictions of
their employer.

Training under this program will contain the FGDC Metadata Core
Curriculum found at: http://www.fgdc.gov/metadata/training.html. The
Core Curriculum provides general topic areas for training, however, the
learning objectives for the core content are requirements for metadata
creator and manager workshops supported under this program.

**C. Project Results**

Projects results and outcomes sought under this category include:

\(1\) Individuals and organizations trained and competent in creating
compliant metadata.

\(2\) Metadata files created for other organizations.

\(3\) Resulting metadata can be discovered and harvestable through

\(a\) The Geospatial One-Stop Portal at http://www.GeoData.gov.

\(b\) Registered Z39.50 Clearinghouse server.

> \(c\) Open Archives Initiative Protocol for Metadata Harvesting
> (OAI-PMH) provider software.

\(d\) FGDC Browse-enabled Web Directory, where metadata is in XML.

\(4\) Establishment of data warehousing for Web mapping service in GOS
Portal.

\(5\) Establishment of formal or informal organizational relationships
to sustain metadata activities beyond performance period.

\(6\) Trainers are registered at the FGDC Metadata Trainer Registry to
provide for greater metadata training opportunities.

\(7\) All workshops are posted to the FGDC Calendar:
http://fgdc.gov/calendar

See Attachment C \"Metadata Training and Outreach Project Report
Format\" for additional project documentation.

**D. Applicant Eligibility**

# Federal, State and local government, academia, private sector, non-profit, and tribal organizations, as well as consortia of organizations, may apply. 

Proposals sought under this category are by organizations skilled and
resourceful in implementing applicable standards.

# E. Funded Activities

\(1\) Funded tasks and items providing training and outreach to other
organizations include:

\(a\) Training sessions (travel, facilities, reproduction costs,
equipment, etc)

\(b\) Clearinghouse service for resulting metadata

\(c\) Labor costs to create and serve metadata for other organizations

\(d\) Travel to provide metadata training and outreach

\(2\) Participation in CAP Orientation Meeting

Applicants are requested to budget sufficient travel funds
(approximately \$1,000) for the participation of one individual at the
CAP orientation workshop to be held in Denver, Spring 2006.

### (3) Project Presentation to spread and promote knowledge of the NSDI, 2006 CAP participants are requested to make formal presentations of their activities. Presentation can be at a local, state, regional, national conference or meeting. The applicant is requested, if necessary, to budget sufficient funds to travel to the meeting or conference. An alternative is to publish a paper or article in a professional journal or newsletter.

**F.** **Funding and In-Kind Match**

\(1\) Federal assistance

Up to \$20,000 is available for funding under this category.

\(2\) In-Kind Resource Match

A minimum [50% match]{.underline} is required. This may include
salaries, funds, and equipment dedicated to the project as well as other
resources. See Section IV. A. (3) for in-match calculation.

**G. Partnership and Collaboration Requirement**

Partnerships with other organizations to leverage resources are
encouraged but not required under this category. Partnerships, both
formal and informal among organizations to leverage limited geospatial
data resources, are seen as primary building blocks for the NSDI.

Those proposals demonstrating support and/or collaboration with state or
regional spatial data strategic plans or councils are sought under this
announcement.

**H. Applicable Standards**

Projects must be in compliance, as applicable, with geographic
information standards developed and endorsed by standard-setting bodies
including the FGDC, ISO, and the OpenGIS Consortium. These standards
include:

> \(1\) FGDC Content Standard for Digital Geospatial Metadata, Version 2
> (CSDGM), FGDC-STD-001-1998 or when available the ISO Metadata Standard
> 19115 using draft ISO Technical Specification 19139.
>
> \(2\) Metadata Service Guidelines: Metadata must be posted to one of
> the following options and harvestable through
>
> \(a\) the Geospatial One-Stop Portal at http://www.GeoData.gov.
>
> \(b\) registered Z39.50 Clearinghouse server.
>
> \(c\) Open Archives Initiative Protocol for Metadata Harvesting
> (OAI-PMH) provider software.

\(d\) FGDC Browse-enabled Web Directory, where metadata is in XML.

**I. Project Resources**

The FGDC Metadata website (http://www.fgdc.gov/metadata/metadata.html)
provides links to resources assisting workshop development at various
content levels and durations. Using the FGDC Metadata Core Curriculum
enables course development that meets FGDC training standards. The FGDC
will provide initial tutorial and referral assistance as well as
training at the FGDC CAP kick-off workshop.

The FGDC will assist in matching training requests and trainer provider
geographically and by data theme.

**J. Reporting**

\(1\) An interim and final project report is required.

(a). See Section IV. B for report submission schedule.

> (b). See Attachment C: Metadata Training and Outreach Project Report
> Format for content.

\(2\) Financial report (see Section IV.B.).

**K. Application Narrative**

The project narrative is the primary document that will be evaluated and
scored by the review panel. Proposal Summary for each awarded proposal
will be linked from the FGDC website. Total point value of 100 points
possible. [Please limit to 5 pages]{.underline} (not including letters
of support, tables, maps, and diagrams):

\(0\) [Proposal Summary]{.underline}: Please list the following items if
appropriate

\(a\) Applicant organization (name, office/branch, street address, city,
state, zip)

\(b\) Collaborating organizations (organization, address)

\(c\) Name of trainer or trainer's organization.

\(d\) Organization Internet address

\(e\) Registered Clearinghouse node or Web folder IP address

\(f\) Key project contact (name, telephone, fax, email)

\(g\) Other contact personnel (name, telephone, fax, email)

\(h\) Geographic scope or area

\(i\) Previous CAP participation (awarded or submitted but not awarded).

\(1\) [Project Scope]{.underline} -- Project Description (25 points)

Describe project, its steps, and partners/participants. Describe how the
project contributes to the NSDI, and conforms to appropriate standards.
List organizations or target organizations/communities served in the
project.

\(2\) [Technical approach]{.underline} (25 points)

Outline the steps, methodologies and resources to be utilized in
implementing the project.

This includes facility type, equipment and supplies supporting the
training. Applications will be evaluated on the degree to which
comprehend the tasks and procedures necessary to accomplish project
objectives. Indicate the training approach: lecture, lecture with
exercises, or lecture with metadata creation tool. Indicate all pre and
post-workshop activities performed to measure learning, if any. Indicate
if course and instructor evaluations are conducted. Include statement
regarding adoption of FGDC Metadata Core Curriculum.

\(3\) [Project Experience]{.underline} (25 points)

Describe experience, special qualifications and skills possessed
necessary for performance of the project. If applicant is a previous
NSDI CAP participant please provide information describing previous
effort and accomplishments. Identify metadata trainer resource.

\(4\) [Commitment to Effort]{.underline} (25 points)

Describe the extent to which project results will continue or be
sustained after the performance period. Applicants are sought that
demonstrate the project is participating in or supporting state or
regional geospatial infrastructure strategies and plans. Memoranda of
Understanding and/or letters of commitment should be attached. State,
County, and Local applicants must include a letter of support from the
State GIS Coordinator or similar.

**[X. 2006 NSDI CAP Category 2: Framework Client
Development:]{.underline} Creating sustainable client applications for
Framework data**

**A. Background**

Framework data services provide live access to geographic base data as
Open Geospatial Consortium (OGC) Web Feature Services. CAP awards in
2004 and 2005 prototyped the development of Framework data services and
the data structures for transmission of Framework data. To encourage
broader access to Framework feature data, sustainable client
applications are required to demonstrate and operationalize the access
to Framework data for decision-making in multiple application domains.

# B. Project Goals

This category is intended to stimulate the development and deployment of
sustainable software applications that access Framework data in support
of popular analytical or decision-making processes within multiple
communities. An underlying goal is to increase visibility, usability,
and regular access to established Framework data services.

**C. Project Results**

Each award in this category will yield freely-available client software.

This client software may be standalone or extensions to existing
software,

and supports specific requirements of an identified community to assist
in problem solving, analysis, or other popular tasks.

Software should be modular in nature to support integration with
existing business processes and be flexible to accommodate new
situations.

Software must support access to an OGC Web Feature Service specification
Version 1.1 with the published Framework GML Application Schemas managed
by the FGDC as part of the draft ANSI Framework Data Content Standard.

Projects are encouraged to provide suggested enhancements to the
Framework data standard and services for greater usability. Software
will be made freely available to the public.

Software will be maintained by the awardee.

**D. Applicant Eligibility**

To be eligible, applicant teams [must include]{.underline} a
representative of :

1\. A **recognized discipline community,** and

2\. A **software developer partner** with a documented history of
software development and maintenance.

3\. Applicant teams must have expertise in multiple operational NSDI
activities

(e.g. FGDC metadata development, clearinghouse operations, OGC Web
Services deployment).

4\. An applicant team member (organization or company) may not
participate in more than one award in this year\'s category 2 projects.

**E. Funding and In-Kind Match**

1\. Federal assistance up to \$75,000 per award

2\. Applicant in-kind resource match (50% in-kind match)

Applicant must document the amount and type of in-kind resource that
will be contributed to the fulfillment of the project goals.

Contribution of matching personnel hours or funding, supplied
development hardware and software, or other in-kind resources will be
considered.

[The value of data will not be considered as match funding.]{.underline}

**F. Federally reimbursable project activities or items:**

1\. These activities and cost items maybe reimbursed by the Federal
awarded funds. These include personnel salary, contractor support,
software development licenses, required travel, communications, and
other office-related costs required by the problem-scoping and software
design process.

2\. Equipment: [No funds under this award may be allocated for equipment
purchase or leasing]{.underline}.

3\. Software used for the purpose of application development and
deployment may be acquired through this award.

4\. Data: [No data collection activities or data purchases maybe
reimbursed by awarded funds.]{.underline}

**G. Partnership and Collaboration Requirements**

Project partnerships that represent professional discipline interests of
national or international scope are required for success.

Project applicants must identify a problem domain for which a common
client software solution is warranted and will be popular.

Alignment with professional organizations or societies is sought.

**H. Applicable Standards**

1\. Content Standard for Digital Geospatial Metadata (CSDGM) Version 2.0
(1998) will be required for the documentation of application software
written

2\. Open Geospatial Consortium Web Feature Service specification Version
1.1 will be required and used by Framework data services and client
applications

3\. Open Geospatial Consortium Web Coverage Service specification
version 1.0 may be required if elevation data are proposed

4\. Draft ANSI/INCITS L1 Framework Data Content Standards will be used
to define the data content supplied by the services

5\. Open Geospatial Consortium Geography Markup Language, "Simple
Features GML" Profile will be used, where possible, for the encoding of
Framework data, otherwise full GML Version 3.1.1 or later will be used.

**I. Category Lead technical contact**, Douglas Nebert, FGDC
Clearinghouse Coordinator

**J. FGDC Provided Project Resources**

Regular teleconferences will be scheduled to provide an exchange of
information regarding Framework data access applications. Relevant
standards and specifications documents and revisions will be shared with
successful applicants.

**K. Reporting**

1\. Interim and final report

> a\. Content and format see Attachment D
>
> b\. Submission schedule see Section IV. B. Reporting and Presentation.

2\. Financial reporting see Section IV. B.

**L. Proposal Narrative**

The project narrative is the primary document that will be evaluated and
scored by the review panel. Proposal Summary for each awarded proposal
will be linked from the FGDC website. Total point value of 100 points
possible. [Please limit to 5 pages]{.underline} (not including letters
of support, tables, maps, and diagrams).

\(0\) Proposal summary: Please list the following items as appropriate

\(a\) Applicant organization (name, office/branch, street address, city,
state, zip)

\(b\) Collaborating organizations (organization, address)

\(c\) Organization Internet address

\(d\) Registered Clearinghouse node

\(e\) Key project contact (name, telephone, fax, email)

\(f\) Other contact personnel (name, telephone, fax, email)

\(g\) Geographic and/or disciplinary scope or area

\(h\) Previous CAP participation (awarded or submitted but not awarded).

## (1) [NSDI Related Experience]{.underline} (20 points)

Provide documentation of and references to previous activities in
support of NSDI. This may include organizational coordination, previous
CAP awards, metadata development, participation in the NSDI
Clearinghouse, geodata.gov, or establishment of Framework Data Services.
Identify any member participation in the development or registered
review of the INCITS Framework Data Content Standards.

## (2[) Project Scope and Benefits]{.underline} (20 points)

Identify the scope and elements of a repeatable task or problem to be
solved using Web Feature Service access to Framework data as feature
services through a usage scenario or use case. Explain the Framework
data (features and properties) required by this scenario and how they
are used. Identify the discipline scope of this scenario; examples
include emergency response, permit processing, dispatch, environmental
modeling, data update, data quality assessment. Identify the type and
number of users who would benefit from a client application that
addresses this problem space. Provide evidence of significant
participation and support for this approach by representatives of
professional organizations or user groups. Proposals that meet an
identified need using Framework data and supply a solution that will be
used by hundreds or thousands of individuals nationwide will receive a
high score. Solutions that can be generalized and can be adapted to
additional uses will receive better scores.

## (3) [Software development expertise]{.underline} (40 points)

Provide professional qualifications of the software development partner
in this proposal. Identify the scope of involvement of the software
developer in achieving the outcomes of this award. Provide evidence of
software development and maintenance, business partnerships, and
sustainability of prior projects. Software partners that show
qualifications and a significant commitment to implement and maintain
this software will receive a higher score for potential sustainability.

## (4) [Application development]{.underline} (20 points)

Describe the deliverable software, its functionality, interfaces,
adaptability, and dependencies on other software or operating systems.
Document the support for the required standards and specifications.
Identify plans for promotion, integration, support, and distribution of
this software. Software may be licensed but must be made available
without cost to the public as a standalone product or as an extension to
an existing product. Software solutions that are easily and widely
deployed will receive the highest scores for availability and promoting
access to Framework data.

**[XI. 2006 NSDI CAP Category 3: Fifty States Initiative:]{.underline}
Strategic and Business Plan Development in Support of the NSDI Future
Directions Fifty States Initiative**

**A. Background**

The National Spatial Data Infrastructure (NSDI) Future Directions
Initiative recognizes that the NSDI cannot be maintained and enhanced by
a single organization. A well-coordinated, concerted effort inclusive of
the private sector, utilities, academia and all levels of government is
needed to leverage resources, minimize redundancies and collaboratively
solve problems to achieve the NSDI vision. The NSDI vision assures that
spatial data from multiple sources are available and easily integrated
to enhance the understanding of our physical and cultural world.
Partnerships are essential to realizing the NSDI Vision.

One of the objectives of the Future Directions Action Plan is the *Fifty
States and Equivalent Entities Involved and Contributing to the NSDI
Plan* (Fifty States Initiative). It recognizes that it will not be
possible to build the NSDI without taking advantage of the day-to-day
efforts of state and local governments. This will require effective
statewide coordination mechanisms that routinely contribute to the
development of the NSDI. The Fifty States Initiative, endorsed by the
Steering Committee of the Federal Geographic Data Committee, will
advance the implementation of effective statewide coordination councils
and the development of geospatial strategic and business plans.

This category specifically supports activities that promote the
development of statewide strategic and business plans for the
establishment of effective, all-inclusive statewide coordination
councils/offices and the related activities necessary to ensure
meaningful contributions to the NSDI.

**B. Goal**

The goal for projects in this category is the development and/or
implementation of statewide strategic and business plans that facilitate
the coordination of programs, policies, technologies, and resources that
enable the coordination, collection, documentation, discovery,
distribution, exchange, and maintenance of geospatial information in
support of the NSDI and the objectives of the Fifty States Initiative
Action Plan.

**C. Project Outcomes**

> **1.** Strategic Planning
>
> • Creating statewide councils/offices/organizations
>
> • Strengthening the effectiveness of existing councils/offices
>
> • Improving coordination of, participation in, and contribution to
> statewide geospatial information activities among state, regional,
> local, tribal, federal, academic, utility, and private sector
> stakeholders
>
> • Gaining recognition from State level governmental and legislative
> entities
>
> • Improving geospatial data discovery, access, and use
>
> • Increasing participation in national geospatial data programs
>
> • Working toward establishing sustainable funding mechanisms
>
> **2.** Business Plan Development
>
> • Assessing needs
>
> • Establishing priorities
>
> • Adopting tools for identifying the status of data development
>
> • Identifying opportunities for data partnerships
>
> • Identifying funding resources and mechanisms required for geospatial
> data coordination, collection, and maintenance.
>
> • Addressing enterprise architecture, the National Geospatial
> Strategy, and open interoperability standards
>
> • Incorporating measures for evaluating return on investments

**D. Project Activities**

> I. Development and/or implementation of a strategic plan that
> addresses how to bring all of the stakeholder groups together into a
> functional governing body that serves as a Statewide Coordination
> Council with the following characteristics:
>
> • A mechanism exists for broad representation and inclusion in
> decision-making of user communities, including Federal, state, county,
> municipal and tribal governments; private sector GIS users and
> vendors; academic sector; non-profit organizations; utilities; and the
> general public.
>
> • The relationship of the Coordination Council to national geospatial
> initiatives such as Geospatial One Stop and *The National Map*.
>
> • A proposed formal authorization process to establish the Statewide
> Council with appropriate bylaws.
>
> • The relationship and linkage with the nine coordination criteria
> (see below) to feed consensus based decision-making into official
> statewide initiatives is defined.
>
> • Adequate funding and a budget are identified (or cost sharing
> mechanisms are established) to support and enable the operation.
>
> • A commitment is made to implementing appropriate OGC, FGDC, ANSI and
> ISO standards to ensure an "open" environment exists.
>
> II\. Development and/or implementation of a statewide Business Plan
> that addresses key coordination criteria, including:
>
> • The absence, presence, or planned development of a geospatial
> enterprise architecture.
>
> • Identification of the status of existing framework and critical
> infrastructure data, future data production plans, and opportunities
> for data production partnerships.
>
> • Establishing data sharing agreements with local, state, tribal and
> federal agencies unless they routinely provide data in the public
> domain.
>
> • Publishing lists of local, state, tribal and federal data
> stewards/integrators for each of the framework layers.
>
> • Posting local, state, and tribal framework data to the national
> clearinghouse or otherwise making them available through OGC
> interfaces.
>
> • Assisting local, state, and tribal data producers in creating
> metadata for data holdings and posting it to the GOS Portal.
>
> • Maintaining a functioning clearinghouse or appropriate inventory
> tool that is available to all interested sectors in a state and is
> available for metadata harvesting by the GOS portal.
>
> • Enabling local, state, and tribal organizations to participate in
> *The National Map* and the Geospatial One Stop Portal program*.*
>
> • Promoting the adoption and incorporation of appropriate OGC, FGDC,
> ANSI and ISO standards and interoperable practices among local, state
> and tribal agencies.

The Nine Coordination Criteria include the following:

> • A full-time, paid coordinator position is designated and has the
> authority to implement the state's business and strategic plans.
>
> Explanation: Many states have created one or more full time positions
> to oversee coordination of geospatial technologies. These individuals
> are responsible for implementing the state's business plan and are
> typically assigned to the Governor's Office, Chief Information
> Officer, Budget Department, or the Technology Office. In some states,
> these duties fall on a volunteer and in others, no one is willing to
> assume this role. It is presumed that having a full-time paid
> individual is advantageous and that a significant portion of their
> energy is channeled into on-going statewide coordination council
> activities.
>
> • A clearly defined authority exists for statewide coordination of
> geospatial information technologies and data production.
>
> Explanation: A responsible individual or group has been designated in
> many states through executive orders, budget authorizations, or
> legislation. These individuals, or groups, are usually better able to
> deal with difficult coordination issues since they are empowered to
> perform this function. In other cases, "all volunteer" efforts are
> very effective at coordinating statewide activities through consensus
> building. In some instances, these groups are recognized as a "clearly
> defined authority" although they have no specific powers.
>
> • The statewide coordination office has a formal relationship with the
> state's Chief Information Officer (or similar office).
>
> Explanation: Geospatial technologies are clearly a component of any
> state's information technology architecture, but they are not always
> viewed as such by "old school" IT leaders. A close relationship with
> the state CIO is essential to move major geospatial technology
> initiatives forward.
>
> • A champion (politician or executive decision-maker) is aware and
> involved in the process of coordination.
>
> Explanation: A visionary political champion who understands geospatial
> technologies is a valuable ally that can help obtain recognition and
> funding to support new initiatives. Without a strong political
> champion, new initiatives often fail.
>
> • Responsibilities for developing the National Spatial Data
> Infrastructure and a State Clearinghouse are assigned.
>
> Explanation: The responsibility for the component pieces of the NSDI
> should be assigned to appropriate staff and agencies to ensure that
> stewards are identified, and to prevent duplication of effort.
> Assignment of responsibilities should happen in advance of actual need
> to ensure that the appropriate activities are appropriately planned
> and incorporated into the state's business plan.
>
> • The ability exists to work and coordinate with local governments,
> academia, and the private sector.
>
> Explanation: Each state must have the capability to routinely meet and
> coordinate with all other sectors. Safeguards should be developed to
> ensure that the needs of other sectors can be incorporated through
> consensus building activities.
>
> • Sustainable funding sources exist to meet projected needs.
>
> Explanation: Sustainable funding is the foundation of effective
> partnerships. Data production tends to be the highest component cost
> for implementation of geospatial technologies and most users have
> requirements for continuous updating of data layers that requires a
> steady fund source. Effective consortia can only be established when
> each of the players brings something to the partnership and
> non-lapsing funds help stabilize partnerships.
>
> • Coordinators have the authority to enter into contracts and become
> capable of receiving and expending funds.
>
> Explanation: To be effective, individual state GIS coordinators or the
> agencies identified as the stewards for the component pieces of the
> NSDI must be able to readily contract for software, systems
> integration, training, and data production costs. Often partnerships
> can be "brokered" to capture end-of-year funds when contracting
> mechanisms are already in place.
>
> • The Federal government works through the statewide coordinating
> authority.
>
> Explanation: It is essential that Federal agencies use statewide GIS
> Coordination offices and councils as a type of "clearinghouse" to make
> sure that grant opportunities are being used wisely to implement the
> business plans of the states. Going through the coordination offices
> and councils will also help to minimize duplications of effort.

**E. Applicant Eligibility**

Federal, state, local, and tribal governments, academia, non
governmental organizations, utilities, and the private sector may apply
for awards in this category. Existing statewide coordinating councils
and/or other entities involved in the development of statewide
geospatial strategic and business plans may apply for an award in this
category. Coordinated multi-sector responses are strongly encouraged.

**F. Funding Amount and In-Kind Match**

1\. Federal Assistance

Up to \$50,000 will be obligated to individual projects under this
category.

2\. Applicant In-Kind Resource Match

A minimum 50% match is required. This may include salaries, funds, and
equipment dedicated to the project as well as other resources (the value
of actual geospatial data holdings are not considered appropriate for
in-kind matches). See Section IV. A. (3) for in-kind match calculation.

**G. Funded Activities**

1\. Funded activities include:

> a\. Fees for consultants, facilitators or recorders
>
> b\. Salary for a statewide coordinator
>
> c\. Salary for statewide coordination staff
>
> d\. Publications
>
> e\. Workshops
>
> f\. Training

2\. In addition, applicants are requested to budget sufficient travel
funds (approximately \$1,000) for participation by one individual at the
orientation workshop be held in conjunction with a Strategic and
Business Plan workshop at the NSGIC Mid-year Meeting in Annapolis,
Maryland on Sunday, March 19, 2006.

**H. Reporting**

1\. An interim and final project report is required.

(a). See Section IV. B for report submission schedule.

> (b). For content see Attachment E: Geographic Information Coordination
> Project
>
> Report Format.
>
> (c). Include a copy of the strategic and/or business plans as an
> attachment to the final report.

2\. Financial reporting (see Section IV. B.).

**I. Application Narrative**

The project narrative is the primary document that will be evaluated and
scored by the review panel. The Proposal Summary for each awarded
proposal will be linked from the FGDC website. A total point value of
100 points is possible. Please limit narrative to 5 pages (not including
letters of support, tables, maps, and diagrams). Applicants are
encouraged to work with their State's USGS Geospatial Liaisons to
develop proposals. For a listing of Liaisons please see
http://geography.usgs.gov/www/partners/crreps.html

(0). [Proposal Summary]{.underline}. Please list the following items, as
appropriate:

\(a\) Applicant organization

\(b\) Collaborating organizations (include letters of
support/recommendation in appendix)

\(c\) Organization internet address

\(d\) Relevant National Digital Geospatial Clearinghouse node address
(if any)

\(e\) Key project contact (name, telephone, email)

\(f\) Other key contact personnel (name, telephone, email)

\(g\) Geographic scope

\(h\) Previous CAP participation (awarded or submitted but not awarded)

\(i\) Concise description of the project (limit to 200 words).

\(1\) [Project Scope]{.underline} (55 points)

a\) Describe the existing geospatial coordination activities in your
state, including the existing coordination groups, the nature and the
currency of their strategic and business plans, and an explanation as to
why they do not meet the suggested criteria proposed in this document.

b\) Describe the proposed strategic and business plan development, how
you expect to implement them in your state, and what key problem areas
can be overcome by instituting a new planning process. What is it about
your proposed approach that will help ensure its success?

\(2\) [Skills and Capabilities]{.underline} (15 points)

Describe the experience, special qualifications and skills possessed
that are necessary for performance of the project. If the applicant is a
previous NSDI CAP participant please provide information describing
previous effort(s) and accomplishments.

\(3\) [Commitment to Effort]{.underline} (15 points)

Describe the organization's outlook for a sustainable operation and the
extent to which project results will continue or be sustained after the
performance period. Applicants are sought that demonstrate commitment to
supporting statewide geospatial infrastructure strategies in support of
the NSDI Fifty States Initiative. Identify the partner
organizations/participants involved and their roles and commitments to
the project. Memoranda of Understanding and/or letters of commitment
should be attached.

\(4\) [Organizational and Managerial Capacity]{.underline} (15 points)

Describe the management plan for the activity, including the nature of
the applicant's organization and its formally documented relationships
with other participants in the project. Describe the plan for project
implementation. Address your capacity to effectively accomplish the
funded activities. Describe the applicant's ability and experience in
managing key aspects of projects such as the one proposed, including the
functions of geospatial data coordination, executive guidance;
geospatial data maintenance and integration, access, and management;
financial and other resource management. Identify how the outcomes of
the project fit the business plans and benefits anticipated by the
partners or customers of the applicant.

**[XII. 2006 NSDI CAP Category 4: Joint Canadian and U.S. Spatial Data
Infrastructure Project]{.underline}**

### **A. Scope**

> (1). General Description: Applications of digital geospatial data vary
> greatly, but users have a recurring need for access to themes of data.
> In the spirit of information exchange, a geospatial data community can
> work together to produce, maintain and share commonly needed data for
> national, regional, state, provincial/territorial and local analysis.
> Within the geospatial data community, multi-agency, and multi-sector
> partnerships are being established in local and regional areas to
> collaboratively leverage resources and funding, and coordinate data
> collection, utilization, access, and sharing. Spatial data
> infrastructures build on these activities by identifying basic
> information content, and the technical, operational, and business
> contexts by which a distributed, collaborative data collection and
> maintenance effort would operate.
>
> Connected distributed data sets are important to the geospatial data
> community. The Federal Geographic Data Committee (FGDC) Secretariat
> and GeoConnections are co-sponsoring a joint project (via a Memorandum
> of Understanding) for the development of regional applications that
> increase the access and use of distributed geospatial data content.
> This regional application will cover a continuous piece of geography
> including both Canada and the U.S., and will enhance further
> understanding of the complexities, challenges, and effort required in
> utilizing spatial data infrastructures and distributed data to address
> a common issue between the two countries.
>
> This category advances the capacity of communities to create and use
> geospatial data. Projects funded under these categories will deal with
> a common priority issue that results in increased information sharing
> while making available new content and services. The projects will
> also demonstrate collaborative approaches and decision‑support in
> solving community issues utilizing distributed data (thematic and
> framework) and through the use or refinement of existing FGDC,
> GeoConnections, and International standards. Projects will establish a
> collaborative process that provides different kinds of organizations
> and disciplines with the ability to integrate and share geospatial
> data.
>
> (2). In the U.S. applications are open to Federal, state, and local
> governments, commercial, academic, non-profit, and Native American
> Tribal organizations. In Canada applications are open to Canadian
> organizations (private, commercial, academic and nonprofit), federal
> (special funding case please refer to section D item 2) and
> provincial/territorial government agencies, local communities and
> Aboriginal (First Nations, Métis and Inuit).

(3). The FGDC will fund under category 4 cost shared project to
demonstrate the ability to address sound community decision-making
through the collaborative use, maintenance and sharing of geospatial
data. One project will be funded under this year's CAP.

> (4). Category 4 proposals must demonstrate collaboration between
> organizations in the U.S. and Canada.
>
> (3**). Please note that under this FY 2006 CAP, applicant
> organizations may submit [only one proposal]{.underline} package.
> Previous Joint U.S. and Canadian Demonstration Project award
> recipients are not eligible.**

### **B. References**

Applicants can find information on spatial data infrastructures through
the GeoConnections and FGDC web sites (http://www.geoconnections.org/
and In particular, applicants should familiarize themselves with the
following reference sources:

(1). **U.S. Sources:**

\- Federal Geographic Data Committee web site http://www.fgdc.gov/

> \- *Framework Introduction and Guide*, FGDC 1997
> http://www.fgdc.gov/framework/frameworkintroguide/
>
> \- *Development of a National Geospatial Data Framework*, FGDC 1995
> http://www.fgdc.gov/framework/framdev.html
>
> (2). Canadian Sources: All the following sources of information can be
> found through the GeoConnections web site at
> http://www.geoconnections.org (in the opportunities section containing
> this announcement).
>
> *- CGDI Target Vision and Implementation Plan; Vision: Better
> knowledge for better decisions,* Sep. 2005
>
> \- *CGDI Target Vision and Implementation Plan; Architecture:
> Architecture Description Version 2.0,* Sep. 2005
>
> \- *GeoBase (http://www.geobase.ca/)*
>
> \- *GeoConnections Discovery Portal* (*http://geodiscover.cgdi.ca)*
>
> \- *A Developers' Guide to the CGDI: Developing and publishing
> geographic information, data and associated services,* Feb. 2004
>
> \- *CGDI online training*, Aug. 2004
>
> *- 4 white papers*
>
> *- CGDI Framework Data Definition,* June 2001
>
> *- The Atlas of Canada (* *http://atlas.gc.ca/site/index.html)*

**C. Project Goal**

The goal of this project is to stimulate cross-border cooperation over a
geographic area through the use of connected, distributed data and
services. This project will test methods for building regional spatial
data infrastructure applications and increasing the sharing of
distributed geospatial data, suggest topics for future research and
development, and provide guidance on policies and practices for the
establishment of an operational spatial data infrastructure between the
U.S and Canada.

Possible projects that may benefit from cross-border regional
cooperation will be within the following themes:

\- Environment and Sustainable Development: Polar Regions;

\- Public Safety: natural hazards forecasting/warning systems;

\- Public Health: pandemic outbreaks/disease surveillance; and,

\- Aboriginal and Native American peoples: land and resource management
or community planning.

This project should advance the capacity of a U.S./Canadian community to
produce and utilize connected, distributed, geospatial data.
Furthermore, the project should demonstrate collaborative approaches in
solving community issues utilizing distributed data. Participation by
different kinds of organizations and disciplines is important, as is the
ability to integrate and share connected distributed data among these
different users.

### **D. Funding for Program: US/Canadian Support**

> (1). **U.S. funding support** for the project will be provided by the
> U.S. Geological Survey on behalf of the Federal Geographic Data
> Committee (FGDC). **A total of \$75,000.00** (US Dollars) is
> available. This funding will be given to the lead US organization, and
> the award document authorizing the funds will be separate from the
> Canadian agreement authorizing Canadian funds.

(2). **Canadian funding support** for the project will be provided by
the Natural Resources Canada, GeoConnections. In Canada, a contribution
agreement is used to financially support the cost share project. For
federal departments, an interdepartmental fund transfer will be used
instead of a contribution agreement. **A total of \$100,000.00**
(Canadian Dollars) is available. This funding will be made to the lead
Canadian organization and will be awarded by authorized representatives
of Canada.

(3). Depending on the proposal merit, one joint project will be funded
with each government issuing its own award document. This estimate does
not bind the U.S. or Canada to a specified number of awards or to the
amount of any award unless that amount is otherwise specified by statute
or regulation. Payment will be made based on project Milestones. The
final payment will represent at least 10% of the FGDC or GeoConnections
share.

(4.) Due to the joint bi-national scope of this project, the lead US
organization will bear responsibility to meet USGS requirements and the
lead Canadian organization will bear responsibility to meet
GeoConnections requirements. Thus, two cost proposals are required for
each Canadian/U.S. proposal, one for U.S organization and one for the
Canadian organization.

### **E. Participants Cost-Share** 

(1). The [**U.S. applicants** must provide 100% in-kind matching
funds]{.underline} in U.S. dollars from funds other than those received
under this project from the U.S. Geological Survey.

> (2). The [**Canadian applicants** must provide 100% in-kind matching
> funds]{.underline} in Canadian dollars from funds other than those
> received under this project from the GeoConnections Program.

(3). These funds may be in the form of cash and/or in-kind contributions
(materials, services, or personnel provided to the proposed project).
[Existing in-place equipment (unless primarily or exclusively used for
the project) is not to be considered acceptable as an in-kind
contribution. No geospatial data sets, whether existing or to be
acquired, are considered acceptable as an in-kind contribution. Profit
must not be included in the in-kind contribution.]{.underline}

#### F. Disbursement of Funding Support

[Applicants must demonstrate that both a lead U.S. organization or
agency and a lead Canadian organization or agency are involved in the
project.]{.underline} Furthermore, each country's lead
organization/agency is required to collaborate with another organization
or agency in its respective country. Thus each application will have a
minimum of four organizations or agencies--two from Canada and two from
the U.S. Funding will be provided only to the lead organization in each
country. They in turn, have the responsibility of dispensing the
appropriate funds to their collaborating organization(s). Canadian funds
are to be spent by Canadian participants and U.S. funds are to be spent
by U.S. participants.

### **G. Eligibility Requirements**

(1). Qualified applicants from among American and Canadian organizations
include Federal, State, Provincial/Territorial and local government
agencies, educational or academic institutions, private
sector/commercial firms, utilities, private foundations, not-for-profit
organizations, and Native American tribes or Aboriginal (First Nations,
Métis and Inuit) groups in the U.S. and Canada are invited under this
Program Announcement.

(2). Although proposals must demonstrate that at a minimum four (at
least two Canadian and two U.S.) organizations are participating in the
project, multi-sector partnerships are encouraged. As stated previously,
a lead organization for the U.S. and a lead organization for Canada must
be identified.

(3). [The application must clearly define the tasks and responsibilities
of each collaborative organization.]{.underline} An **Agreement of
Participation** (Attachment H) is required of each organization
participating. Each participating organization shall agree to
contribute, in-kind or cash, to the project.

#### H. Unsuitable Applications

> (1). Applications will not be considered for projects on topics not
> being sought under this Program Announcement. Though integral to many
> operations, data collection is not considered an appropriate activity
> for funding under this Program Announcement.
>
> (2). Applications are sought from U.S. and Canadian organizations.
> Applications from any other countries (other foreign governments,
> foreign citizens, educational institutions in foreign countries or
> firms located in foreign countries) will not be accepted.
>
> (3). Proposals in which there is a real or an appearance of a conflict
> of interest will not be accepted.
>
> (4). Applications solely involving the direct procurement of a product
> or service will not be considered.

(5). Applications that do not meet the requirement for
participation/collaboration of other organizations will not be
considered.

#### I. Period of Performance

The project will begin upon completion of the award documents on or
about March 2006. All activities proposed must be completed on or before
the end of the Canadian Government fiscal year [March 31,
2007.]{.underline}

#### J. Reporting Requirements

Note that travel costs for project participants to attend the three
meetings identified in the reporting requirements should be included in
the cost proposals. The meeting locations are proposed by the applicant.

Required reports, presentations, and other participatory involvement:

> (1). Initial Orientation meeting involving all key project
> participants, the GeoConnections representative and FGDC Secretariat
> (Travel by project participants may be required depending on meeting
> location as proposed by the applicant);
>
> (2). Milestone reports indicating project progress;
>
> (3). Interim progress review meeting (Travel by project participants
> may be required depending on meeting location as proposed by the
> applicant); and,
>
> (4). Final technical report of project activities that includes:
>
> (a). Project summary;
>
> (b). Project outcome;
>
> (c). Recommendations for distributed thematic and framework
> development;
>
> (d). Assessment of project success;
>
> (e). Plans for follow-on activities including outreach;
>
> (f). Discussion about user-demand requirements for geospatial data in
> a national level spatial data infrastructure; and,
>
> (g). Discussion about commonalities, issues, difficulties, and
> challenges (both technical and policy) that were encountered.
>
> (h). Any other relevant deliverables.

(5). Formal oral presentation of the Project (Travel by project
participants may be required depending on meeting location as proposed
by the applicant).

# K. Publicity 

It's important that project results receive wide dissemination to
increase the base of knowledge and experience that can be shared
throughout the profession and geospatial community. Organizations
receiving an award are encouraged to publish the results of any work
supported under this Program Announcement, without review by the FGDC or
GeoConnections. However, publications or other written products
resulting from the project must acknowledge the financial assistance of
the FGDC or GeoConnections.

> (1). Publication of project results is strongly encouraged;
>
> (2). Formal oral presentation of the project (travel by project
> participants will be required, depending on meeting location as
> proposed by the applicants); and,

(3). Display the NSDI logo and GeoConnections logo on participating
organizations home page and link to the Geospatial One Stop portal and
GeoConnections Discovery Portal server if applicable to the project.

**L. Award Terms and Conditions**

(1). Awards made under this Program Announcement to the lead [US
organization]{.underline} shall be administered in accordance with
**General Terms and Conditions** (Attachment B and **Special Terms and
Conditions** (Attachment A).

(2). Canadian funding support for the project will be provided by the
Natural Resources Canada, GeoConnections Secretariat. In Canada, the
proponents will be paid by cheques to financially support the cost share
project. For federal departments, an interdepartmental settlement
transfer will be issued instead of cheque. A total of \$100,000.00
(Canadian Dollars) is available for the project. This funding will be
made to the lead Canadian organization and will be awarded by authorized
representatives of Canada.

#### M. Instructions for Preparing the Application

The application should be assembled in the following order listed below.
(See Section VII: List of Attachments for a summary of required
application documentation for U.S. and Canadian organizations.)

> (1). **Standard Form SF -- 424** *Application for Federal Assistance*
> (Applies to U.S. organizations only) The lead **US organization**
> should prepare this attachment and should be signed by an individual
> authorized to commit the applicant. See [Section V. Application and
> Submission Information, A. Proposal Forms.]{.underline}

In addition, the US organization should provide a cost proposal that
contains a breakdown of the total estimated project cost by individual
milestones described in your Technical Proposal. This cost proposal
should show in-kind and grant funds, and what each organization is
contributing or spending on each milestone.

> (2). **Standard Form SF -- 424A** *Budget Information --
> Non-Construction Program* (Applies to U.S. organizations only) The
> **U.S. organization** should prepare this document. See [Section V.
> Application and Submission Information, A. Proposal
> Forms.]{.underline}
>
> (3). **Canadian Applicant Budget Information.** (Applies to Canadian
> organizations only) Preparation of the price proposal for **Canadian
> participants** - Please include sufficient funds to cover three travel
> requirements: (a). attendance at an initial program orientation
> meeting, (b). attendance at an interim progress review meeting, and
> (c). a formal oral presentation of project activities at a conference
> agreed upon between the FGDC/GeoConnections and the award recipient.
> This meeting location is to be proposed by the applicant.
>
> **Allowable Expenditures**
>
> The Recipient agrees that the contribution referred to in Section D
> (2), Canadian Funding Support, of this announcement will be applied to
> the allowable expenditures incurred in the course of conducting the
> project activities. The allowable expenditures are:
>
> -direct costs of carrying out the project, including: professional
> labor fees, project management, development of a demonstration of the
> ability to address sound community decision-making through the
> collaborative use, maintenance and sharing of distributed geospatial
> data; travel to conduct the project (at rates negotiated with
> GeoConnections), project coordination and communications.
>
> -administration of the project, including: administrative labor;
> liaison with project consultants, GeoConnections, FGDC; others
> partners; translation; printing and binding of project reports.

**(**a). **Method of Payment**: The pricing basis for the resultant
contribution may be negotiated between GeoConnections and the selected
Applicant. Negotiation of the pricing basis may be required normally in
accordance with the requirements stated in the RFP.

**(**b). **Price Proposal:** The price proposal should contain a
detailed breakdown of the total estimated project cost by individual
milestones in a firm price bid and described in the Technical Proposal
application. [Please note that the project team cannot submit a price
proposal based on average rates. Each project team member\'s workload
has to be priced separately using appropriate costing procedures. The
total of all project team member prices will be included in the proposed
total estimated project cost.]{.underline}

**(**c). **Project Cost Breakdown:** This detailed total estimated
project cost breakdown should address, as applicable, but not be limited
to, each of the following:

(i.) **[Labor:]{.underline}** For the purposes of this announcement,
labour costs represent the actual salaries paid to personnel. For
in-kind contributions, labour also includes employee benefits up to a
maximum of 20%. Each participating organization is required to explain
how it calculates per diem rates. A typical way to calculate labour is
to use the labour-rate formula: reasonable annual salary, plus
reasonable overhead and benefits, divided by a reasonable number of
billable days in a year. Labour rates must be exclusive of profit. In
the case of government personnel, official labour rates approved by the
government organization should be used.

(ii.) **[Other Direct Charges]{.underline}:**

**- Equipment/Software Rental**. Rental costs will be considered, if
included in your price proposal. Purchase costs for equipment are not
acceptable and will not be considered. Costs for software essential to
the project will be considered. The original purchase price of the
equipment or software as well as the number of years of useful life of
the equipment or software should be provided with the price proposal.
Equipment and software used in the day-to-day business of the
organization are covered in the overhead in the labour rates and cannot
therefore be considered as in-kind contributions. The costs for
equipment/software should not exceed 25% of the total estimated project
cost.

\-**Training:** Training, as part of technology transfer activities, may
form part of the total estimated project cost. It should not, however,
exceed 15% of the total project cost. Training costs should be fully
explained and justified in the project proposal.

**- Materials, Supplies, Components:** Indicate general categories and
the pricing basis, inclusive of customs duty and taxes, but exclusive of
GST/HST. Indicate whether the items are likely to be used or consumed
during the course of the project work.

**- Travel and living expenses:** Limited travel and living expenses
will be considered case-by-case depending on the travel's purpose.
Proposals should detail the basis and cost of all required travel. The
basis of travel costs should be in accordance with the current Treasury
Board Travel Directive, or, if applicable, in accordance with the
project proponent's own travel guidelines (but not exceeding the
Treasury Board Directive). The Treasury Board Travel Directive is
available at
http://publiservice.tbs-sct.gc.ca/pubs_pol/hrpubs/TBM_113/td-dv_e.asp.

**- Subcontracts:** Identify potential subcontractors and provide for
each the same cost breakdown information detailed herein.

**- Other Charges:** Identify any other direct charges, inclusive of
customs duty and taxes, but exclusive of GST/HST, such as long distance
communication and rental costs. Please provide the estimated cost of
each one, and the relevance to the proposed work.

[Profit: Not applicable since proposals are required to be submitted on
a cost sharing basis. Foregoing of profit is not allowable as a
contribution.]{.underline}

[Advance payments: Based on Treasury Board Policy on Transfer of
Payments (2-12).]{.underline}

Contributions are normally paid on the basis of achievement of
performance objectives or as reimbursement of expenditures incurred.
Where advance payments are necessary, they should be limited to the
immediate cash requirements of the recipient and not exceed the
following payment frequency:

+------------------+-----------+------------------+-------------------+
| Total Value of   | Duration  |                  |                   |
| annual amount    | of        |                  |                   |
|                  | Agreement |                  |                   |
+------------------+-----------+------------------+-------------------+
|                  | ##### L   | 4 months or      |                   |
|                  | ess than  | longer           |                   |
|                  | 4 months  |                  |                   |
+------------------+-----------+------------------+-------------------+
|                  |           | Initial Advance  | Subsequent        |
|                  |           |                  | Advances          |
+------------------+-----------+------------------+-------------------+
| Up to \$24,999   | 90%       | 90%              | N/A               |
+------------------+-----------+------------------+-------------------+
| \$25,000 -       | 90%       | Up to 75%        | Quarterly         |
| \$100,000        |           |                  |                   |
+------------------+-----------+------------------+-------------------+

For agreements of less than 4 months, the schedule represents the
maximum percentage that may be paid out initially, with the balance
payable monthly or at the end of the agreement. The amount of each
advance payment would correspond to its frequency, e.g. a quarterly
advance would be for the approximate amount of expenditures expected to
be incurred by the recipient in the following three months.

**N. Proposal Application Narrative**

The narrative is the most important part of your application. (To be
prepared jointly by collaborating **U.S. and Canadian applicants**).
[Applicants shall submit an unbound, signed original and 10 rubber
banded or binder-clipped copies of the application.]{.underline} The
Application Narrative shall not exceed 12 single-spaced pages (including
figures and tables), and the type size shall not be smaller than
12-pitch/10 point type. References, appendices, curriculum vitae,
letters of support/endorsement, and related documentation are not
included within the 12-page limit.

[Applications for funding will be considered in accordance with the
following factors set forth below]{.underline}. Proposals should address
each of the following factors in the exact headings and sequence as they
are listed. Please provide sufficient definition or description of
methodology within the context of the project, to permit understanding.
Please be very explicit. We encourage applicants to use examples to
demonstrate their understanding. The maximum possible score for all
selection factors together is 100 points. The application narrative
should not exceed 12 pages.

(0). Project Summary--- please list as appropriate:

> \(a\) Canadian and U.S. Lead organizations
>
> \(b\) Lead Canadian and U.S. project contacts (name, telephone, email)
>
> \(c\) Collaborating organizations (include Agreement of Participation,
> Attachment J, as attachments)
>
> \(d\) Collaborating organizations key contacts (name, telephone,
> email)
>
> \(e\) Relevant Internet addresses
>
> \(f\) Geographic scope of project
>
> \(g\) Concise description of the project (limit to 200 words).

(1). [Project Description]{.underline} (20 points)-- Merit to the
Canadian Geospatial Data Infrastructure (CGDI) and National Spatial Data
Infrastructure (NSDI)

> Proposals will be evaluated on the quality and relevance of the
> project to spatial data infrastructures (NSDI, CGDI).

(a). The proposal should include a concise description of the project; a
clear statement of project objectives; an explanation of how, and to
what degree, the proposed effort contributes to the development of a
joint U.S./Canadian regional information sharing initiative and identify
an issue in need of improved cross-border cooperation. The project must
address a practical problem as described under Scope (section A) and
Project Goal (section C) of this announcement.

> (b). The proposal should include citations of related and ongoing
> projects and describe their connection to such ongoing projects.
>
> (c). The proposal should include specific well-defined project
> outcomes that will result from this project. Describe how such
> outcomes will increase the use of connected distributed data sets and
> services as well as foster the increased use of a common geospatial
> framework for Canada and the United States.

(2). [Project Approach]{.underline} (20 points)

Applications should outline the steps that will be taken to implement
the project. The applicant should describe feasibility and levels of
risk associated with this project. Provide a detailed project plan to
accomplish the stated objective.

> (a). Proposals will be evaluated on the degree to which they reflect
> an understanding and detail of the tasks and procedures necessary to
> accomplish the stated objective. The proposal will be evaluated to
> determine whether the resources identified by the applicant to
> accomplish the tasks are reasonable relative to the anticipated
> results, and whether they accurately reflect the level of effort
> described in the proposal, including the necessary facilities,
> equipment, and supplies.
>
> (b). Proposals will be evaluated on the adequacy of the methodology to
> carry out the effort; steps taken to implement the project, evidence
> of adequate planning; effectiveness of the plan of management to
> assure proper and efficient administration of the project; and quality
> of the applicant\'s plans to use its resources and personnel to
> achieve the project objective.
>
> (c). To show clearly the tasks and responsibilities of the project,
> the proposal should include two tables. The first table emphasizes
> participating organizations and shows their roles and contributions
> (as shown below). The second table emphasizes contributions by project
> milestone (also shown below).

Table 1

+-----------------+-----------------+-----------------+-----------------+
| #######         | **Human\        | **Role**        | *               |
| ## Organization | Resources**     |                 | *Contribution** |
+-----------------+-----------------+-----------------+-----------------+
| Company A       | Joe Smith       | Scientist       | \- data         |
|                 |                 |                 | analysis        |
|                 | Sam Johns       | Analyst         |                 |
|                 |                 |                 | \- labour       |
+-----------------+-----------------+-----------------+-----------------+
| Agency X        | Paula Data      | Data processing | \- travel       |
|                 |                 |                 |                 |
|                 |                 |                 | \- material     |
|                 |                 |                 |                 |
|                 |                 |                 | \- labour       |
+-----------------+-----------------+-----------------+-----------------+

Table 2

+---------+-----------+----------+-----------+-----------+-----------+
| #       | **Tasks** | **Team\  | **\#      | **Deliv   | **Due     |
| ####### |           | m        | Days**    | erables** | date**    |
| # Phase |           | embers** |           |           |           |
+---------+-----------+----------+-----------+-----------+-----------+
| 1       | Research  | Tom      | 10        | Milestone | December  |
|         |           | Jones    |           | report    | 1^st^     |
|         |           |          | 5         |           |           |
|         |           | Julie B. |           | Prototype | February, |
|         |           |          |           |           | 4th       |
+---------+-----------+----------+-----------+-----------+-----------+
| 2       | Analysis  | Afonso   | 3         | Milestone | March     |
|         |           | M.       |           | report    | 31^st^    |
+---------+-----------+----------+-----------+-----------+-----------+

> (d). The proposal should include a work plan that indicates clearly
> identified outcomes as a means of assessing progress. In outlining
> project tasks, please include a Work Plan Milestone Chart (such as
> Gantt) illustrating major activities and their completion dates as an
> attachment to the Application Narrative (the milestone chart does not
> count against the 12 page narrative limit). The Initial Orientation
> Meeting, Interim Progress Review Meeting, and Final Technical Report
> shall be in your milestones.
>
> (e). Proposals will be evaluated on their ability to register and
> catalogue metadata to a clearinghouse for searching, ability to
> connect distributed data sets to the Internet, and their ability to
> implement web services at the end of the project.

(3). [Technical/Operational Context]{.underline} (30 points)

> Proposals should demonstrate technical and operational goals. The
> technical approach will be evaluated on its ability to address:
>
> (a). The goals of:
>
> (1). Data integration (horizontal and vertical alignment, scale,
> conflation, generalization, semantics, format conversion, and
> assessment of data quality);
>
> (2). Maintenance of data including updates and revisions;
>
> (3). Convergence of framework concepts and methodologies between U.S.
> and Canada including: Utilization of the U.S. NSDI framework data
> themes: geodetic control, cadastral data, hydrography, elevation,
> government units, transportation, and orthoimagery; and Canadian CGDI
> framework and GeoBase themes: geodetic reference system, roads,
> hypsography (DEM), hydrographic layers, Canadian Data Alignment Layer
> (CDAL), geographical names, orthoimagery, and administrative
> boundaries;
>
> (4). Implementation and use of standards (i.e. FGDC Metadata standard
> or ISO metadata standard);

(b). The operational capability to use web map and web feature client
and server software for linking and viewing distributed thematic
geospatial and framework data between U.S. and Canadian organizations.
This capability should use Open Geospatial Consortium (OGC)
specifications.

> (1). Describe how clearinghouses will be used in the project. Include
> current functionality of the clearinghouse and its service of
> compliant metadata. Describe efforts to extend the clearinghouse to
> include such OGC compliant services as web mapping services (WMS), web
> feature services (WFS), web coverage services (WCS), geographic markup
> language (GML), styled layer descriptors (SLD).
>
> (2). Describe the extent that OGC compliant web mapping services are
> part of this project.
>
> (3). Describe the extent that OGC compliant web feature services are
> part of this project.

(4)**.** [Business Context]{.underline} (10 points)

> The application should describe the approach proposed to ensure that
> the project will result in distributed data that are widely used and
> useful--increased distributed data accessibility. Innovative
> approaches are encouraged. These include:
>
> (a). avoidance of restrictive practices that would inhibit the use of
> the distributed data;
>
> (b). provide information about copyright and intellectual property
> issues, data limitations, including suggested optimal uses of data,
> disclaimers and liability;
>
> (c). be available in public and non-proprietary format(s);
>
> (d). use business practices that increase distributed data activities.

(5). [Project Participants/Experience/Outreach]{.underline} (20 points)

> (a). Participation: Each project must involve four or more
> organizations. Proposals will be evaluated based on the level and
> diversity of participation. Applications should clearly define the
> tasks and responsibilities of each collaborative organization
> (Complete the **Agreement of Participation** Attachment H). Any
> additional evidence of the activity being endorsed and supported
> (formal Memoranda of Understanding and/or letters of commitment from
> participating organizations) should be provided as attachments.
>
> (b). Experience: Proposals will be evaluated to assess the
> applicant\'s experience and competence to perform the proposed effort
> successfully, including the following: the significant qualifications
> of key personnel to be used in the project; the time that each person
> named will commit to the project; and whether the staffing is adequate
> to complete the effort in the designated time frame. Describe
> experience, qualifications, and skills held by the staff for
> performance of the project. (Resumes of key personnel may be provided
> as attachments).
>
> (c). Outreach: The application should describe the means of providing
> for communication and outreach to stakeholders, such as, web pages,
> workshops, and informational meetings. Also, the proposal should
> describe ways to improve project visibility. The application should
> describe the degree that the project accommodates the participation of
> new or other organizations having similar data interests over the
> project area;

### **O. Delivery of Application** 

See [Section V. Application and Submission Information]{.underline}

###### P. Contact Information

For questions concerning the preparation of the application please
contact:

(1). U.S. applicants: See [Section VIII. Agency Contacts]{.underline}

(2). Canadian organization applicants:

> Julie Béland\
> Project Coordination Officer\
> Program Management Office\
> GeoConnections Secretariat\
> Natural Resources Canada\
> Government of Canada\
> Room 626, 615 Booth Street\
> Ottawa, Ontario, K1A 0E9\
> Canada
>
> Telephone: (613) 947-5009\
> Facsimile: (613) 947-2410\
> Email: jbeland@nrcan.gc.ca

**[XIII. 2006 NSDI CAP Category 5: Geographic Information Integration
and Analysis]{.underline}**

**A. Background**

Through activities of the NGPO, the U.S. Geological Survey (USGS) is
working with federal, state, tribal, and local government agencies and
the private sector to make available current and accurate geographic
data in an integrated format to support the business needs of
governments, private companies and the public. Category 5 of the CAP
grant seeks to develop sustainable partnerships to integrate, maintain
and provide access to current geospatial data and to develop the
infrastructure needed to integrate these data and make them available
through geospatial programs of the NGPO.

Projects funded under this category are expected to implement or expand
sustainable operational capabilities to maintain and update data over an
organization's (or consortia) geographic area of interest and to provide
access to them through *The National Map* and the Geospatial One-Stop
portal. Related data, web services, and plans for data maintenance and
backup procedures will be documented in a partnership agreement with the
NGPO and made available through the Geospatial One-Stop portal, as
appropriate.

**B. Goal**

The goal of this category is to assist organizations and consortia to
work together with the NGPO to develop and provide access to geospatial
information that serves community needs. Participation is sought from
those organizations that maintain, update, and serve geospatial data of
interest to multiple users. Of special interest are organizations or
consortia whose geographic area of interest covers a "large area" (for
example, a state, group of states, ecoregion, or metropolitan area).
Funds may help new participants overcome initial impediments to
participation and current participants improve their services as part of
the NSDI.

**C. Measurable Results**

-   Base topographic data provided to *The National Map* and other data
    available through the Geospatial One-Stop portal. The base data
    provided should be available in the public domain[^1] for unlimited
    viewing, downloads (limited by data volume restrictions), and
    unrestricted use and redistribution. Participants are expected to
    allow their map services and metadata to be featured on the
    Geospatial One-Stop portal.

-   Operational capability to maintain and update data evidenced through
    periodic updates of data made available through *The National Map*.

-   Written agreement with NGPO to serve as an NSDI steward.

**D. Deliverables**

In addition to the data, services, and agreement, interim and final
reports documenting activities and outcomes are required. See Section
IV.B for reporting schedule. Documentation will describe approaches used
for integrating, maintaining, and updating data, encouraging
participation, managing operations and plans for keeping data current,
and other best practices that can be followed by others for adoption.
See Attachment G - Geographic Information Integration & Analysis Project
Report Format for content.

**E. Applicant Eligibility**

1)  Organizations (State and local government, regional consortia,
    academia, private sector, non‑profit and tribal organizations) or
    consortia of organizations may apply for this category.

2)  A letter of support from a state or regional GIS council or
    equivalent coordination group is encouraged.

3\) The applicant must demonstrate the capability to develop, maintain,
update, and

make available data in support of the NSDI.

4\) Applicants must have geographic information system or mapping
software that

can be extended to support OGC Web Mapping Service (WMS) version 1.1.1
(or

later) interfaces.

**F. Funded Tasks**

\(1\) Activities such as organizing and integrating data and metadata,
providing incentives for participation, implementing procedures for data
integration and maintenance, and providing access to data through *The
National Map* and the Geospatial One-Stop portal.

\(2\) Reasonable expense for hardware and software may be funded
dependent on available funds. Data collection will NOT be funded through
this announcement.

\(3\) In addition, applicants are requested to budget sufficient travel
funds (approximately \$1,000) for the participation of an individual at
the orientation, training and kickoff workshop to be held in Annapolis,
MD, March 19, 2006.

### (4) Project Presentation: In order to spread and promote knowledge of the NSDI, 2006 CAP participants are requested to formally present on their activities and contribute to written materials prepared by the NGPO. Presentation can be at local, state, regional, national conference or meeting. The applicant is requested, if necessary, to budget sufficient funds to travel to the meeting or conference. An alternative is to publish a paper or article in a professional journal or newsletter. The NGPO requests that this information be shared for NGPO purposes. 

**G. Funding Amount**

Up to \$50,000 will be obligated to individual projects under this
category.

**H. In-kind Resource Match and Partnerships Requirements**

A minimum [100% match]{.underline} is required; these resources may
include salaries, funds, and software dedicated to the project. Up to 15
percent of an in-kind match can be in the form of the value of
geospatial data holdings to be offered. (USGS understands that the value
of data provided is likely to be much higher.)

For the maximum award of \$50,000, the required 100% in-kind match is
\$50,000.

**I. Applicable Standards**

Projects must be in conformance with the standards, specifications, and
guidelines below:

1)  Open GIS Consortium- (OGC-) compliant Web Mapping Service (WMS)
    (version 1.1.1 or later)

2)  ISO/FGDC metadata standard

3)  Geospatial Positioning Accuracy Standard, Part 3, National Standard
    for Spatial Data Accuracy (FGDC-STD-007.3-1998)

4)  For hydrography, elevation, and geographic names, specifications and
    procedures for the National Hydrography Dataset (see
    http://nhd.usgs.gov), the National Elevation Dataset, and the
    Geographic Names Information System (see http://geonames.usgs.gov)
    respectively.

If the applicant anticipates offering additional web services, consult
with USGS liaisons to discuss relevant standards to be used.

**J. USGS Project Resources:**

The USGS will provide through its website www.usgs.gov/ngpo information
on *The National Map*, *Geospatial One-Stop* and *NSDI* as well as
contact information for USGS Geospatial Liaison personnel at the state
level.

Applicants are encouraged to contact Geospatial Liaisons for questions
on activities in their states and about participation in the CAP
program.

The USGS will provide technical advice on how Open Geospatial Consortium
Web Services and how data for *The National Map* should be served and
validated.

**K. USGS Involvement Statement:**

The USGS will collaborate closely with the awarded projects. Through the
local geography liaison, USGS will monitor the milestones and
accomplishments on work performed as part of this agreement.

### **L. Application Review and Award Criteria**

Applications are considered based on the completeness of documentation,
and meeting of stated basic eligibility and in-kind match and
partnership requirements. Specific evaluation factors are identified in
the proposal narrative and summary worksheet. Budget information is
evaluated for reasonableness and appropriateness to the goals of the
NSDI and the applicant's project goals. In addition to the above
criteria, proposals maybe selected for award based on geographic areas
of interest, organizational sectors, data themes, or geographic
dispersion.

Proposals are reviewed by a peer group of professionals knowledgeable in
the GIS discipline, the NGPO programs, and the NSDI. Individual
proposals will be evaluated and ranked for meriting award. The slate of
proposals proposed for award will be submitted to NGPO management for
final approval.

**M. Project Narrative:**

The project narrative is the primary document that will be evaluated by
the review panel. Total point value of 100 points possible. [Please
limit to 5 pages]{.underline} (not including letters of support, tables,
maps, and diagrams):

[Project Narrative]{.underline}: Please address each of the following
factors in the sequence as they are listed. The maximum possible score
is 100 points.

Please list the name of the [Project Leader]{.underline} and that
person's [Organization]{.underline}.

\(1\) [Organizational and Managerial Capacity]{.underline} (25 points)

Describe the management plan for the activity, including the nature of
the applicant's organization (e.g. single organization or consortium)
and its formally documented relationships with other participants in the
project. Describe the applicant's ability and experience in managing key
aspects of projects such as the one proposed, including the functions of
geospatial data maintenance and integration, access, and management;
coordination, executive guidance; financial and other resource
management; and monitoring and responding to users (for more
information, see the first half of
http://www.fgdc.gov/framework/frameworkintroguide/chapter4.html).
Identify the portion of the organization's budget that is represented by
the amount requested. Briefly describe the organization's or
consortium's outlook for sustained operation in the next three years,
and identify how the outcomes of the project fit the business plans and
benefits anticipated by the partners or customers of the applicant.

\(2\) [Project Scope]{.underline}: (25 points)

Provide a project plan, to include the scope of project, a description
and measured area of the geographic area of interest, the intended
activities, and the data themes to be viewable and/or downloadable.
Describe the characteristics of these data. Discuss the anticipated
update or refresh cycle for the data. Identify the extent to which data
will be degraded or restricted for any reason. Identify the
organizations involved and their roles and commitments to the project.
State that the data in the project are in the public domain. Identify
any other applications or services anticipated to be developed through
the project. Clearly identify the intended outcomes of the project.

\(3\) [Related Experience of Project Team]{.underline} (25 Points)

Describe the team's current level of activities and involvement in data
maintenance and update activities, and services currently provided, for
the data. Identify staff expertise in establishing and modifying GIS web
services. Describe experience with USGS topographic mapping and
partnership activities, especially digital data activities that
contribute to the NSDI such as programs and databases for imagery,
elevation, hydrography, geographic names, and land cover, or other
statewide activities similar in scope. Describe experience with NSDI
activities, including, but is not limited to, any experience with NSDI
areas of standards, metadata, clearinghouse, framework, organizational
coordination, and activities related to Geospatial One-Stop. Indicate if
the proposal supports state or regional GIS infrastructure objectives,
coordination with state or regional GIS coordination groups or their
equivalents, and their implementation plans.

\(4\) [Data Service Function and Capacity]{.underline} (25 points)

Describe your GIS data and mapping capabilities for data maintenance and
update, and web-based display and other services for the data that will
be used in the project. Indicate the capacity of your data servers to
support anticipated user demand (e.g. expressed as design goals for maps
rendered, volume of data to be downloaded per time interval, internet
bandwidth requirements, number of simultaneous users). Describe plans
for continuity of operations, backup, mirror sites, and/or offsite
archive. Provide the name and version of the software being used or
developed for this project. Identify users and collaborators that access
your GIS data and mapping services and the volume of information being
made available. Describe design goals, both short term and long term, of
how this project will improve your current baseline. In addition, if
hardware and software are to be acquired under this announcement please
describe it and justify its function to the project.

**N. Data Themes and Goals for Data Characteristics**

The following information provides a better sense of the data themes and
related data characteristics in *The National Map*. Characteristics of
data currentness and positional accuracy are provided as goals. Data
offered must improve (be more current, accurate, etc.) on those already
available in *The National Map*.

Generally, the data provided must feature one or more of the following
data themes: raster color or black-and-white orthoimagery; raster
ground-surface elevation; vector feature data for the themes of
hydrography, transportation centerlines (especially roads, but also
including railroads, pipelines, powerlines, and other features),
structures, and boundaries of governmental units and administrative
boundaries of publicly-owned lands; geographic names; and land cover.
For the vector data categories the minimum information content is
descriptive information such as feature type or classification
information and a geographic name. For road data, street name and
address range information is desired. Other commonly-used unique feature
identifiers also are of interest. Specific information content
requirements for hydrography and geographic names are available in
documentation for the National Hydrography Dataset (http://nhd.usgs.gov)
and Geographic Names Information System (http://geonames.usgs.gov)
respectively.

Two types of geographic areas are of special interest. For urban areas
(see section O), the data should have the currentness and positional
accuracy qualities typically sought by local governments. For large
areas (for example, states or groups of states), the data should have
the positional accuracy qualities of USGS primary topographic map series
(typically 1:24,000-scale; 1:63,360-scale in Alaska). The following
table provides minimum (that is, data should be no worse than these
measures) goals for these two classes of data:

  ------------------------------------------------------------------------------------------------
  **Minimum ("no                                                               
  worse than")                                                                 
  Goals for                                                                    
  Resolution,                                                                  
  Accuracy, and                                                                
  Currentness**                                                                
  ---------------- ------------------- ------------------- ------------------- -------------------
                   **Urban Areas (see                      **Large Areas**     
                   Section O)**                                                

  **Data Theme**   **Minimum           **Minimum           **Minimum           **Minimum
                   Resolution or       Currentness**[^3]   Resolution or       Currentness**[^5]
                   Accuracy**[^2]                          Accuracy**[^4]      

  Orthoimagery     1 foot resolution;  Two years           1 meter resolution; Five years
                   3 meters horizontal                     11.70 meters        
                   accuracy                                horizontal accuracy 

  Elevation        1/9 arcsecond       Two years           1/3 arcsecond       Five years
                   (\~3 meters)                            (\~10 meters) (2    
                   resolution; 0.73                        arcsecond in        
                   meter vertical                          Alaska) resolution; 
                   accuracy                                vertical accuracy   
                                                           commensurate with   
                                                           contour interval of 
                                                           USGS primary        
                                                           topographic map for 
                                                           area                

  Hydrography      4.68 meters         Two years           13.90 meters        Five years
                   horizontal accuracy                     horizontal          
                                                           accuracy; 36.69     
                                                           meters horizontal   
                                                           accuracy for Alaska 

  Transportation   4.68 meters         Two years           13.90 meters        Five years
                   horizontal accuracy                     horizontal          
                                                           accuracy; 36.69     
                                                           meters horizontal   
                                                           accuracy for Alaska 

  Boundaries       4.68 meters         Two years           13.90 meters        Five years
                   horizontal accuracy                     horizontal          
                                                           accuracy; 36.69     
                                                           meters horizontal   
                                                           accuracy for Alaska 

  Structures       4.68 meters         Two years           13.90 meters        Five years
                   horizontal accuracy                     horizontal          
                                                           accuracy; 36.69     
                                                           meters horizontal   
                                                           accuracy for Alaska 

  Land Cover       Should align with   Two years           Should align with   Five years
                   base maps that have                     base maps that have 
                   the accuracies                          the accuracies      
                   listed above.                           listed above.       

  Geographic Names Same as the                             Same as the         
                   associated feature                      associated feature  
  ------------------------------------------------------------------------------------------------

Data should be in the North American Datum of 1983; elevation data in
the North American Vertical Datum of 1988.

Other sought data characteristics are reviewed in "*The National Map*:
Topographic Mapping for the 21^st^ Century"
(http://nationalmap.usgs.gov/report/national_map_report_final.pdf,
starting on page 10).

Other requirements:

1)  The data provided should be available in the public domain.

2)  The data provided will be available for unlimited viewing, limited
    downloads (limited by data volume restrictions), and unrestricted
    use and redistribution.

3)  USGS may incorporate data provided in *The National Map* into its
    national databases; in particular:

    a.  Activities that include hydrography data must result in the data
        being incorporated into the National Hydrography Dataset.

    b.  Activities that include elevation data must result in the data
        being incorporated into the National Elevation Dataset.

    c.  Activities that include geographic names must result in data
        being incorporated into the Geographic Names Information System.

**O. Urban Areas**

"Urban areas" of interest are the geographic area for the urbanized
area[^6] or urban cluster[^7] as delineated by the Bureau of the Census
from the 2000 Census for the places listed below. Coverage for an area
larger than that delineated by the Bureau of the Census may be proposed
by the applicant.

Albany, NY

Albuquerque, NM

Allentown -- Bethlehem, PA

Amarillo, TX

Anchorage, AK

Atlanta, GA

Augusta, GA

Augusta, ME

Austin, TX

Bakersfield. CA

Baltimore -- Annapolis, MD

Barre -- Montpelier, VT

Baton Rouge, LA

Birmingham, AL

Bismarck, ND

Boise, ID

Boston, MA

Bridgeport -- Stamford, CT

Buffalo, NY

Cape Coral, FL

Carson City, NV

Charleston -- North Charleston, SC

Charleston, WV

Charlotte, NC

Chattanooga, TN

Cheyenne, WY

Chicago, IL

Cincinnati, OH

Cleveland -- Akron, OH

Colorado Springs, CO

Columbia, SC

Columbus, GA

Columbus, OH

Concord, NH

Corpus Christi, TX

Dallas -- FT. Worth -- Arlington -- Garland -- Irving, TX

Dayton, OH

Denver -- Aurora, CO

Des Moines, IA

Detroit -- Warren, MI

Dover, DE

El Paso, TX

Flint, MI

Frankfort, KY

Fresno, CA

Ft. Wayne, IN

Grand Rapids, MI

Greensboro -- Winston Salem, NC

Harrisburg, PA

Hartford, CT

Helena, MT

Honolulu, HI

Houston, TX

Huntsville, AL

Indianapolis, IN

Jackson, MS

Jacksonville, FL

Jefferson City, MO

Juneau, AK

Kansas City, MO-KS

Knoxville, TN

Lancaster, PA

Lansing, MI

Las Vegas, NV

Lexington, KY

Lincoln, NE

Little Rock, AR

Los Angeles -- Glendale -- Long Beach -- Huntington Beach -- Santa Ana
-- Anaheim, CA

Louisville, KY

Lubbock, TX

Madison, WI

McAllen, TX

Memphis, TN

Miami -- Ft. Lauderdale, FL

Milwaukee, WI

Minneapolis -- St. Paul, MN

Mission Viejo, CA

Mobile, AL

Modesto, CA

Montgomery, AL

Nashville, TN

New Haven, CT

New Orleans -- Metairie, LA

New York -- Newark, NY

Norfolk -- Chesapeake -- Newport News -- Virginia Beach, VA

Oklahoma City, OK

Olympia, WA

Omaha, NE

Orlando, FL

Oxnard, CA

Palm Bay -- Melbourne, FL

Pensacola, FL

Philadelphia, PA

Phoenix -- Glendale -- Mesa, AZ

Pierre, SD

Pittsburgh, PA

Portland, OR

Poughkeepsie -- Newburgh, NY

Providence, RI

Raleigh -- Durham, NC

Reno, NV

Richmond, VA

Riverside -- San Bernardino, CA

Rochester, NY

Sacramento, CA

Salem, OR

Salt Lake City -- Ogden, UT

San Antonio, TX

San Diego, CA

San Francisco -- Oakland -- San Jose -- Fremont, CA

San Juan, PR

Santa Fe, NM

Sarasota -- Bradenton, FL

Savannah, GA

Scranton, PA

Seattle -- Tacoma, WA

Shreveport, LA

Spokane, WA

Springfield, IL

Springfield, MA

St. Louis, MO

**Attachment A**

**Terms and Conditions**

**1.** **[Method of Payment]{.underline}**

> The U.S. Geological Survey (USGS) is using the Health and Human
> Services (HHS) Payment Management System (PMS) to provide electronic
> invoicing and payment for assistance award recipients. The Recipient
> has established or will establish an account with PMS. With the award
> of each grant/cooperative agreement, a sub account will be set up from
> which the Recipient can draw down funds. The sub account number will
> be shown in block 4 of the face page of each award or modification.
>
> Payments will be made available through the PMS. The PMS is
> administered by the Department of Health and Human Services (DHHS),
> Division of Payment Management of the Financial Management Service,
> Program Support Center. The DHHS will forward instructions for
> obtaining payments to the recipients. Inquiries regarding payment
> should be directed to:
>
> Division of Payment Management
>
> Department of Health and Human Services
>
> P.O. Box 6021
>
> Rockville, MD 20852
>
> The Division of Payment Management web address is
> [www.dpm.psc.gov](http://www.dpm.psc.gov/). Problems or questions with
> electronic draw down procedures should be directed to Fran Odgers
> (301) 443-2090.
>
> Payments may be drawn in advance only as needed to meet immediate cash
> disbursement needs.

**2. [Cooperative Agreement]{.underline}**

> A cooperative agreement is the legal instrument reflecting a
> relationship between the Federal Government and a State or local
> government or other recipient whenever:
>
> \(1\) the principal purpose of the relationship is the transfer of
> money, property, services, or anything of value to the State or local
> government or other recipient to accomplish a public purpose of
> support, or stimulation authorized by Federal statute, rather than
> acquisition, by purchase, lease, or barter, of property or services
> for the direct benefit or use of the Federal Government; and
>
> \(2\) substantial involvement is anticipated between the executive
> agency, acting for the Federal Government, and State or local
> government or other recipient during performance of the activity.

**3. [Principal Investigator]{.underline}**

The Principal Investigator is the individual designated by the Recipient
(and approved by the USGS)

who is responsible for the technical direction of the research project.
The Principal Investigator cannot

be changed or become substantially less involved than was indicated in
the Recipient\'s proposal,

without the prior written approval of the Administrative Contracting
Officer.

**Attachment A - continued**

**4. [Project Officer]{.underline}**

> The USGS Project Officer will work with the recipient to ensure that
> technical requirements, as detailed in the awardee's proposal, are
> being met. The Project Officer's responsibilities include, but are not
> limited to, providing technical guidance on the project, resolving
> Recipient questions about USGS technical standards, and coordinating
> schedules, deliveries and exchange of materials.

**5. [Contracting Officer (CO)]{.underline}**

> Contracting officers are individuals who have been delegated in
> writing by the USGS Office of Acquisition and Grants as the sole
> authority designated to obligate Federal funds and create terms and
> conditions of awards. They are the only individuals who have authority
> to negotiate, enter into, and administer awards resulting for this
> program. Contracting officers have responsibility to ensure the
> effective use of Federal funds.

**6. [Rights in Technical Data]{.underline}**

> The U.S. Government may publish, reproduce, and use all data obtained
> from this Cooperative Agreement project in any manner and for any
> purpose, without limitation, and may authorize others to do the same.

**7. [Public Domain]{.underline}**

> All data submitted to the U.S. Geological Survey (USGS) under this
> Cooperative Agreement will become part of the public domain, and will
> be available in a non-proprietary format, at the cost of reproduction,
> to any requesting organization or individual.

**8. [Dissemination of Results and Reporting Requirements]{.underline}**

> The Principal Investigator is strongly encouraged to disseminate
> research results promptly to the scientific community and appropriate
> professional organizations; local, state, regional and federal
> agencies; and the general public. The U. S. Geological Survey (USGS)
> encourages the Recipient to publish project reports in scientific and
> technical journals. The Government may publish, reproduce, and use all
> technical data developed as a result of this award in any manner and
> for any purpose, without limitation, and may authorize others to do
> the same.
>
> Data generated as a part of work funded under this program is not
> subject to proprietary period of exclusive data access. Any data
> generated must be made available to the USGS as soon as it is
> available. The USGS reserves a royalty-free, nonexclusive and
> irrevocable license to reproduce, publish, or otherwise use, and to
> authorize others to use the data for Government purposes. Any project
> funded in whole or part with funds obtained under this program shall
> fall under this clause. The USGS Contracting Officer is the sole
> person to decide which data falls in this category should any question
> arise.

**Attachment A - continued**

A. **[Required reports/documents]{.underline}**. The Principal
Investigator or Director, Sponsored Research Office is required to
submit the following reports or documents:

+-----------+-----------------+----------+----------------------------+
| **        | **No. of        | **Submit | **When**                   |
| Report/** | Copies** **and  | To**◊    |                            |
|           | Method of       |          | **Due**                    |
| **D       | Transmittal**   |          |                            |
| ocument** |                 |          |                            |
+-----------+-----------------+----------+----------------------------+
| Interim   | Submitted by    | CAP      | 6 months after project     |
| Report    | email           | Program  | start date                 |
|           | attachment      | Contact  |                            |
+-----------+-----------------+----------+----------------------------+
| Final     | Submitted by    | CAP      | 90 days after completion   |
| Technical | email           | Program  | of project                 |
| Report    | attachment      | Contact  |                            |
+-----------+-----------------+----------+----------------------------+
| SF 272    | Original + 1    | Con      | Required quarterly of each |
|           |                 | tracting | PMS sub-account. Quarterly |
| Federal   |                 | Officer  | reports are due 15 working |
| Cash      |                 |          | days after the end of each |
|           |                 |          | fiscal quarter.            |
| Tra       |                 |          |                            |
| nsactions |                 |          |                            |
| Report    |                 |          |                            |
+-----------+-----------------+----------+----------------------------+
| Final SF  | Original + 1    | Con      | Submit a final SF 269 no   |
| 269       |                 | tracting | later than 90 calendar     |
| Financial |                 | Officer  | days after the grant       |
| Status    |                 |          | agreement completion date  |
| Report    |                 |          | and the Recipient will     |
|           |                 |          | liquidate all obligations  |
|           |                 |          | incurred under the award.  |
|           |                 |          | The Recipient will         |
|           |                 |          | promptly return any unused |
|           |                 |          | federal advances or will   |
|           |                 |          | complete a final draw from |
|           |                 |          | PMS to obtain any          |
|           |                 |          | remaining amounts due.     |
+-----------+-----------------+----------+----------------------------+

**Attachment A - continued**

B. [**Report preparation instructions**.]{.underline} The Recipient
shall prepare the reports/documents in accordance with the following
instructions:

(1**) Interim Project Report**. The Recipient is required to submit an
Interim Project Report

> six months after the start of the project date. Interim report should
> be submitted as an attachment by email to the CAP Coordinator. See the
> CAP Administration webpage for the suggested report content at:
> (http://www.fgdc.gov/funding/admin.html).
>
> \(2\) **Annual and/or Final Technical Report.** Interim report should
> be submitted as an attachment by email to the CAP Coordinator. See the
> CAP Administration webpage for the suggested report content at:
> (http://www.fgdc.gov/funding/admin.html).

(1) **SF 272, Federal Cast Transactions Report** is required quarterly
    for each PMS sub-

> account. Quarterly reports are due 15 working days after the end of
> each fiscal quarter
>
> and will be submitted to the contracting officer, unless otherwise
> instructed.

(1) **Final SF 269, Financial Status Report**. Submit a final SF 269 no
    later than 90 calendar

> days after the grant agreement completion date and the Recipient will
> liquidate all obligations incurred under the award. The Recipient will
> promptly return any unused federal advances or will complete a final
> draw from PMS to obtain any remaining amounts due. This report is
> subject to audit.

C**. [Adherence to reporting requirements]{.underline}**. **A
Recipient\'s failure to submit the required**

**reports/documents, in a timely manner, may result in the with­holding
of payment, in**

**termination of the award, or in delay or non-issuance of a new
award.**

**9**. **[Adherence to Original Project Objective and Budget
Estimate]{.underline}**

> A. Any commitments or expenditures incurred by the Recipient in excess
> of the funds provided by this award shall be the responsibility of the
> Recipient. Expenditures incurred prior to the effective date of this
> award cannot be charged against award funds unless provided for in
> this award.
>
> B. **The following requests for change require advance written
> approval by the Contracting Officer shown on your award. Your request
> must be submitted directly to the Contracting Officer [at least 30
> calendar days]{.underline} prior to the requested effective date of
> the change:**
>
> \(1\) Changes in the scope, objective, or key personnel referenced in
> the Recipient\'s proposal.
>
> \(2\) Request for supplemental funds.

**Attachment A - continued**

> \(3\) Transfer of funds between direct cost categories when the
> cumulative amount of transfers during the project period exceeds 10
> percent of the total award.
>
> \(4\) Foreign travel not approved at time of award.
>
> \(5\) Acquisition of nonexpendable personal property (equipment) not
> approved at time of award.
>
> \(6\) [No-cost Extensions to the Project Period]{.underline}.
> **No-cost extensions are discouraged**. Applicants should consider
> their time commitments at the time of application for a grant.
> Requests for no-cost extensions will be considered on a case-by-case
> basis. The USGS reserves the right to limit the length of time and
> number of no-cost extensions. Applicants must supply documentation
> supporting their request for an extension. The Recipient shall include
> in the request the cause of the needed extension, a description of the
> remaining work to be completed, the proposed date of completion, the
> amount of funds remaining, and a revised budget for the remaining
> funds. If all funds have been disbursed to the Recipient, this must be
> indicated in the request. A request for an extension that is received
> by the Administrative Contracting Officer after the expiration date
> shall not be honored.
>
> \(7\) Creation of any direct cost line item not approved at time of
> award.

\(8\) Any other significant change to the award.

> C. The Contracting Officer will notify the Recipient in writing within
> 30 calendar days after receipt of the request for revision or
> adjustment whether the request has been approved.

**10. [Nonexpendable Personal Property]{.underline}**

> Title to nonexpendable personal property acquired wholly or in part
> with Federal funds shall be vested in the Recipient unless otherwise
> specified in the award document. The Recipient shall retain control
> and maintain a property inventory of such property as long as there is
> a
>
> need for such property to accomplish the purpose of the project,
> whether or not the project continues to be supported by Federal funds.
> When there is no longer a need for such property to accomplish the
> purpose of the project, the Recipient shall use the property in
> connection with other Federal awards the Recipient has received. Under
> no circumstances shall title to such property be vested in a sub-tier
> recipient. Disposal of nonexpendable personal property shall be in
> accordance with the applicable OMB circular.

**11. [Record Retention Period]{.underline}**

> Unless a longer period is requested by the award, a Recipient shall
> retain all records for 3 years after the end of the project period for
> which it uses USGS award funds.

**Attachment A - continued**

**12. [Pre-agreement Costs]{.underline}**

> Pre-agreement costs are not authorized under this program. Costs must
> be obligated during the project period.

**13. [Metric Conversion Requirements]{.underline}**

> All progress and final reports, other reports, or publications
> produced under this award shall employ the metric system of
> measurements to the maximum extent practicable. Both metric and
> inch-pound units dual units may be used if necessary during any
> transition period(s).
>
> However, the recipient may use non-metric measurements to the extent
> the recipient has supporting documentation that the use of metric
> measurements is impracticable or is likely to
>
> cause significant inefficiencies or loss of markets to the recipient,
> such as when foreign competitors are producing competing products in
> non-metric units.

**14. [Violation of Award Terms]{.underline}**

> If a Recipient materially fails to comply with the terms of the award,
> the Contracting Officer may suspend, terminate, or take such other
> remedies as may be legally available and appropriate in the
> circumstances.

**15. [Award Closeout]{.underline}**

> Awards will be closed out once all requirements have been met.
> Technical and financial reports must be submitted on time as specified
> in Item 2 of these Special Terms and Conditions. Failure to adhere to
> the reporting requirements may result in the non-payment of your final
> award invoice or in other adverse action.

**16. [Partnership with Grantees/Cooperators]{.underline}**

> The U.S. Geological Survey, through its federal grant/cooperative
> agreement awards, will collaborate with universities, federal state,
> local and tribal governments, and private organizations and businesses
> to provide relevant, timely, objective knowledge and information on
> natural resources, hazards and the environment.

**17. [Buy American Act Requirements]{.underline}**

> **Notice:** Pursuant to Section 307(b) of the Department of the
> Interior (DOI) and Related Agencies Appropriations Act, FY 2000,
> Public Law 106-113, please be advised on the following:
>
> In the case of any equipment or product that may be authorized to be
> purchased with financial assistance provided using funds made
> available in FY 2000 and thereafter, it is the sense of the Congress
> that entities receiving the assistance should, in expending the
> assistance, purchase only American-made equipment and products.

**Attachment A - continued**

**18. [Anti-Lobbying Requirements]{.underline}**

> The Recipient shall not use any part of the Department of Interior
> provided hereunder for any activity or the publication of distribution
> of literature that in any way tends to promote public or opposition to
> any legislative proposal on which Congressional action is not
> complete.

**19. [Seat Belt Provision]{.underline}**

> Recipient of grants/cooperative agreements and/or sub-awards are
> encouraged to adopt and enforce on-the-job seat belt use policies and
> programs for their employees when operating company-owned, rented, or
> personally owned vehicles. These measures include, but are not limited
> to, conducing education, awareness, and other appropriated programs
> for their employees about the importance of wearing seat belts and the
> consequences of not wearing them.

**20. [Endorsement Provision]{.underline}**

> Recipient shall not publicize or otherwise circulate, promotional
> material (such as advertisements, sales brochures, press releases,
> speeches, still and motion pictures, articles, manuscripts or other
> publications) which states or implies governmental, Departmental,
> bureau, or government employee endorsement of product, services, or
> position which the recipient represents. No release of information
> relating to this award may state of imply that the Government approves
> of the recipient's work products, or considers the recipient's work
> product to be superior to other products or services.

\--End of Special Terms and Conditions---

**Attachment B**

# GENERAL PROVISIONS

The Recipient shall be subject to the following OMB
circulars/regulations, as amended, which are incorporated herein by
reference:

1\. [Educational Institutions]{.underline}

> A. OMB Circular A‑21, Cost Principles for Educational Institutions.
>
> B. OMB Circular A‑110, Uniform Administrative Requirements for Grants
> and other
>
> Agreements with Institutions of Higher Education, Hospitals and Other
> Non-
>
> Profit Organizations (Being replaced by 2 CFR Part 215.)

C. OMB Circular A-133, Audits of States, Local Governments, and
Non-Profit

Organizations.

2\. [State and Local Governments]{.underline}

> A. OMB Circular A‑87, Cost Principles for State, Local and Indian
> Tribal Governments.
>
> B. OMB Circular A‑102, Grants and Cooperative Agreements With State
> and Local Governments.

C. OMB Circular A-133, Audits of States, Local Governments, and
Non-Profit

Organizations.

3\. [Nonprofit Organizations]{.underline}

> A. OMB Circular A‑110, Uniform Administrative Requirements for Grants
> and other Agreements with Institutions of Higher Education, Hospitals
> and Other Non-Profit Organizations.

B. OMB Circular A‑122, Cost Principles for Nonprofit Organizations.

> C. OMB Circular A-133, Audits of States, Local Governments, and
> Non-Profit Organizations.

4\. [Profit‑Making Organizations]{.underline}

A. General administrative requirements will be in accordance with the
OMB Circular

A-10 and the Cost Principles in Federal Acquisition Regulation (FAR)
Part 31.

**Attachment B**

B. Principles for determining the allowability of cost will be in
accordance with the

FAR, subchapter E, part 31.2.

5\. [Patents\--Small Businesses and Nonprofit Organizations]{.underline}

Subject to the provisions set forth in 37 CFR 401 and 35 U.S.C. 203, a
Recipient may retain the entire right, title, and interest throughout
the world to each subject invention. With respect to any subject
invention in which the Recipient retains title, the Federal Government
will have a nonexclusive, nontrans­ferable, irrevocable, paid-up license
to practice or have practiced for or on behalf of the United States the
subject invention throughout the world.

6\. [Code of Federal Regulations (CFR)]{.underline}

a.  43 CFR Part 12, Subpart A: Admin, Audit and Cost Principles

b.  43 CFR Part 12, Subpart D: Government Debarment and Suspension

> (nonprocurement) and Government wide requirements for Drug Free
>
> Workplace

c.  43 CFR Part 12, Subpart E: Buy American Requirements for Assistance
    Programs

d.  43 CFR Part 12, Subpart F: Admin -- Higher Education Hospitals, and
    Other Non Profit Organizations

e.  43 CFR Part 17, Subpart A: Nondiscrimination of the Basis of Race,
    Color, or National Origin

f.  43 CFR Part 17, Subpart B: Nondiscrimination of the Basis of
    Handicap

> . 43 CFR Part 17, Subpart C: Nondiscrimination of the Basis of Age
>
> . 43 CFR Part 18, Lobbying
>
> . 2 CFR Part 215, (new location for OMB Circular A-110 Uniform
>
> Administrative Requirements for Grants and other Agreements with
>
> Institutions of Higher Education, Hospitals, and other Non-Profit
>
> Organizations.)

\--End of General Provisions\--

**Attachment C**

**NSDI Cooperative Agreements Program\
Metadata Training & Outreach Project**

**[Interim and Final Project Summary Format]{.underline}**

Indicate **Agreement Number**

Indicate whether **Interim** or **Final Report**

List:

**Organization**: Name, address, web address.

**Project Leader**: Name, telephone, email

In writing the report keep in mind the objective of this category for
organizations skilled in metadata implementation, and clearinghouse
service to assist other organizations by providing training, metadata
creation assistance, and clearinghouse or web mapping services. Ideally,
sustained on-going processes for data documentation will be established
for organizations for documenting (metadata) their geospatial holdings,
serving this documentation.

**Project Narrative**

Summarize the project activities. Include its accomplishments, successes
strengths and weaknesses, further challenges, and collaboration
activities as appropriate. What are the organizational practices that
have developed to support metadata creation and maintenance for the
future?

**Metadata training and outreach assistance**

\- List organizations, organizational type and number of individuals
receiving metadata training, and outreach assistance as appropriate.

\- Indicate the competency of individuals and organizations competent in
creating me

\- At what level of proficiency or competency are the trainees or
training?

\- Indicate the number, duration and venue of workshops conducted as
appropriate

\- Character of workshop and participants e.g. managers, data producers
etc.

**Status of Metadata Service\
**- Site names where metadata is served; clearinghouse node or
Geospatial One-Stop harvestable web folder.\
- Approximately how many metadata entries have resulted from this
project?\
- Do you need assistance in providing for metadata service to
organizations you have assisted?

**Next Steps**

\- Will this project\'s activities continue in the future?

\- What formal or informal organizational relationships established to
sustain activities beyond performance period?\
- Describe the next phase in your project

\- Are there issues in metadata management and service\
- Requirements (more technical assistance, software, other?)

\- What areas need work?

\- What do you anticipate will be the activities of metadata training,
outreach, creation and posting (to clearinghouse or other locations)
after the project performance period ends?

**Feedback on Cooperative Agreements Program**\
- What are the program strengths and weaknesses?\
- Where does the program make a difference?\
- Was the assistance you received sufficient or effective?\
- What would you recommend doing differently?\
- Are there factors that are missing or need to consider that were
missed?\
- Are there program management concerns that need to be addressed? Time
frame?

\- If you were to do this again, what would you do differently?

**Attachment D**

**NSDI Cooperative Agreements Program**

**Framework Client Development**

**[Interim and Final Project Summary Format]{.underline}**

Brief documentation of the data and server configuration approach taken
is required in a form, with graphics, that can be followed by others for
adoption.

Indicate **Agreement Number**

Indicate whether **Interim** or **Final report**

List:

**Organization:** Name, address, web address

**Project Leader:**

Name, telephone, email

**Collaborating Organizations:** Name, point of contact, address, web
address

In writing the report keep in mind the goals of your project under this
category: to establish, register, and maintain an operational Web
Feature Service for Framework data.

**Project Narrative**

Summarize the project activities. Include its accomplishments, successes
strengths and weaknesses, further challenges, and collaboration
activities, as appropriate.

**Status of your data access activities**

What Framework data theme(s) will be accessed under this project?

What is the data volume of Framework data anticipated for access
(geographic coverage, dataset size, feature count)?

Who are the primary organizations providing data for this project?

**Status of Framework Client Development**

What is the status of software development?

How will the client software be evaluated and quality-assured?

Describe your experience and purpose in accessing the data services?

Describe any internal or external users that are using this client.

Identify plans for the promotion and distribution of this software.

**Project management**

Will this project\'s activities continue in the future?

Describe the next phase in your project .

Requirements (more technical assistance, software, other?)

What areas need work?

**Feedback on Cooperative Agreements Program**

What are the program strengths and weaknesses?

Where does the program make a difference?

Was the assistance you received sufficient or effective?

What would you recommend doing differently?

Are there factors that are missing or need to consider that were missed?

Are there program management concerns that need to be addressed? Time
frame?

If you were to do this again, what would you do differently?

**Attachment E**

**NSDI Cooperative Agreements Program**

**Interim and Final Project Summary Format**

**Fifty States Initiative: Strategic and Business Plan Development in
Support of the NSDI Future Directions Fifty States Initiative**

**Agreement Number**

**Interim or Final report**

**Organization**: Name, address, web address

**Project Leader**: Name, title, telephone, email

**Collaborating Organizations**: Name, point of contact with E-mail
address, address, web address

**Project Narrative**

In writing the report keep in mind the goal of your project under this
category which is the development and/or implementation of statewide
strategic and business plans.

Please include

-   Summary of project activities

-   Key accomplishments to date

-   Explain how statewide coordination has changed as a result of this
    project?

-   How inclusive is your effort? What have you done to bring new
    stakeholder groups or organizations into statewide coordination?

-   What practices or activities led to success? What practices or
    activities have not?

**Next Steps**

-   How will this project continue in the future?

```{=html}
<!-- -->
```
-   Describe the next steps in your project

-   Where do you need assistance?

**Attachments**

-   Strategic Plan

-   Business Plan

**Feedback on Cooperative Agreements Program**\
What are the CAP Program strengths and weaknesses?\
Where does it make a difference?\
Was the assistance you received sufficient or effective?\
What would you recommend that the FGDC do differently?\
Are there factors that are missing or additional needs that should be
considered?\
Are there program management concerns that need to be addressed, such as
the time frame?

If you were to do this again, what would you do differently?

**Attachment F**

**NSDI Cooperative Agreements Program**

**Joint Canadian-US Spatial Data Infrastructure Project**

**[Interim and Final Project Summary Format]{.underline}**

Indicate **Agreement Number**

Indicate whether **Interim** or **Final report**

List:

**Organization:** Name, address, web address

**Project Leader:** Name, telephone, email

**Collaborating Organizations:** Name, point of contact, address, web
address

**Project Narrative**

(a). Project summary;

(b). Project outcome;

(c). Recommendations for distributed thematic and framework development;

(d). Assessment of project success;

(e). Plans for follow-on activities including outreach;

(f). Discussion about user-demand requirements for geospatial data in a
national level spatial data infrastructure; and,

(g). Discussion about commonalities, issues, difficulties, and
challenges (both technical and policy) that were encountered.

(h). Any other relevant deliverables

**Feedback on Cooperative Agreements Program**

What are the program strengths and weaknesses?

Where does the program make a difference?

Was the assistance you received sufficient or effective?

What would you recommend doing differently?

Are there factors that are missing or need to consider that were missed?

Are there program management concerns that need to be addressed? Time
frame?

If you were to do this again, what would you do differently?

**Attachment G**

> **NSDI Cooperative Agreements Program**
>
> **Geographic Information Integration and Analysis**
>
> **Project Report**

The goal of this category is to assist organizations and consortia to
work with the USGS to make base geospatial information widely available
to meet government, business and citizen needs. Please use this format
to develop a brief and succinct interim or final project report, as
appropriate.

List:

> Cooperative Agreement Number:
>
> Project title:
>
> Project start and end dates:
>
> Lead project organization:

Project Lead:

> USGS Mapping State Liaison:
>
> Collaborating organizations (list):

Data themes: (list)

[Project Summary]{.underline}

a\. Describe the project; its tasks, highlights, challenges, and
accomplishments. What are your approaches to overcoming impediments to
participation in *The National Map*? Based on your experience what would
you recommend for implementation and development for project success
(technical, institutional and organizational)?

b\. Describe the data themes provided through *The National Map*. Are
there any use restrictions? Are your map services and data documentation
(metadata) registered in The National Map and Geospatial One-Stop? What
is the status of maintaining, updating and serving themes of data that
are included in *The National Map*? Based on your perspective and
project experience describe user requirements for a national level
spatial data infrastructure.

c\. Describe the operational capability to maintain and update data
through periodic updates of data made available through *The National
Map*.

d\. Discuss the issues, difficulties, and challenges (both technical,
institutional and organizational) that were encountered. How can the CAP
program be improved.

e\. Describe your relationship and issues with the USGS. Has a formal
ongoing agreement been established to provide data and web services
through *The National Map*? Describe your plans for follow-on
activities. What are the terms and mutual commitment of resources?
Please attach copy of written agreement if available.

**Attachment H**

# AGREEMENT OF PARTICIPATION

**IMPORTANT NOTICE:** The project's proposal MUST include this annex
completed and signed by EACH proposed project participant in order to be
considered responsive. Project participants include all those
participants that propose to contribute cash or in-kind to the estimated
proposed project cost.

Name and full address of Project Participant:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Agrees to participate in undertaking the Joint Canadian and American
Framework Demonstration Project described in the proposal submitted by:

**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

which proposal is entitled:

"\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_"
, and dated \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ if it is successful in being
selected for funding.

x
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

(preferably a senior level Signature)

Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Job
Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

EmailAddress:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Telephone/FaxNumber:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

[^1]: Public domain refers to works that are not protected under U.S.
    copyright law and are publicly available. Public domain materials
    may be used by anyone, anywhere in the U.S., anytime without
    permission, license, or royalty payment.

[^2]: ^,4^ Accuracy statement based on Geospatial Positioning Accuracy
    Standard, Part 3, National Standard for Spatial Data Accuracy
    (FGDC-STD-007.3-1998).
    http://www.fgdc.gov/standards/status/sub1_3.html. For horizontal
    accuracies (95% confidence level), 3 meters is commensurate with
    1:3,075-scale maps under the National Map Accuracy Standard, 4.68
    meters with 1:4,800-scale maps, 13.90 meters with 1:24,000-scale
    maps, and 36.69 meters with 1:63,360-scale maps. For vertical
    accuracy (95% confidence level), 0.73 meter is commensurate with a
    four-foot contour interval under the National Map Accuracy Standard.

[^3]: ^,5^ Estimated currentness of the data at the date of service
    initiation; that is, the data served reflects the ground condition
    sometime during the two (or five) years prior to the start of
    service through *The National Map*. (Note that, for themes in which
    the ground changes rarely, older data might meet this condition.)

[^4]:

[^5]:

[^6]: The Bureau of the Census defines an urbanized area as consisting
    of a central place(s) and adjacent territory with a general
    population density of at least 1,000 people per square mile of land
    area that together have a minimum residential population of at least
    50,000 people.

[^7]: The Bureau of the Census defines an urban cluster as a densely
    settled territory that has at least 2,500 people but fewer than
    50,000.