Image Format Sample Clauses

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.
Sample 1Sample 2
AutoNDA by SimpleDocs
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.
Sample 1
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) (continues on next page) 14 Chapter 1. Documentation outline (continued from previous page) 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@'
Sample 1
Image Format. Must use official form and submit original via mail or in email format in full color.
Sample 1

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.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • 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. TRAVEL, MEALS AND LODGING - LOT 4 – IMPLEMENTATION ONLY 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 xxxx://xxx.xxxxx.xx.xx/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. PERFORMANCE AND BID BONDS 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. CONTRACTOR REQUIREMENTS AND PROCEDURES FOR PARTICIPATION BY NEW YORK STATE CERTIFIED MINORITY- AND WOMEN-OWNED BUSINESS ENTERPRISES AND EQUAL EMPLOYMENT OPPORTUNITIES FOR MINORITY GROUP MEMBERS AND WOMEN I. New York State Law 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 XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-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.

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

  • Formats Formats for records must be satisfactory to FTA and include, but are not limited to, electronic records, including any emails related to the Award, records on paper, and records created in other formats.

  • Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.

  • Proposal Format a. Offerors shall submit an original of their proposals and the number of copies listed in paragraph “c” below.

Time is Money Join Law Insider Premium to draft better contracts faster.