Geospatial Guidance Clause Samples

Geospatial Guidance. SUBRECIPIENT is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospacial activities with the guidance available on the Federal Emergency Management Agency (“FEMA”) website.
View SourceView Similar (11)
Geospatial Guidance. SAN MATEO is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospatial activities with the guidance available on the FEMA website;
View SourceView Similar (3)
Geospatial Guidance. NOVATO is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospacial activities with the guidance available on the Federal Emergency Management Agency (“FEMA”) website.
View Source
Geospatial Guidance. SANTA ▇▇▇▇ is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospatial activities with the guidance available on the Federal Emergency Management Agency (“FEMA”) website.
View Source
Geospatial Guidance. MARIN is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospacial activities with the guidance available on the Federal Emergency Management Agency (“FEMA”) website.
View Source
Geospatial Guidance. ALAMEDA is encouraged to use Geospatial technologies, which can capture, store, analyze, transmit and/or display location-based information (i.e., information linked to a latitude and longitude), and to align any geospatial activities with the guidance available on the Federal Emergency Management Agency (“FEMA”) website.
View Source

Related to Geospatial Guidance

  • ICO Guidance 6.1 The Parties agree to take account of any guidance issued by the Information Commissioner and/or any relevant central government body. The Buyer may on not less than thirty (30) Working Days’ notice to the Supplier amend the contract to ensure that it complies with any guidance issued by the Information Commissioner and/or any relevant central government body.

  • TECHNICAL GUIDANCE LETTERS In the sole discretion of the System Agency, and in conformance with federal and state law, the System Agency may issue instructions, clarifications, or interpretations as may be required during work performance in the form of a Technical Guidance Letter (TGL). A TGL must be in writing, and may be delivered by regular mail, electronic mail, or facsimile transmission. Any TGL issued by the System Agency will be incorporated into the Contract by reference for all purposes when it is issued.

  • HIV/AIDS Model Workplace Guidelines Grantee will: a. implement the System Agency’s policies based on the Human Immunodeficiency Virus/Acquired Immunodeficiency Syndrome (HIV/AIDS), AIDS Model Workplace Guidelines for Businesses at ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇▇▇.▇▇.▇▇/hivstd/policy/policies.shtm, State Agencies and State Grantees Policy No. 090.021. b. educate employees and clients concerning HIV and its related conditions, including AIDS, in accordance with the Texas. Health & Safety Code §§ 85.112-114.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.