sigma consolefonts
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 13
Sigma Consolefonts 0.01
Sigma Consolefonts package contains a set of UTF-8 fonts which provide readability and wide coverage. more>>
Sigma Consolefonts package contains a set of UTF-8 fonts which provide readability and wide coverage. Actually, it is only one font, in an 8x16 size but with a number of variations of what gets mapped into the (psfu) consolefont. If you arent using Linux and a UTF-8 locale, this probably will not have any relevance to you.
Still interested ? Ok, here is a less than wonderful photograph of what the sigma-general version of this font can do. Apologies for the poor quality of the photo, I hope you can get an idea of what this does - and if you are using the linux console without a graphical desktop, youll just have to download it to try it out.
I aim to let people see as many characters as possible on their console. I know that most people assume a graphical desktop is necessary to see a wide range of characters, but the standard console can display 512 characters if you do without the bold colours.
Traditional console fonts have often used separate glyphs for cyrillic and latin letters of the same shape, but desktop fonts normally render them identically (e.g. latin A and cyrillic А), and so do I - this helps make some space available. I have used Dmitry Bolkhovityanovs perl script to select which glyphs are used in a particular psfu font, and to map multiple codepoints to the same glyph. There are a limited range of line-drawing characters (enough to give a decent display in the linux kernels make menuconfig).
The main use of these fonts is when you dont have a graphical desktop but still want to be able to read text in many languages. So, perhaps they are most appropriate to people running servers. For myself, they let me read my mail over ssh when I am building the graphical desktop for a new system.
The font itself started out as etl16 from one of the debian console packages. I altered it to give more balanced letters - longer descenders at the expense of less space above the letters, and bringing the accents closer to the letter. The cell format of a capital letter is 3 rows above the letter, 10 rows for the letter, and another 3 rows for the descender. In hex, that is 3A3, hence the name (U+03A3 is Σ).
Unlike traditional vga fonts hard-coded into the machine, these fonts are much less bright - you may have to increase your screens brightness. This is because they are thin (normally only one pixel wide). The 8x16 size is very much "one size fits all" - adequate for most accented latin, and for cyrillic and current greek, but not ideal where there are multiple accents (livonian, vietnamese, polytonic greek).
Unlike most other console fonts, these come with the source (a bdf font) and a series of map files to decide what to include. So, if you really dislike the form of one of the letters you can alter it - the bdf is just 16 lines of hex codes, e.g. a capital U has nine lines of x42 (0100 0010) and a baseline of x3C (0011 1100).
If you want to change a map, either to add something else, or to remove something you dont use, they are simple to edit.
The linux console cannot accomodate CJK languages, so this font is for people who use alphabetic languages. The armenian and georgian glyphs should be identical to what is in etl16, also the arabic and hebrew (and I really dont know how useful those are on a left-to-right terminal). Everything else has been tweaked to provide what I think is a satisfactory result.
The tarball includes my attempt at listing the alphabets for the languages covered - to answer the question, which glyphs do you need for a particular language. These files may also be useful if you are using xorg and want to check whether your fonts provide adequate coverage.
For most people, I think the general version should work well (latin, greek and the main european cyrillic letters). Some people may prefer the cyrillic variant (all current cyrillic, greek, some latin letters. There is also a caucasian variant (latin, cyrillic, armenian, georgian) and some other example and proof-of-concept variants, e.g. african, polytonic, vietnamese. Ultimately, the african languages are limited by a lack of precomposed glyphs in unicode (AFAIK, there is a lack of terminals which support combining diacriticals), but some languages such as venda should work. Languages with multiple accents above the letter (livonian, polytonic greek, vietnamese) are not wonderful in the 8x16 size, but they might suffice.
<<lessStill interested ? Ok, here is a less than wonderful photograph of what the sigma-general version of this font can do. Apologies for the poor quality of the photo, I hope you can get an idea of what this does - and if you are using the linux console without a graphical desktop, youll just have to download it to try it out.
I aim to let people see as many characters as possible on their console. I know that most people assume a graphical desktop is necessary to see a wide range of characters, but the standard console can display 512 characters if you do without the bold colours.
Traditional console fonts have often used separate glyphs for cyrillic and latin letters of the same shape, but desktop fonts normally render them identically (e.g. latin A and cyrillic А), and so do I - this helps make some space available. I have used Dmitry Bolkhovityanovs perl script to select which glyphs are used in a particular psfu font, and to map multiple codepoints to the same glyph. There are a limited range of line-drawing characters (enough to give a decent display in the linux kernels make menuconfig).
The main use of these fonts is when you dont have a graphical desktop but still want to be able to read text in many languages. So, perhaps they are most appropriate to people running servers. For myself, they let me read my mail over ssh when I am building the graphical desktop for a new system.
The font itself started out as etl16 from one of the debian console packages. I altered it to give more balanced letters - longer descenders at the expense of less space above the letters, and bringing the accents closer to the letter. The cell format of a capital letter is 3 rows above the letter, 10 rows for the letter, and another 3 rows for the descender. In hex, that is 3A3, hence the name (U+03A3 is Σ).
Unlike traditional vga fonts hard-coded into the machine, these fonts are much less bright - you may have to increase your screens brightness. This is because they are thin (normally only one pixel wide). The 8x16 size is very much "one size fits all" - adequate for most accented latin, and for cyrillic and current greek, but not ideal where there are multiple accents (livonian, vietnamese, polytonic greek).
Unlike most other console fonts, these come with the source (a bdf font) and a series of map files to decide what to include. So, if you really dislike the form of one of the letters you can alter it - the bdf is just 16 lines of hex codes, e.g. a capital U has nine lines of x42 (0100 0010) and a baseline of x3C (0011 1100).
If you want to change a map, either to add something else, or to remove something you dont use, they are simple to edit.
The linux console cannot accomodate CJK languages, so this font is for people who use alphabetic languages. The armenian and georgian glyphs should be identical to what is in etl16, also the arabic and hebrew (and I really dont know how useful those are on a left-to-right terminal). Everything else has been tweaked to provide what I think is a satisfactory result.
The tarball includes my attempt at listing the alphabets for the languages covered - to answer the question, which glyphs do you need for a particular language. These files may also be useful if you are using xorg and want to check whether your fonts provide adequate coverage.
For most people, I think the general version should work well (latin, greek and the main european cyrillic letters). Some people may prefer the cyrillic variant (all current cyrillic, greek, some latin letters. There is also a caucasian variant (latin, cyrillic, armenian, georgian) and some other example and proof-of-concept variants, e.g. african, polytonic, vietnamese. Ultimately, the african languages are limited by a lack of precomposed glyphs in unicode (AFAIK, there is a lack of terminals which support combining diacriticals), but some languages such as venda should work. Languages with multiple accents above the letter (livonian, polytonic greek, vietnamese) are not wonderful in the 8x16 size, but they might suffice.
Download (0.080MB)
Added: 2007-08-13 License: BSD License Price:
808 downloads
Warcraft Sigma Style Icons for Linux 1
Transparent Background, 24 Bits color, 8 bits shadow more>> PNG (Transparent Background, 24 Bits color, 8 bits shadow) ICO (Windows Icons) ICNS (Mac icons) Sizes: 256x256, 128x128, 48x48, 32x32, 24x24, 16x16<<less
Download (483KB)
Added: 2009-04-07 License: Freeware Price: Free
203 downloads
Sigma Six 1.06
Six Sigma is a formalized methodology which some companies use to measure and delivery quality to their customers. more>>
Six Sigma project is a formalized methodology which some companies use to measure and delivery quality to their customers.
Companies who participate in Six Sigma programs strive for a statistical goal of six standard deviations between the mean and the closest specification limit for whatever process is being measured.
This translates to a permissible defect or error rate of just 3.4 errors or defects of out of every 1 million "opportunities" to create that error or defect, or a success rate of 99.9997%.
How did Six Sigma originate?
A Motorola Corporation Quality and Reliability engineer by the name of Bill Smith is widely credited with devising the Six Sigma process. He had concluded a study which determined that actual Motorola product failure rates were much higher than had been predicted when the products were designed. The high failure rates translated into additional warranty repair costs for Motorola and decreased customer satisfaction.
Mr. Smith went to Motorolas CEO and convinced him that the company would benefit financially from a formalized methodology which analyzed and controlled quality and reliability processes. This process became what is known as Six Sigma.
Does Six Sigma work?
There are many large and small businesses who have implemented Six Sigma programs successfully. It is reported that the General Electric Corporation saved over $10 billion dollars in the first five years after implementing their Six Sigma program.
Enhancements:
- The CSS had a few bugs in the syntax that caused some minor display problems.
<<lessCompanies who participate in Six Sigma programs strive for a statistical goal of six standard deviations between the mean and the closest specification limit for whatever process is being measured.
This translates to a permissible defect or error rate of just 3.4 errors or defects of out of every 1 million "opportunities" to create that error or defect, or a success rate of 99.9997%.
How did Six Sigma originate?
A Motorola Corporation Quality and Reliability engineer by the name of Bill Smith is widely credited with devising the Six Sigma process. He had concluded a study which determined that actual Motorola product failure rates were much higher than had been predicted when the products were designed. The high failure rates translated into additional warranty repair costs for Motorola and decreased customer satisfaction.
Mr. Smith went to Motorolas CEO and convinced him that the company would benefit financially from a formalized methodology which analyzed and controlled quality and reliability processes. This process became what is known as Six Sigma.
Does Six Sigma work?
There are many large and small businesses who have implemented Six Sigma programs successfully. It is reported that the General Electric Corporation saved over $10 billion dollars in the first five years after implementing their Six Sigma program.
Enhancements:
- The CSS had a few bugs in the syntax that caused some minor display problems.
Download (0.23MB)
Added: 2006-03-03 License: Other/Proprietary License with Source Price:
1330 downloads
Radar Tools 0.18
Radar Tools is an advanced SAR remote sensing image processing software. more>>
Radar Tools in short RAT is a small collection of tools for processing SAR (synthetic aperture radar) remote sensing data, packed together in a nice graphical user interface.
Our motivation to start the development of RAT is that modern remote sensing software like Erdas Image or ENVI include only some basic SAR functionality. Advanced algorithms have to be implemented by oneself.
So we descided to start the development of RAT. RAT should bring modern SAR algorithms to a wider user-base by simplifying in particular the data handling and processing of complex SAR data.
RAT is planned as an ongoing community effort, i.e. there will be no final version with a certain functionality. It is our idea to include more and more SAR tools in future and to make them freely available to the scientific community.
We of course also hope for external contributions. Because of this, the programming interface of RAT is kept quite simple and adding own functions is quite easy. Function templates are included in the distribution and a step-by-step description of how to program a RAT module will appear soon in the documentation.
Main features:
General features
- Cross-platform (Unix, Windows, Linux & Mac OSX)
- Free software, no commercial software license needed (when using the IDL-VM version)
- Availability of the complete source code
- Modular design, easy to extend by own functions
- Small memory footprint even when processing large images (vertical tiling)
- No limitation on the image size
- Keep track of data representation changes during image processing
- Optimised preview on screen while calculations are done in full resolution
- Native import routines for E-SAR (DLR) and ENVISAT-IMS (ESA) data
- Export possibility to generic graphic formats (png, jpg & tiff)
- Undo function for the last processing step
Generic image manipulation
- Resize, presumming & cut region
- Zooming of an area of interest
- Mirror vertical and horizontal
- Binary transforms
Single channel SAR
- SAR speckle filtering (Boxcar, Median, Gauss, Kuan, Frost, MAP Lee, refined Lee, Lee-Sigma)
- Edge detection (RoA, MSP-RoA, Sobel, Roberts)
- Co-occurance texture features, variation coefficient
- Point and distributed target analysis
- Generic slant-to-ground range projection
SAR polarimetry
- Polarimetric point target analysis
- Polarimetric speckle filtering (Boxcar, Lee, refined Lee)
- Polarimetric CFSAR edge detection
- Calculation of interchannel ratios, correlation & phase differences
- Formation of covariance and coherency matrix, span calculation
- Polarimetric basis transforms (linear -> circular ....)
- Decompositions (Pauli, Freman-Durdan, Moriyama, Entropy/Alpha, Eigenvalue, Sphere-Diplane-Helix....)
- Polarimetric classification (Entropy/Alpha/Anisotropy, Wishart, No. of scatterers, physical, Lee category preserving...)
- Polarimetric calibration: imbalance, symmetrisation & crosstalk (Quegan method)
SAR interferometry
- Image pair coregistration (coarse, subpixel & spatially varying)
- Interferogram formation
- Flat-earth removal
- Phase-unwrapping (least-squares only)
- Phase noise filter (Boxcar, Goldstein & GLSME)
- Coherence estimation (Boxcar, Gauss, Region Growing)
- Shaded relief calculation
Polarimetric SAR interferometry
- Formation of POLINSAR covariance and coherency matrices
- Coherence estimation & optimisation
- Extraction of optimised ESPRIT phases
- POLINSAR speckle filtering (Boxcar, Gauss & Lee)
- Coherence analysis in the complex unitary plane
<<lessOur motivation to start the development of RAT is that modern remote sensing software like Erdas Image or ENVI include only some basic SAR functionality. Advanced algorithms have to be implemented by oneself.
So we descided to start the development of RAT. RAT should bring modern SAR algorithms to a wider user-base by simplifying in particular the data handling and processing of complex SAR data.
RAT is planned as an ongoing community effort, i.e. there will be no final version with a certain functionality. It is our idea to include more and more SAR tools in future and to make them freely available to the scientific community.
We of course also hope for external contributions. Because of this, the programming interface of RAT is kept quite simple and adding own functions is quite easy. Function templates are included in the distribution and a step-by-step description of how to program a RAT module will appear soon in the documentation.
Main features:
General features
- Cross-platform (Unix, Windows, Linux & Mac OSX)
- Free software, no commercial software license needed (when using the IDL-VM version)
- Availability of the complete source code
- Modular design, easy to extend by own functions
- Small memory footprint even when processing large images (vertical tiling)
- No limitation on the image size
- Keep track of data representation changes during image processing
- Optimised preview on screen while calculations are done in full resolution
- Native import routines for E-SAR (DLR) and ENVISAT-IMS (ESA) data
- Export possibility to generic graphic formats (png, jpg & tiff)
- Undo function for the last processing step
Generic image manipulation
- Resize, presumming & cut region
- Zooming of an area of interest
- Mirror vertical and horizontal
- Binary transforms
Single channel SAR
- SAR speckle filtering (Boxcar, Median, Gauss, Kuan, Frost, MAP Lee, refined Lee, Lee-Sigma)
- Edge detection (RoA, MSP-RoA, Sobel, Roberts)
- Co-occurance texture features, variation coefficient
- Point and distributed target analysis
- Generic slant-to-ground range projection
SAR polarimetry
- Polarimetric point target analysis
- Polarimetric speckle filtering (Boxcar, Lee, refined Lee)
- Polarimetric CFSAR edge detection
- Calculation of interchannel ratios, correlation & phase differences
- Formation of covariance and coherency matrix, span calculation
- Polarimetric basis transforms (linear -> circular ....)
- Decompositions (Pauli, Freman-Durdan, Moriyama, Entropy/Alpha, Eigenvalue, Sphere-Diplane-Helix....)
- Polarimetric classification (Entropy/Alpha/Anisotropy, Wishart, No. of scatterers, physical, Lee category preserving...)
- Polarimetric calibration: imbalance, symmetrisation & crosstalk (Quegan method)
SAR interferometry
- Image pair coregistration (coarse, subpixel & spatially varying)
- Interferogram formation
- Flat-earth removal
- Phase-unwrapping (least-squares only)
- Phase noise filter (Boxcar, Goldstein & GLSME)
- Coherence estimation (Boxcar, Gauss, Region Growing)
- Shaded relief calculation
Polarimetric SAR interferometry
- Formation of POLINSAR covariance and coherency matrices
- Coherence estimation & optimisation
- Extraction of optimised ESPRIT phases
- POLINSAR speckle filtering (Boxcar, Gauss & Lee)
- Coherence analysis in the complex unitary plane
Download (2.5MB)
Added: 2007-04-02 License: Freeware Price:
952 downloads
Statistics::LineFit 0.07
Statistics::LineFit module least squares line fit, weighted or unweighted. more>>
Statistics::LineFit module least squares line fit, weighted or unweighted.
SYNOPSIS
use Statistics::LineFit;
$lineFit = Statistics::LineFit->new();
$lineFit->setData (@xValues, @yValues) or die "Invalid data";
($intercept, $slope) = $lineFit->coefficients();
defined $intercept or die "Cant fit line if x values are all equal";
$rSquared = $lineFit->rSquared();
$meanSquaredError = $lineFit->meanSqError();
$durbinWatson = $lineFit->durbinWatson();
$sigma = $lineFit->sigma();
($tStatIntercept, $tStatSlope) = $lineFit->tStatistics();
@predictedYs = $lineFit->predictedYs();
@residuals = $lineFit->residuals();
(varianceIntercept, $varianceSlope) = $lineFit->varianceOfEstimates();
The Statistics::LineFit module does weighted or unweighted least-squares line fitting to two-dimensional data (y = a + b * x). (This is also called linear regression.) In addition to the slope and y-intercept, the module can return the square of the correlation coefficient (R squared), the Durbin-Watson statistic, the mean squared error, sigma, the t statistics, the variance of the estimates of the slope and y-intercept, the predicted y values and the residuals of the y values. (See the METHODS section for a description of these statistics.)
The module accepts input data in separate x and y arrays or a single 2-D array (an array of arrayrefs). The optional weights are input in a separate array. The module can optionally verify that the input data and weights are valid numbers. If weights are input, the line fit minimizes the weighted sum of the squared errors and the following statistics are weighted: the correlation coefficient, the Durbin-Watson statistic, the mean squared error, sigma and the t statistics.
The module is state-oriented and caches its results. Once you call the setData() method, you can call the other methods in any order or call a method several times without invoking redundant calculations. After calling setData(), you can modify the input data or weights without affecting the modules results.
The decision to use or not use weighting could be made using your a priori knowledge of the data or using supplemental data. If the data is sparse or contains non-random noise, weighting can degrade the solution. Weighting is a good option if some points are suspect or less relevant (e.g., older terms in a time series, points that are known to have more noise).
<<lessSYNOPSIS
use Statistics::LineFit;
$lineFit = Statistics::LineFit->new();
$lineFit->setData (@xValues, @yValues) or die "Invalid data";
($intercept, $slope) = $lineFit->coefficients();
defined $intercept or die "Cant fit line if x values are all equal";
$rSquared = $lineFit->rSquared();
$meanSquaredError = $lineFit->meanSqError();
$durbinWatson = $lineFit->durbinWatson();
$sigma = $lineFit->sigma();
($tStatIntercept, $tStatSlope) = $lineFit->tStatistics();
@predictedYs = $lineFit->predictedYs();
@residuals = $lineFit->residuals();
(varianceIntercept, $varianceSlope) = $lineFit->varianceOfEstimates();
The Statistics::LineFit module does weighted or unweighted least-squares line fitting to two-dimensional data (y = a + b * x). (This is also called linear regression.) In addition to the slope and y-intercept, the module can return the square of the correlation coefficient (R squared), the Durbin-Watson statistic, the mean squared error, sigma, the t statistics, the variance of the estimates of the slope and y-intercept, the predicted y values and the residuals of the y values. (See the METHODS section for a description of these statistics.)
The module accepts input data in separate x and y arrays or a single 2-D array (an array of arrayrefs). The optional weights are input in a separate array. The module can optionally verify that the input data and weights are valid numbers. If weights are input, the line fit minimizes the weighted sum of the squared errors and the following statistics are weighted: the correlation coefficient, the Durbin-Watson statistic, the mean squared error, sigma and the t statistics.
The module is state-oriented and caches its results. Once you call the setData() method, you can call the other methods in any order or call a method several times without invoking redundant calculations. After calling setData(), you can modify the input data or weights without affecting the modules results.
The decision to use or not use weighting could be made using your a priori knowledge of the data or using supplemental data. If the data is sparse or contains non-random noise, weighting can degrade the solution. Weighting is a good option if some points are suspect or less relevant (e.g., older terms in a time series, points that are known to have more noise).
Download (0.024MB)
Added: 2007-07-12 License: Perl Artistic License Price:
835 downloads
Statistics::OLS 0.07
Statistics::OLS is a Perl module to perform ordinary least squares and associated statistics. more>>
Statistics::OLS is a Perl module to perform ordinary least squares and associated statistics.
SYNOPSIS
use Statistics::OLS;
my $ls = Statistics::OLS->new();
$ls->setData (@xydataset) or die( $ls->error() );
$ls->setData (@xdataset, @ydataset);
$ls->regress();
my ($intercept, $slope) = $ls->coefficients();
my $R_squared = $ls->rsq();
my ($tstat_intercept, $tstat_slope) = $ls->tstats();
my $sigma = $ls->sigma();
my $durbin_watson = $ls->dw();
my $sample_size = $ls->size();
my ($avX, $avY) = $ls->av();
my ($varX, $varY, $covXY) = $ls->var();
my ($xmin, $xmax, $ymin, $ymax) = $ls->minMax();
# returned arrays are x-y or y-only data
# depending on initial call to setData()
my @predictedYs = $ls->predicted();
my @residuals = $ls->residuals();
I wrote Statistics::OLS to perform Ordinary Least Squares (linear curve fitting) on two dimensional data: y = a + bx. The other simple statistical module I found on CPAN (Statistics::Descriptive) is designed for univariate analysis. It accomodates OLS, but somewhat inflexibly and without rich bivariate statistics. Nevertheless, it might make sense to fold OLS into that module or a supermodule someday.
Statistics::OLS computes the estimated slope and intercept of the regression line, their T-statistics, R squared, standard error of the regression and the Durbin-Watson statistic. It can also return the residuals.
It is pretty simple to do two dimensional least squares, but much harder to do multiple regression, so OLS is unlikely ever to work with multiple independent variables.
This is a beta code and has not been extensively tested. It has worked on a few published datasets. Feedback is welcome, particularly if you notice an error or try it with known results that are not reproduced correctly.
<<lessSYNOPSIS
use Statistics::OLS;
my $ls = Statistics::OLS->new();
$ls->setData (@xydataset) or die( $ls->error() );
$ls->setData (@xdataset, @ydataset);
$ls->regress();
my ($intercept, $slope) = $ls->coefficients();
my $R_squared = $ls->rsq();
my ($tstat_intercept, $tstat_slope) = $ls->tstats();
my $sigma = $ls->sigma();
my $durbin_watson = $ls->dw();
my $sample_size = $ls->size();
my ($avX, $avY) = $ls->av();
my ($varX, $varY, $covXY) = $ls->var();
my ($xmin, $xmax, $ymin, $ymax) = $ls->minMax();
# returned arrays are x-y or y-only data
# depending on initial call to setData()
my @predictedYs = $ls->predicted();
my @residuals = $ls->residuals();
I wrote Statistics::OLS to perform Ordinary Least Squares (linear curve fitting) on two dimensional data: y = a + bx. The other simple statistical module I found on CPAN (Statistics::Descriptive) is designed for univariate analysis. It accomodates OLS, but somewhat inflexibly and without rich bivariate statistics. Nevertheless, it might make sense to fold OLS into that module or a supermodule someday.
Statistics::OLS computes the estimated slope and intercept of the regression line, their T-statistics, R squared, standard error of the regression and the Durbin-Watson statistic. It can also return the residuals.
It is pretty simple to do two dimensional least squares, but much harder to do multiple regression, so OLS is unlikely ever to work with multiple independent variables.
This is a beta code and has not been extensively tested. It has worked on a few published datasets. Feedback is welcome, particularly if you notice an error or try it with known results that are not reproduced correctly.
Download (0.008MB)
Added: 2007-05-23 License: Perl Artistic License Price:
531 downloads
Image::ExifTool 6.42
Image::ExifTool is a Perl module that can read and write meta information. more>>
Image::ExifTool is a Perl module that can read and write meta information.
SYNOPSIS
use Image::ExifTool ImageInfo;
# ---- Simple procedural usage ----
# Get hash of meta information tag names/values from an image
$info = ImageInfo(a.jpg);
# ---- Object-oriented usage ----
# Create a new Image::ExifTool object
$exifTool = new Image::ExifTool;
# Extract meta information from an image
$exifTool->ExtractInfo($file, %options);
# Get list of tags in the order they were found in the file
@tagList = $exifTool->GetFoundTags(File);
# Get the value of a specified tag
$value = $exifTool->GetValue($tag, $type);
# Get a tag description
$description = $exifTool->GetDescription($tag);
# Get the group name associated with this tag
$group = $exifTool->GetGroup($tag, $family);
# Set a new value for a tag
$exifTool->SetNewValue($tag, $newValue);
# Write new meta information to a file
$success = $exifTool->WriteInfo($srcfile, $dstfile);
# ...plus a host of other useful methods...
ExifTool provides an extensible set of perl modules to read and write meta information in image, audio and video files, including the maker note information of many digital cameras by various manufacturers such as Canon, Casio, FujiFilm, JVC/Victor, Kodak, Leaf, Minolta/Konica-Minolta, Nikon, Olympus/Epson, Panasonic/Leica, Pentax/Asahi, Ricoh, Sanyo and Sigma/Foveon.
<<lessSYNOPSIS
use Image::ExifTool ImageInfo;
# ---- Simple procedural usage ----
# Get hash of meta information tag names/values from an image
$info = ImageInfo(a.jpg);
# ---- Object-oriented usage ----
# Create a new Image::ExifTool object
$exifTool = new Image::ExifTool;
# Extract meta information from an image
$exifTool->ExtractInfo($file, %options);
# Get list of tags in the order they were found in the file
@tagList = $exifTool->GetFoundTags(File);
# Get the value of a specified tag
$value = $exifTool->GetValue($tag, $type);
# Get a tag description
$description = $exifTool->GetDescription($tag);
# Get the group name associated with this tag
$group = $exifTool->GetGroup($tag, $family);
# Set a new value for a tag
$exifTool->SetNewValue($tag, $newValue);
# Write new meta information to a file
$success = $exifTool->WriteInfo($srcfile, $dstfile);
# ...plus a host of other useful methods...
ExifTool provides an extensible set of perl modules to read and write meta information in image, audio and video files, including the maker note information of many digital cameras by various manufacturers such as Canon, Casio, FujiFilm, JVC/Victor, Kodak, Leaf, Minolta/Konica-Minolta, Nikon, Olympus/Epson, Panasonic/Leica, Pentax/Asahi, Ricoh, Sanyo and Sigma/Foveon.
Download (1.0MB)
Added: 2006-11-16 License: Perl Artistic License Price:
1075 downloads
libsift 1.8
libsift is an algorithm to identify and locate interesting points within an image. more>>
libsift is an algorithm to identify and locate interesting points within an image. For all such points, a descriptive signature is extracted.
The signatures can be stored and matched among multiple images, allowing for a large number of interesting applications, such as aligning overlapping images and identifying objects or motion within image sequences.
libsift is used by the autopano-sift program to create panorama images.
This library is a 100% C# implementation of the SIFT algorithm ("Scale-Invariant Feature Transform") and additional matching algorithms. The SIFT algorithm is an image feature location and extraction algorithm which provides the following key advantages over similar algorithms:
- Combined feature location and extraction algorithm.
- The keypoint locations are more precise and repeatable, because SIFT uses subpixel localization and multiple scale keypoint identification
- The descriptors are highly distinctive. For example, I tested with up to 300,000 keypoints while matching a large 60 picture panorama and it did not have a single invalid match.
- The feature vectors can be efficiently correlated using probabilistic algorithms like Best-Bin-First kd-tree search.
Enhancements:
- A serious bug in the Gaussian sigma computation and a bug in the DoG scale handling were fixed.
<<lessThe signatures can be stored and matched among multiple images, allowing for a large number of interesting applications, such as aligning overlapping images and identifying objects or motion within image sequences.
libsift is used by the autopano-sift program to create panorama images.
This library is a 100% C# implementation of the SIFT algorithm ("Scale-Invariant Feature Transform") and additional matching algorithms. The SIFT algorithm is an image feature location and extraction algorithm which provides the following key advantages over similar algorithms:
- Combined feature location and extraction algorithm.
- The keypoint locations are more precise and repeatable, because SIFT uses subpixel localization and multiple scale keypoint identification
- The descriptors are highly distinctive. For example, I tested with up to 300,000 keypoints while matching a large 60 picture panorama and it did not have a single invalid match.
- The feature vectors can be efficiently correlated using probabilistic algorithms like Best-Bin-First kd-tree search.
Enhancements:
- A serious bug in the Gaussian sigma computation and a bug in the DoG scale handling were fixed.
Download (0.15MB)
Added: 2006-01-21 License: GPL (GNU General Public License) Price:
1374 downloads
Unicode::Overload 0.01
Unicode::Overload is a Perl source filter to implement Unicode operations. more>>
Unicode::Overload is a Perl source filter to implement Unicode operations.
SYNOPSIS
use charnames :full;
use Unicode::Overload (
"N{UNION}" => infix =>
sub { my %a = map{$_=>1}@{$_[0]};
my %b = map{$_=>1}@{$_[1]};
return keys(%a,$b); },
"N{SUPERSCRIPT TWO}" => postfix => sub { $_[0] ** 2 },
"N{NOT SIGN}" => prefix => sub { !$_[0] },
[ "N{LEFT FLOOR}", "N{RIGHT FLOOR}" ] => outfix =>
sub { POSIX::floor($_[0]) },
);
@union = (@a N{UNION @b); # Parentheses REQUIRED
die "Pythagoras was WRONG!" # Same here
unless sqrt((3)N{SUPERSCRIPT TWO} + (4)N{SUPERSCRIPT TWO}) == 5;
$b = N{NOT SIGN}($b); # Required here too
die "Fell through floor" # Balanced characters form their own parentheses
unless N{LEFT FLOOR}-3.2N{RIGHT FLOOR} == 4;
Allows you to declare your own Unicode operators and have them behave as prefix (like sigma or integral), postfix (like superscripted 2), infix (like union), or outfix (like the floor operator, with the L-like and J-like brackets).
To keep this document friendly to people without UTF-8 terminals, the N{} syntax for Unicode characters will be used throughout, but please note that the N{} characters can be replaced with the actual UTF-8 characters anywhere.
Also, please note that since Perl 5 doesnt support the notion of arbitrary operators, this module cheats and uses source filters to do its job. As such, all "operators" must have their arguments enclosed in parentheses. This limitation will be lifted when a better way to do this is found.
Also, note that since these arent "real" operators there is no way (at the moment) to specify precedence. All Unicode "operators" have the precedence (such as it is) of function calls, as they all get transformed into function calls inline before interpreting.
In addition, due to a weird unicode-related bug, only one character per operator is currently permitted. Despite behaving correctly elsewhere, substr() thinks that one character equals one byte inside Unicode::Overload .
Anyway, this module defines four basic types of operators. Prefix and infix should be familiar to most users of perl, as prefix operators are basically function calls without the parens. Infix operators are of course the familiar + etcetera.
The best analogy for postfix operators is probably the algebraic notation for squares. $a**2 is perls notation, ($a)N{SUPERSCRIPT TWO} is the Unicode::Overload equivalent, looking much closer to a mathematical expression, with the 2 in its proper position.
Outfix is the last operator, and a little odd. Outfix can best be thought of as user-definable brackets. One of the more common uses for this notation again comes from mathematics in the guise of the floor operator. Looking like brackets with the top bar missing, they return effectively POSIX::floor() of their contents.
Since outfix operators define their own brackets, extra parentheses are not needed on this type of operator.
A quick summary follows:
prefix
Operator goes directly before the parentheses containing its operands. Whitespace is allowed between the operator and opening parenthesis. This acts like a function call.
Sample: N{NOT SIGN}($b)
postfix
Operator goes directly after the parentheses containing its operands. Whitespace is allowed between the closing parenthesis and operator. This doesnt have a good Perl equivalent, but there are many equivalents in algebra, probably the most common being:
Sample: ($a+$b)N{SUPERSCRIPT TWO}
infix
Operator goes somewhere inside the parentheses. Whitespace is allowed between either parenthesis and the operator.
Sample: ($a N{ELEMENT OF} @list)
outfix
Operators surround their arguments and are translated into parentheses. As such, whitespace is allowed anywhere inside the operator pairs. There is no requirement that the operators be visually symmetrical, although it helps.
Sampe: $c=N{LEFT FLOOR}$a_+$bN{RIGHT FLOOR}
The requirements for parentheses will be removed as soon as I can figure out how to make these operators behave closer to perl builtins. Nesting is perfectly legal, but multiple infix operators cant coexists within one set of parentheses.
<<lessSYNOPSIS
use charnames :full;
use Unicode::Overload (
"N{UNION}" => infix =>
sub { my %a = map{$_=>1}@{$_[0]};
my %b = map{$_=>1}@{$_[1]};
return keys(%a,$b); },
"N{SUPERSCRIPT TWO}" => postfix => sub { $_[0] ** 2 },
"N{NOT SIGN}" => prefix => sub { !$_[0] },
[ "N{LEFT FLOOR}", "N{RIGHT FLOOR}" ] => outfix =>
sub { POSIX::floor($_[0]) },
);
@union = (@a N{UNION @b); # Parentheses REQUIRED
die "Pythagoras was WRONG!" # Same here
unless sqrt((3)N{SUPERSCRIPT TWO} + (4)N{SUPERSCRIPT TWO}) == 5;
$b = N{NOT SIGN}($b); # Required here too
die "Fell through floor" # Balanced characters form their own parentheses
unless N{LEFT FLOOR}-3.2N{RIGHT FLOOR} == 4;
Allows you to declare your own Unicode operators and have them behave as prefix (like sigma or integral), postfix (like superscripted 2), infix (like union), or outfix (like the floor operator, with the L-like and J-like brackets).
To keep this document friendly to people without UTF-8 terminals, the N{} syntax for Unicode characters will be used throughout, but please note that the N{} characters can be replaced with the actual UTF-8 characters anywhere.
Also, please note that since Perl 5 doesnt support the notion of arbitrary operators, this module cheats and uses source filters to do its job. As such, all "operators" must have their arguments enclosed in parentheses. This limitation will be lifted when a better way to do this is found.
Also, note that since these arent "real" operators there is no way (at the moment) to specify precedence. All Unicode "operators" have the precedence (such as it is) of function calls, as they all get transformed into function calls inline before interpreting.
In addition, due to a weird unicode-related bug, only one character per operator is currently permitted. Despite behaving correctly elsewhere, substr() thinks that one character equals one byte inside Unicode::Overload .
Anyway, this module defines four basic types of operators. Prefix and infix should be familiar to most users of perl, as prefix operators are basically function calls without the parens. Infix operators are of course the familiar + etcetera.
The best analogy for postfix operators is probably the algebraic notation for squares. $a**2 is perls notation, ($a)N{SUPERSCRIPT TWO} is the Unicode::Overload equivalent, looking much closer to a mathematical expression, with the 2 in its proper position.
Outfix is the last operator, and a little odd. Outfix can best be thought of as user-definable brackets. One of the more common uses for this notation again comes from mathematics in the guise of the floor operator. Looking like brackets with the top bar missing, they return effectively POSIX::floor() of their contents.
Since outfix operators define their own brackets, extra parentheses are not needed on this type of operator.
A quick summary follows:
prefix
Operator goes directly before the parentheses containing its operands. Whitespace is allowed between the operator and opening parenthesis. This acts like a function call.
Sample: N{NOT SIGN}($b)
postfix
Operator goes directly after the parentheses containing its operands. Whitespace is allowed between the closing parenthesis and operator. This doesnt have a good Perl equivalent, but there are many equivalents in algebra, probably the most common being:
Sample: ($a+$b)N{SUPERSCRIPT TWO}
infix
Operator goes somewhere inside the parentheses. Whitespace is allowed between either parenthesis and the operator.
Sample: ($a N{ELEMENT OF} @list)
outfix
Operators surround their arguments and are translated into parentheses. As such, whitespace is allowed anywhere inside the operator pairs. There is no requirement that the operators be visually symmetrical, although it helps.
Sampe: $c=N{LEFT FLOOR}$a_+$bN{RIGHT FLOOR}
The requirements for parentheses will be removed as soon as I can figure out how to make these operators behave closer to perl builtins. Nesting is perfectly legal, but multiple infix operators cant coexists within one set of parentheses.
Download (0.005MB)
Added: 2007-07-12 License: Perl Artistic License Price:
834 downloads
Image::MetaData::JPEG::MakerNotes 0.15
Image::MetaData::JPEG::MakerNotes contains random information and details on MakerNotes. more>>
Image::MetaData::JPEG::MakerNotes contains random information and details on MakerNotes.
Pieces of information available after parsing the MakerNote
The result of the process of parsing the maker note is stored in a directory in the internal data structure for the APP1 Segment, whose path is "IFD@SubIFD@MakerNoteData_$format", where $format is the specific note format; the MakerNote entry in IFD0@SubIFD is then removed. This translation happens always, because there is a catch-all unknown rule for a binary makernote with very broad acceptance rules. The maker note directory contains, in addition, a special subdir with some fields reporting about the parsing process.
key content
-------- -------
ORIGINAL the raw content of the maker note (unparsed)
SIGNATURE the first few bytes which allowed the format to be chosen
ENDIANNESS the byte order chosen during parsing
FORMAT the maker note format chosen during parsing
ERROR [optional] error details, in case of failure while parsing
Supported MakerNote formats
Maker note formats are specified in a special internal hash, with a key for each format (including the unknown format). Each format entry corresponds to an anonymous hash containing information for parsing the MakerNote; the "normal" format is considered to be an IFD-like MakerNote with a next_link pointer, offsets counted from the global TIFF header and no MakerNote internal TIFF header.
key meaning or effect
--------- -----------------
signature the MakerNote signature (a regular expression)
maker the Maker signature (i.e., its name, no regex)
tags a reference to a hash for tag translations
(A) mkntstart if set, offsets are counted from the maker note start
(B) mkntTIFF if set, offsets are counted from the internal TIFF header
(C) ignore if set, the format is to be ignored
(D) nonext if set, the maker note IFD does not have a next_link
(E) endianness if set, the byte order is fixed to this value
(F) nonIFD if set, the maker note is not IFD-like
Currently, "supported" formats are described in the following table; authoritative data is indeed kept in Tables_makernotes.pl, to which the reader should refer for tag definitions and translations. Remember that both the signature and the maker fields are regular expressions matching at the beginning (the real signature corresponds to $1).
A B C D E F Maker Signature
----------- --------- -----------------
Agfa AGFA (AGFA 00 01)
Canon Canon ()
Casio_1 CASIO ()[^Q]
Casio_2 CASIO (QVC 00{3})
Epson EPSON (EPSON 00 01 00)
Foveon FOVEON (FOVEON 00{2} 01 00)
Fujifilm x FUJIFILM (FUJIFILM 14 00{3})
HPackard x Hewlett-Packard (HP)
Kyocera x x KYOCERA (KYOCERA {12} 00{3})
Kodak B x KODAK (KDK INFO[a-zA-Z0-9]* )
Minolta_1 MINOLTA ().{10}MLT0
Minolta_2 Minolta ().{10}MLT0
Konica x Minolta|KONICA ((MLY|KC|(+M){4})| 01 00{5} 04)
Nikon_1 NIKON (Nikon 00 01 00)
Nikon_2 NIKON ()[^N]
Nikon_3 x NIKON (Nikon 00 02[ 20 00] 00{2})
Olympus OLYMPUS (OLYMP 00[ 01 02] 00)
Panasonic_1 x Panasonic (Panasonic 00{3})
Panasonic_2 x x Panasonic (MKED)
Pentax_1 x Asahi ()[^A]
Pentax_2 x x Asahi (AOC 00..)
Ricoh_1 x RICOH (Rv|Rev)
Ricoh_2 x RICOH ( 00)
Ricoh_3 RICOH ((Ricoh|RICOH) 00{3})
Sanyo SANYO (SANYO 00 01 00)
Sigma SIGMA (SIGMA 00{3} 01 00)
Sony x SONY (SONY (CAM|DSC) 00{3})
Toshiba x TOSHIBA ()
unknown x . ()
References
MakerNote format details are not usually released by vendors (well, this is an euphemism: no vendor ever, to my knowledge, released any detail on its format, exception made for Sigma/Foveon). All information used for this package was collected on the Internet (and its reliability is therefore limited) or through personal tests. Some interesting sites are (not an exhaustive list at all):
General: home.arcor.de/ahuggel/exiv2/makernote.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/makernotes.html
Agfa: www.ozhiker.com/electronics/pjmt/jpeg_info/agfa_mn.html
Canon: www.burren.cx/david/canon.html
Casio: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.dicasoft.de/casiomn.htm
Epson: www.ozhiker.com/electronics/pjmt/jpeg_info/epson_mn.html
Foveon: Foveon is the same as Sigma, see Sigma
Fujifilm: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
......: www.ozhiker.com/electronics/pjmt/jpeg_info/fujifilm_mn.html
Kyocera: www.ozhiker.com/electronics/pjmt/jpeg_info/kyocera_mn.html
Kodak: my personal tests with my Kodak DX3900 (not IFD-like)
Minolta: www.dalibor.cz/minolta/makernote.htm
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/minolta_mn.html
Nikon: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.tawbaware.com/990exif.htm
...: www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
Olympus: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/olympus_mn.html
Panasonic: www.compton.nu/panasonic.html
Pentax: www.ozhiker.com/electronics/pjmt/jpeg_info/pentax_mn.html
Ricoh: www.ozhiker.com/electronics/pjmt/jpeg_info/ricoh_mn.html
Sanyo: www.exif.org/makernotes/SanyoMakerNote.html
Sigma: www.x3f.info/technotes/FileDocs/MakerNoteDoc.html
Sony: www.ozhiker.com/electronics/pjmt/jpeg_info/sony_mn.html
DX3900 MakerNote format
Kodak MakerNotes are written in a proprietary binary format, which is not IFD-like. So, there is no way to detect the beginning, end and type of a field; everything here was inferred through a careful comparison of the content of a set of Kodak JPEG files and their shot parameters. Fields seems to be aligned on four bytes boundaries. For the DX3900 model the endianness is always fixed to big endian. The signature regular expression is "^(KDK INFO[a-zA-Z0-9]* )", the maker is KODAK. The meaning of the tags is as follows:
BYTE ??? firmware version? This is always 3
BYTE Compression 1 = normal, 2 = 2160x1440 high compression
BYTE BurstMode 0 = off, 1 = on
BYTE MacroMode 0 = normal, 1 = close-up
SHORT PixelXDimension allowed 2160x1440, 1800x1200,
SHORT PixelYDimension / values: 1536x1024, 1080x720
SHORT Year the year value, with four digits
BYTE Month the month value (in [1,12])
BYTE Day the day value (in [1,31])
BYTE Hour the hour value (in [0,23])
BYTE Minute the minute value (in [0,59])
BYTE Second the second value (in [0,59])
BYTE SubSecond (in 130th of seconds?)
SHORT ??? ???
BYTE ??? ???
BYTE ShutterMode 0 = auto, 32 = manual
BYTE MeteringMode 0 = multi-pattern, 1=centre weight., 2=centre spot
BYTE BurstSequenceIndex index in [1,8], 0 if burst mode off
SHORT FNumber 100 times the Exif F-number
LONG ExposureTime in 10^-5 seconds
SSHORT ExposureBiasValue 1000 times the exposure bias in [-2,+2 step .5]
SHORT ??? ???
LONG ???
LONG ??? is this an estimate of the subject
LONG ??? / distance? If so, it is very rough.
LONG ??? /
BYTE FocusMode 0 = auto, 2 = close, 3 = infinity
BYTE ??? always 2
SHORT ??? ???
SSHORT PanoramaMode 0 = normal, -1 = focus at infinity
SHORT SubjectDistance (x-28)*2.54+7 looks like the distance in cm
BYTE WhiteBalance 0 = normal, 1 = fluor., 2 = tungsten, 3 = daylight
(27 bytes with unknown meaning here)
BYTE FlashMode 0 = auto, 1 = on, 2 = off, 3 = red-eyes
BYTE FlashFired 0 = yes, 1 = no
SHORT ISOSpeedMode the requested speed in {100,200,400} or zero
SHORT ??? ???
SHORT TotalZoomFactor 100 times the zoom factor in [+1,+6 step 0.1]
SHORT DateTimeStampMode 0 = none, [1,6] = the six modes
SHORT ColourMode 1 = black & white, 2 = sepia, 32 = colour
SHORT DigitalZoomFactor 100 times the zoom factor in [+1,+3 step 0.1]
BYTE ??? always zero
SBYTE Sharpness 0 = standard, 1 = sharp, -1 = soft
(808 bytes with unknown meaning here, maybe a thumbnail?)
<<lessPieces of information available after parsing the MakerNote
The result of the process of parsing the maker note is stored in a directory in the internal data structure for the APP1 Segment, whose path is "IFD@SubIFD@MakerNoteData_$format", where $format is the specific note format; the MakerNote entry in IFD0@SubIFD is then removed. This translation happens always, because there is a catch-all unknown rule for a binary makernote with very broad acceptance rules. The maker note directory contains, in addition, a special subdir with some fields reporting about the parsing process.
key content
-------- -------
ORIGINAL the raw content of the maker note (unparsed)
SIGNATURE the first few bytes which allowed the format to be chosen
ENDIANNESS the byte order chosen during parsing
FORMAT the maker note format chosen during parsing
ERROR [optional] error details, in case of failure while parsing
Supported MakerNote formats
Maker note formats are specified in a special internal hash, with a key for each format (including the unknown format). Each format entry corresponds to an anonymous hash containing information for parsing the MakerNote; the "normal" format is considered to be an IFD-like MakerNote with a next_link pointer, offsets counted from the global TIFF header and no MakerNote internal TIFF header.
key meaning or effect
--------- -----------------
signature the MakerNote signature (a regular expression)
maker the Maker signature (i.e., its name, no regex)
tags a reference to a hash for tag translations
(A) mkntstart if set, offsets are counted from the maker note start
(B) mkntTIFF if set, offsets are counted from the internal TIFF header
(C) ignore if set, the format is to be ignored
(D) nonext if set, the maker note IFD does not have a next_link
(E) endianness if set, the byte order is fixed to this value
(F) nonIFD if set, the maker note is not IFD-like
Currently, "supported" formats are described in the following table; authoritative data is indeed kept in Tables_makernotes.pl, to which the reader should refer for tag definitions and translations. Remember that both the signature and the maker fields are regular expressions matching at the beginning (the real signature corresponds to $1).
A B C D E F Maker Signature
----------- --------- -----------------
Agfa AGFA (AGFA 00 01)
Canon Canon ()
Casio_1 CASIO ()[^Q]
Casio_2 CASIO (QVC 00{3})
Epson EPSON (EPSON 00 01 00)
Foveon FOVEON (FOVEON 00{2} 01 00)
Fujifilm x FUJIFILM (FUJIFILM 14 00{3})
HPackard x Hewlett-Packard (HP)
Kyocera x x KYOCERA (KYOCERA {12} 00{3})
Kodak B x KODAK (KDK INFO[a-zA-Z0-9]* )
Minolta_1 MINOLTA ().{10}MLT0
Minolta_2 Minolta ().{10}MLT0
Konica x Minolta|KONICA ((MLY|KC|(+M){4})| 01 00{5} 04)
Nikon_1 NIKON (Nikon 00 01 00)
Nikon_2 NIKON ()[^N]
Nikon_3 x NIKON (Nikon 00 02[ 20 00] 00{2})
Olympus OLYMPUS (OLYMP 00[ 01 02] 00)
Panasonic_1 x Panasonic (Panasonic 00{3})
Panasonic_2 x x Panasonic (MKED)
Pentax_1 x Asahi ()[^A]
Pentax_2 x x Asahi (AOC 00..)
Ricoh_1 x RICOH (Rv|Rev)
Ricoh_2 x RICOH ( 00)
Ricoh_3 RICOH ((Ricoh|RICOH) 00{3})
Sanyo SANYO (SANYO 00 01 00)
Sigma SIGMA (SIGMA 00{3} 01 00)
Sony x SONY (SONY (CAM|DSC) 00{3})
Toshiba x TOSHIBA ()
unknown x . ()
References
MakerNote format details are not usually released by vendors (well, this is an euphemism: no vendor ever, to my knowledge, released any detail on its format, exception made for Sigma/Foveon). All information used for this package was collected on the Internet (and its reliability is therefore limited) or through personal tests. Some interesting sites are (not an exhaustive list at all):
General: home.arcor.de/ahuggel/exiv2/makernote.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/makernotes.html
Agfa: www.ozhiker.com/electronics/pjmt/jpeg_info/agfa_mn.html
Canon: www.burren.cx/david/canon.html
Casio: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.dicasoft.de/casiomn.htm
Epson: www.ozhiker.com/electronics/pjmt/jpeg_info/epson_mn.html
Foveon: Foveon is the same as Sigma, see Sigma
Fujifilm: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
......: www.ozhiker.com/electronics/pjmt/jpeg_info/fujifilm_mn.html
Kyocera: www.ozhiker.com/electronics/pjmt/jpeg_info/kyocera_mn.html
Kodak: my personal tests with my Kodak DX3900 (not IFD-like)
Minolta: www.dalibor.cz/minolta/makernote.htm
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/minolta_mn.html
Nikon: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
...: www.tawbaware.com/990exif.htm
...: www.ozhiker.com/electronics/pjmt/jpeg_info/nikon_mn.html
Olympus: park2.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
.....: www.ozhiker.com/electronics/pjmt/jpeg_info/olympus_mn.html
Panasonic: www.compton.nu/panasonic.html
Pentax: www.ozhiker.com/electronics/pjmt/jpeg_info/pentax_mn.html
Ricoh: www.ozhiker.com/electronics/pjmt/jpeg_info/ricoh_mn.html
Sanyo: www.exif.org/makernotes/SanyoMakerNote.html
Sigma: www.x3f.info/technotes/FileDocs/MakerNoteDoc.html
Sony: www.ozhiker.com/electronics/pjmt/jpeg_info/sony_mn.html
DX3900 MakerNote format
Kodak MakerNotes are written in a proprietary binary format, which is not IFD-like. So, there is no way to detect the beginning, end and type of a field; everything here was inferred through a careful comparison of the content of a set of Kodak JPEG files and their shot parameters. Fields seems to be aligned on four bytes boundaries. For the DX3900 model the endianness is always fixed to big endian. The signature regular expression is "^(KDK INFO[a-zA-Z0-9]* )", the maker is KODAK. The meaning of the tags is as follows:
BYTE ??? firmware version? This is always 3
BYTE Compression 1 = normal, 2 = 2160x1440 high compression
BYTE BurstMode 0 = off, 1 = on
BYTE MacroMode 0 = normal, 1 = close-up
SHORT PixelXDimension allowed 2160x1440, 1800x1200,
SHORT PixelYDimension / values: 1536x1024, 1080x720
SHORT Year the year value, with four digits
BYTE Month the month value (in [1,12])
BYTE Day the day value (in [1,31])
BYTE Hour the hour value (in [0,23])
BYTE Minute the minute value (in [0,59])
BYTE Second the second value (in [0,59])
BYTE SubSecond (in 130th of seconds?)
SHORT ??? ???
BYTE ??? ???
BYTE ShutterMode 0 = auto, 32 = manual
BYTE MeteringMode 0 = multi-pattern, 1=centre weight., 2=centre spot
BYTE BurstSequenceIndex index in [1,8], 0 if burst mode off
SHORT FNumber 100 times the Exif F-number
LONG ExposureTime in 10^-5 seconds
SSHORT ExposureBiasValue 1000 times the exposure bias in [-2,+2 step .5]
SHORT ??? ???
LONG ???
LONG ??? is this an estimate of the subject
LONG ??? / distance? If so, it is very rough.
LONG ??? /
BYTE FocusMode 0 = auto, 2 = close, 3 = infinity
BYTE ??? always 2
SHORT ??? ???
SSHORT PanoramaMode 0 = normal, -1 = focus at infinity
SHORT SubjectDistance (x-28)*2.54+7 looks like the distance in cm
BYTE WhiteBalance 0 = normal, 1 = fluor., 2 = tungsten, 3 = daylight
(27 bytes with unknown meaning here)
BYTE FlashMode 0 = auto, 1 = on, 2 = off, 3 = red-eyes
BYTE FlashFired 0 = yes, 1 = no
SHORT ISOSpeedMode the requested speed in {100,200,400} or zero
SHORT ??? ???
SHORT TotalZoomFactor 100 times the zoom factor in [+1,+6 step 0.1]
SHORT DateTimeStampMode 0 = none, [1,6] = the six modes
SHORT ColourMode 1 = black & white, 2 = sepia, 32 = colour
SHORT DigitalZoomFactor 100 times the zoom factor in [+1,+3 step 0.1]
BYTE ??? always zero
SBYTE Sharpness 0 = standard, 1 = sharp, -1 = soft
(808 bytes with unknown meaning here, maybe a thumbnail?)
Download (0.28MB)
Added: 2007-08-09 License: Perl Artistic License Price:
806 downloads
GIS::Distance::Vincenty 0.01001
GIS::Distance::Vincenty Perl module contains Thaddeus Vincenty distance calculations. more>>
GIS::Distance::Vincenty Perl module contains Thaddeus Vincenty distance calculations.
SYNOPSIS
my $calc = GIS::Distance::Vincenty->new();
my $distance = $calc->distance( $lon1, $lat1 => $lon2, $lat2 );
For the benefit of the terminally obsessive (as well as the genuinely needy), Thaddeus Vincenty devised formulae for calculating geodesic distances between a pair of latitude/longitude points on the earths surface, using an accurate ellipsoidal model of the earth.
Vincentys formula is accurate to within 0.5mm, or 0.000015", on the ellipsoid being used. Calculations based on a spherical model, such as the (much simpler) Haversine, are accurate to around 0.3% (which is still good enough for most purposes, of course).
Note: the accuracy quoted by Vincenty applies to the theoretical ellipsoid being used, which will differ (to varying degree) from the real earth geoid. If you happen to be located in Colorado, 2km above msl, distances will be 0.03% greater. In the UK, if you measure the distance from Lands End to John O Groats using WGS-84, it will be 28m - 0.003% - greater than using the Airy ellipsoid, which provides a better fit for the UK.
NOTE: This formula is still considered alpha quality in GIS::Distance. It has not been tested enough to be used in production.
FORMULA
a, b = major & minor semiaxes of the ellipsoid
f = flattening (a-b)/a
L = lon2 - lon1
u1 = atan((1-f) * tan(lat1))
u2 = atan((1-f) * tan(lat2))
sin_u1 = sin(u1)
cos_u1 = cos(u1)
sin_u2 = sin(u2)
cos_u2 = cos(u2)
lambda = L
lambda_pi = 2PI
while abs(lambda-lambda_pi) > 1e-12
sin_lambda = sin(lambda)
cos_lambda = cos(lambda)
sin_sigma = sqrt((cos_u2 * sin_lambda) * (cos_u2*sin_lambda) +
(cos_u1*sin_u2-sin_u1*cos_u2*cos_lambda) * (cos_u1*sin_u2-sin_u1*cos_u2*cos_lambda))
cos_sigma = sin_u1*sin_u2 + cos_u1*cos_u2*cos_lambda
sigma = atan2(sin_sigma, cos_sigma)
alpha = asin(cos_u1 * cos_u2 * sin_lambda / sin_sigma)
cos_sq_alpha = cos(alpha) * cos(alpha)
cos2sigma_m = cos_sigma - 2*sin_u1*sin_u2/cos_sq_alpha
cc = f/16*cos_sq_alpha*(4+f*(4-3*cos_sq_alpha))
lambda_pi = lambda
lambda = L + (1-cc) * f * sin(alpha) *
(sigma + cc*sin_sigma*(cos2sigma_m+cc*cos_sigma*(-1+2*cos2sigma_m*cos2sigma_m)))
}
usq = cos_sq_alpha*(a*a-b*b)/(b*b);
aa = 1 + usq/16384*(4096+usq*(-768+usq*(320-175*usq)))
bb = usq/1024 * (256+usq*(-128+usq*(74-47*usq)))
delta_sigma = bb*sin_sigma*(cos2sigma_m+bb/4*(cos_sigma*(-1+2*cos2sigma_m*cos2sigma_m)-
bb/6*cos2sigma_m*(-3+4*sin_sigma*sin_sigma)*(-3+4*cos2sigma_m*cos2sigma_m)))
c = b*aa*(sigma-delta_sigma)
<<lessSYNOPSIS
my $calc = GIS::Distance::Vincenty->new();
my $distance = $calc->distance( $lon1, $lat1 => $lon2, $lat2 );
For the benefit of the terminally obsessive (as well as the genuinely needy), Thaddeus Vincenty devised formulae for calculating geodesic distances between a pair of latitude/longitude points on the earths surface, using an accurate ellipsoidal model of the earth.
Vincentys formula is accurate to within 0.5mm, or 0.000015", on the ellipsoid being used. Calculations based on a spherical model, such as the (much simpler) Haversine, are accurate to around 0.3% (which is still good enough for most purposes, of course).
Note: the accuracy quoted by Vincenty applies to the theoretical ellipsoid being used, which will differ (to varying degree) from the real earth geoid. If you happen to be located in Colorado, 2km above msl, distances will be 0.03% greater. In the UK, if you measure the distance from Lands End to John O Groats using WGS-84, it will be 28m - 0.003% - greater than using the Airy ellipsoid, which provides a better fit for the UK.
NOTE: This formula is still considered alpha quality in GIS::Distance. It has not been tested enough to be used in production.
FORMULA
a, b = major & minor semiaxes of the ellipsoid
f = flattening (a-b)/a
L = lon2 - lon1
u1 = atan((1-f) * tan(lat1))
u2 = atan((1-f) * tan(lat2))
sin_u1 = sin(u1)
cos_u1 = cos(u1)
sin_u2 = sin(u2)
cos_u2 = cos(u2)
lambda = L
lambda_pi = 2PI
while abs(lambda-lambda_pi) > 1e-12
sin_lambda = sin(lambda)
cos_lambda = cos(lambda)
sin_sigma = sqrt((cos_u2 * sin_lambda) * (cos_u2*sin_lambda) +
(cos_u1*sin_u2-sin_u1*cos_u2*cos_lambda) * (cos_u1*sin_u2-sin_u1*cos_u2*cos_lambda))
cos_sigma = sin_u1*sin_u2 + cos_u1*cos_u2*cos_lambda
sigma = atan2(sin_sigma, cos_sigma)
alpha = asin(cos_u1 * cos_u2 * sin_lambda / sin_sigma)
cos_sq_alpha = cos(alpha) * cos(alpha)
cos2sigma_m = cos_sigma - 2*sin_u1*sin_u2/cos_sq_alpha
cc = f/16*cos_sq_alpha*(4+f*(4-3*cos_sq_alpha))
lambda_pi = lambda
lambda = L + (1-cc) * f * sin(alpha) *
(sigma + cc*sin_sigma*(cos2sigma_m+cc*cos_sigma*(-1+2*cos2sigma_m*cos2sigma_m)))
}
usq = cos_sq_alpha*(a*a-b*b)/(b*b);
aa = 1 + usq/16384*(4096+usq*(-768+usq*(320-175*usq)))
bb = usq/1024 * (256+usq*(-128+usq*(74-47*usq)))
delta_sigma = bb*sin_sigma*(cos2sigma_m+bb/4*(cos_sigma*(-1+2*cos2sigma_m*cos2sigma_m)-
bb/6*cos2sigma_m*(-3+4*sin_sigma*sin_sigma)*(-3+4*cos2sigma_m*cos2sigma_m)))
c = b*aa*(sigma-delta_sigma)
Download (0.008MB)
Added: 2007-07-25 License: Perl Artistic License Price:
834 downloads
NAFE 0.1
NAFE is a tool to write and edit Linux console font files (.psf) with any text editor. more>>
nafe (Not Another Font Editor) is a tool to convert Linux console font files into ASCII text files that are human-readable/editable.
It also converts this text files back into system-usable PSF font files for display on the Linux text console, thus making font editing easy.
nafe is no consolefont editor, but a toolset to translate psf format consolefonts into text files
and text files into psf files.
The advantage is that you can edit the font in the text file easily with any text editor (not provided by nafe).
So you are independent from your actual terminal hardware and dont need stuff like svgalib
nafe understands and creates psf mode 1 and mode 2 files.
<<lessIt also converts this text files back into system-usable PSF font files for display on the Linux text console, thus making font editing easy.
nafe is no consolefont editor, but a toolset to translate psf format consolefonts into text files
and text files into psf files.
The advantage is that you can edit the font in the text file easily with any text editor (not provided by nafe).
So you are independent from your actual terminal hardware and dont need stuff like svgalib
nafe understands and creates psf mode 1 and mode 2 files.
Download (0.017MB)
Added: 2005-04-11 License: GPL (GNU General Public License) Price:
1659 downloads
Photorec 6.6
PhotoRec is a small tool to recover pictures from digital camera memory. more>>
PhotoRec is a small tool to recover pictures from digital camera memory. Photorec software searches for MOV and JPEG headers, and because there is (usually) no data fragmentation, it can recover the whole file.
It can recover data from CompactFlash, Memory Stick, SecureDigital, SmartMedia, Microdrive, MMC, USB Memory Drives...
PhotoRec is safe to use, it will never attempt to write to the drive or memory support you are about to recover from. Recovered files are instead written in the directory from where you are running the PhotoRec program.
Photorec ignores the filesystem, this way it works even if the filesystem is severely damaged.
It can recover lost files at least from:
- FAT,
- NTFS,
- EXT2/EXT3 filesystem
Digital Camera
PhotoRec has been successfully tested with:
- Canon EOS300D, 10D
- HP PhotoSmart 620, 850, 935
- Nikon CoolPix 775, 5700
- Olympus C350N, C860L, Mju 400 Digital, Stylus 300
- Sony DSC-P9
- Praktica DCZ-3.4
- Casio Exilim EX-Z 750
PhotoRec searchs known file header and because there is no data fragmentation (usually), it can recover the whole file. Photorec recognises numerous file format including:
Archive
- .7z 7zip archive file
- .bz2 bzip2 compressed data
- .gz gzip compressed data
- .rar Rar archive
- .tar tar archive
- .zip zip archive
- Multimedia
- .asf, .wma, .wmv: Advanced Streaming Format used for Audio/Video
- .au Sun/NeXT audio data
- .avi .wav RIFF audio/video
- .bmp BMP bitmap image
- .cdr Corel Draw
- .crw Canon Raw picture
- .ctg Canon catalog
- .dcr Kodak Raw picture
- .dsc Nikon dsc
- .fla Flash Project File
- .gif Graphic Interchange Format
- .jng JPEG Network Graphics
- .jpg JPG picture
- .mng Multiple-Image Network Graphics
- .mov MOV video
- .mp3 MPEG ADTS, layer III, v1 audio
- .mp4 MPEG 4
- .mpg Moving Picture Experts Group video
- .mrw Minolta Raw picture
- .ogg OGG Vorbis audio
- .orf Olympus Raw Format picture
- .pcx PCX file format
- .pef Pentax Raw picture
- .png Portable Network Graphics
- .psd Adobe Photoshop Image
- .qxd QuarkXpress Document
- .qxp QuarkXpress Document
- .raf Raw Fujifilm picture
- .raw Contax picture
- .rdc Rollei picture
- .sit Mikron
- .sr2 Sony Raw picture
- .tif Tag Image File Format
- .x3f Sigma/Foveon X3 raw picture
- .xcf GIMP XCF File
Office
- .doc Microsoft Word
- .mbd Access database
- .odd OpenDocument Drawing
- .odp OpenDocument Presentation
- .ods OpenDocument Spreadsheet
- .odt OpenDocument Text
- .pap Papyrus word file
- .ppt PowerPoint presentation
- .rtf Rich Text Format
- .sda StarDraw
- .sdc StarCalc
- .sdd StarImpress
- .sdw StarWriter
- .slk Sylk, Multiplan Symbolic Link Interchange
- .sxc OpenOffice Spreadsheet
- .sxd OpenOffice Drawing
- .sxi OpenOffice Presentation
- .sxw OpenOffice Text Document
- .txt Text file
- .vis Visio document
- .xls Microsoft Excel
Others
- .asp ASP script
- .bat Batch
- .c C source file
- .dbf DBase 3 (prone to false positive)
- .dbx Outlook Express
- .eps Encasulated PostScript
- .exe MS executable
- .frm MySQL table definition
- .h C header
- .html HTML
- .jsp JSP script
- .MYI MySQL MISAM compressed data
- .pdf Portable Document Format
- .php PHP script
- .pl Perl script
- .prc PalmOS application
- .ps PostScript document
- .pst Outlook
- .py Python script
- .qdf Quicken
- .sh Shell script
- .wab Windows Address Book
Enhancements:
- A new method for handling fragmented data is now used, making recovery more reliable and faster.
- This release can be set to search for files in FAT16/FAT32 unallocated space only, which avoids wasting time recovering files that are still accessible, making the recovery of lost files much faster and more efficient.
- New file formats have been added.
<<lessIt can recover data from CompactFlash, Memory Stick, SecureDigital, SmartMedia, Microdrive, MMC, USB Memory Drives...
PhotoRec is safe to use, it will never attempt to write to the drive or memory support you are about to recover from. Recovered files are instead written in the directory from where you are running the PhotoRec program.
Photorec ignores the filesystem, this way it works even if the filesystem is severely damaged.
It can recover lost files at least from:
- FAT,
- NTFS,
- EXT2/EXT3 filesystem
Digital Camera
PhotoRec has been successfully tested with:
- Canon EOS300D, 10D
- HP PhotoSmart 620, 850, 935
- Nikon CoolPix 775, 5700
- Olympus C350N, C860L, Mju 400 Digital, Stylus 300
- Sony DSC-P9
- Praktica DCZ-3.4
- Casio Exilim EX-Z 750
PhotoRec searchs known file header and because there is no data fragmentation (usually), it can recover the whole file. Photorec recognises numerous file format including:
Archive
- .7z 7zip archive file
- .bz2 bzip2 compressed data
- .gz gzip compressed data
- .rar Rar archive
- .tar tar archive
- .zip zip archive
- Multimedia
- .asf, .wma, .wmv: Advanced Streaming Format used for Audio/Video
- .au Sun/NeXT audio data
- .avi .wav RIFF audio/video
- .bmp BMP bitmap image
- .cdr Corel Draw
- .crw Canon Raw picture
- .ctg Canon catalog
- .dcr Kodak Raw picture
- .dsc Nikon dsc
- .fla Flash Project File
- .gif Graphic Interchange Format
- .jng JPEG Network Graphics
- .jpg JPG picture
- .mng Multiple-Image Network Graphics
- .mov MOV video
- .mp3 MPEG ADTS, layer III, v1 audio
- .mp4 MPEG 4
- .mpg Moving Picture Experts Group video
- .mrw Minolta Raw picture
- .ogg OGG Vorbis audio
- .orf Olympus Raw Format picture
- .pcx PCX file format
- .pef Pentax Raw picture
- .png Portable Network Graphics
- .psd Adobe Photoshop Image
- .qxd QuarkXpress Document
- .qxp QuarkXpress Document
- .raf Raw Fujifilm picture
- .raw Contax picture
- .rdc Rollei picture
- .sit Mikron
- .sr2 Sony Raw picture
- .tif Tag Image File Format
- .x3f Sigma/Foveon X3 raw picture
- .xcf GIMP XCF File
Office
- .doc Microsoft Word
- .mbd Access database
- .odd OpenDocument Drawing
- .odp OpenDocument Presentation
- .ods OpenDocument Spreadsheet
- .odt OpenDocument Text
- .pap Papyrus word file
- .ppt PowerPoint presentation
- .rtf Rich Text Format
- .sda StarDraw
- .sdc StarCalc
- .sdd StarImpress
- .sdw StarWriter
- .slk Sylk, Multiplan Symbolic Link Interchange
- .sxc OpenOffice Spreadsheet
- .sxd OpenOffice Drawing
- .sxi OpenOffice Presentation
- .sxw OpenOffice Text Document
- .txt Text file
- .vis Visio document
- .xls Microsoft Excel
Others
- .asp ASP script
- .bat Batch
- .c C source file
- .dbf DBase 3 (prone to false positive)
- .dbx Outlook Express
- .eps Encasulated PostScript
- .exe MS executable
- .frm MySQL table definition
- .h C header
- .html HTML
- .jsp JSP script
- .MYI MySQL MISAM compressed data
- .pdf Portable Document Format
- .php PHP script
- .pl Perl script
- .prc PalmOS application
- .ps PostScript document
- .pst Outlook
- .py Python script
- .qdf Quicken
- .sh Shell script
- .wab Windows Address Book
Enhancements:
- A new method for handling fragmented data is now used, making recovery more reliable and faster.
- This release can be set to search for files in FAT16/FAT32 unallocated space only, which avoids wasting time recovering files that are still accessible, making the recovery of lost files much faster and more efficient.
- New file formats have been added.
Download (1.0MB)
Added: 2007-05-09 License: GPL (GNU General Public License) Price:
934 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above sigma consolefonts search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
