Image Format Clause Samples

The Image Format clause defines the specific technical requirements for the format in which images must be provided or delivered under the agreement. Typically, this clause will specify acceptable file types such as JPEG, PNG, or TIFF, and may include details about resolution, color profile, or compression standards. By clearly outlining these requirements, the clause ensures that all images are compatible with intended uses and meet quality expectations, thereby preventing misunderstandings or disputes over deliverable standards.
Image Format. You can select the save format for the scanned image. If you select Options, you can make detailed settings for each save format. The following shows the supported save formats and extensions. Note:  Some items and settings may not be available depending on the scanner you are using. Read this help for the sections that apply to your scanner.  You cannot make settings for any items in Image Format Options for PNM and PNG formats. ■PNM (*.pnm) A file format that is supported by a wide variety of Linux applications. ■JPEG (*.jpg) A file format which allows you to compress the data to be saved. If the compression ratio is high, the image quality declines, and you cannot convert the image back to the original quality. Every time you save the image, the quality declines. We recommend saving the scanned image in TIFF format when processing the image. ■PNG (*.png) A file format which allows you to compress the data to be saved. The image quality does not decline by compressing. ■TIFF (*.tif) A file format created to exchange data between various applications such as graphic software and DTP software. ■Multi-TIFF (*.tif) A file format in which you can save multiple pages as one file. You can save up to 200 pages per file. To open a Multi-TIFF file, you need an application that supports Multi-TIFF. Scanning may be interrupted depending on the number of originals, resolution settings, or the amount of free space on the hard disk. ■PDF (*.pdf) A general file format that can be used across different operating systems and provides the same level of screen display and print result. 9.4.1. Image Format Options Screen 9.4.1.1. JPEG 9.4.1.2. PDF
View SourceView Similar (2)
Image Format. Proprietary Image trailer tacked onto industry standard image format. Images may be exported to a number of formats. County DEM with up to 0.7 m spacing will be included in Image trailer. Contractor will work County to provide the most practicable postings (5m spacing may be used in National Forest areas). Testing will be done for tessellated ground plane based on provided DEM.
View SourceView Similar (2)
Image Format. Must use official form and submit original via mail or in email format in full color.
View Source
Image Format. The REDUCEME data files are stored as unformatted binary files, and they are composed by a header, which contains basic frame information, and the data records. Next, we give the simple FORTRAN code required to read and write files with this format (those files can be found in the reduceme/specials/ subdirectory): • Program simple_read: read a data file with REDUCEME format. • Program simple_write: write a data file with REDUCEME format. Let’s have a look to the file simple_read.f: PROGRAM SIMPLE_READ IMPLICIT NONE C INTEGER NCHAR INTEGER NSCAN,NCHAN REAL STWV,DISP REAL AIRMASS,TIMEXPOS REAL SPECTRA(1124,1124) CHARACTER*12 IDENTIFICATION CHARACTER*255 OBJECT CHARACTER*255 FITSFILE CHARACTER*255 COMMENT C open file OPEN(10,FILE='file000.dat',STATUS='OLD',FORM='UNFORMATTED') C read header information READ(10) IDENTIFICATION READ(10) NSCAN,NCHAN READ(10) STWV,DISP READ(10) AIRMASS READ(10) TIMEXPOS READ(10) NCHAR IF(NCHAR.GT.0) READ(10) OBJECT(1:NCHAR) READ(10) NCHAR IF(NCHAR.GT.0) READ(10) FITSFILE(1:NCHAR) READ(10) NCHAR IF(NCHAR.GT.0) READ(10) COMMENT(1:NCHAR) C read data frame DO I=1,NSCAN READ(10) (SPECTRA(J,I),J=1,NCHAN) END DO CLOSE(10) C end of program STOP END The first header element, IDENTIFICATION, is a character string (length=12 characters), which is employed by the programs to identify the data frames written in REDUCEME format. Due to historical reasons, this string was chosen to be ‘abcdefghijkl’. It is important to note that the data array SPECTRA must be dimensioned at least to the maximum expected NCHAN and NSCAN. In order to distinguish data frames from their associated error frames, we have decided to add the extra character string ' @ERROR@' (CHARACTER*8) to the OBJECT header keyword. For example: data file: file000.dat, with OBJECT='NGC 9999' –> error file: file000e.dat, with OBJECT='NGC 9999 @ERROR@'
View Source
Image Format. Proprietary Image trailer tacked onto industry standard image format. Images may be exported to a number of formats. If applicable, County DEM with up to 0.7 m spacing will be included in Image trailer. Contractor will work County to provide the most practicable postings (5m spacing may be used in National Forest areas). Testing will be done for tessellated ground plane based on provided DEM. 1.4.3 IMAGE QUALITY Images will have clear views of the ground and will be free from obstruction by clouds; however, there may be occasional cloud and other shadows. In controlled airspace, around airports, etc., the image resolutions may vary. Quality of Images will be comparable to images from previous LAR-IAC projects given comparable resolutions. 1.4.4 ACCURACY Neighborhood Oblique Images: 1. Relative Image Accuracy: Expected to be within approximately 5 meters or less over 1,000 meters. This standard assumes an accurate DEM. 2. Benchmark Accuracy: Expected to be in accordance with three (3) sample Sectors delivered by Contractor and reviewed in benchmark by County (proposed for February 2008). Observed accuracy of neighborhood oblique imagery to be within EXHIBIT A.1 – STATEMENT OF WORK – OBLIQUE IMAGES 2m from “GPS verified ground true location.” This standard assumes an accurate DEM. 3. Sensor Positional Accuracy: 30 cm absolute 4. Sensor Directional Accuracy: 0.01 degrees absolute
View Source

Related to Image Format

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇.▇▇/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Due Formation The Company is a company duly incorporated as an exempted company with limited liability, validly existing and in good standing under the laws of the Cayman Islands. The Company has all requisite power and authority to carry on its business as it is currently being conducted.