When starting a new thread it always helps if you tell us what operating system and shell you're using. Various utilities on different systems have options that vary form operating system to operating system and shells are notorious for offering different sets of features above and beyond those that are in almost all shells. If we know what operating system and shell you're using, we are less likely to make suggestions that won't work in your environment.
We are here to help you learn how to do things like this on your own; not to act as your unpaid programming staff. If you show us what you have tried to solve a problem on your own (posting your code in CODE tags) along with the sample input that you provided (please surround sample input data in CODE tags) and the output you hope to produce from that data (also, please in CODE tags) we can make better suggestions to help you get around whatever was keeping you from your goal.
In a case like this one might try something like:
Code:
awk -v Headers="Box Name,Weight,Length,Depth,Color" '
BEGIN { # Split the Headers given to us into field names and print the output
# header line. Set NHdrs to the number of fields to be printed in each
# output record. Set elements of the subscript[] array to have the
# output field name as a subscript and the output field position as the
# value.
NHdrs = split(Headers, Hdrs, /,/)
for(i = 1; i <= NHdrs; i++) {
subscript[Hdrs[i]] = i
printf("%s%s", Hdrs[i], (i == NHdrs) ? ORS : ",")
}
# Since the input field separator is sometimes <colon><space> and
# sometimes <space><colon>, we will use a <colon> surrounded by any
# number of <space>s as our field separator:
FS = " *: *"
}
# Define a function to print an output record if any input data has been seen
# since we last printed a record.
function print_record( loop) {
if(data) {
data = 0
for(loop = 1; loop <= NHdrs; loop++)
printf("%s%s", field[loop], (loop == NHdrs) ? ORS : ",")
split("", field)
}
}
NF { # We have an input field on this line, gather the data and skip to the
# next input record.
field[subscript[$1]] = $2
data++
next
}
{ # Since there is no input fields on this line, print the data
# accumulated from the previous lines as an output record.
print_record()
}
END { # In case there was no empty line at the end of the input file, also
# print the data accumulated from the previous lines when we hit EOF.
print_record()
}' file
These 2 Users Gave Thanks to Don Cragun For This Post:
Hi I have an input file and I want to transpose it but I need to take care that if any field is missing for a record it should be popoulated with space for that field - using a shell script
INFILE
----------
emp=1
sal=2
loc=abc
emp=2
sal=21
sal=22
loc=xyz
emp=5
loc=abc
OUTFILE... (10 Replies)
Hi,
I found the following awk script to transpose multiple (3) columns to multiple rows:
#===
BEGIN {FS=","}
{
for (i=1;i<=NF;i++)
{
arr=$i;
if(nf<= NF)
nf=NF;
}
nr=NR
}
END {
for(i=1;i<=nf;i++)
{ (8 Replies)
Hi,
I did read a few posts on the subjects, tried out a few solutions, but did not solve my problem.
https://www.unix.com/302121568-post11.html
https://www.unix.com/shell-programming-scripting/137953-large-file-columns-into-rows-etc-4.html
Please help. Problem very similar to the second link... (15 Replies)
I'm aware there are a lot of resources dedicated to the question of transposing rows and columns, but I'm a total newbie at this and the task appears to be beyond me.
I have 40 text files with content that looks like this:
Dokument 1 von 146
Orange County Register (California)
June 26, 2010... (2 Replies)
I have a data
A 1
B 2
C 3
D 4
E 5
i would like to change the data
A B C D E
1 2 3 4 5
Pls suggest how we can do it in UNIX.
Start using code tags, thanks. Also start reading your PM's you get from Mods as well read the Forum Rules. That might not do any harm. (24 Replies)
Any tips on how I can awk the input data to display the desired output per below? Thanking you in advance.
input test data:
2
2010-02-16 10:00:00
111111111111 bytes
99999999999 bytes
90%
4
2010-02-16 12:00:00
333333333333 bytes
77777777777 bytes
88%
5
2010-02-16 11:00:00... (4 Replies)
Hello. very new to shell scripting and would like to know if anyone could help me.
I have data thats being pulled into a txt file and currently have to manually transpose the data which is taking a long time to do.
here is what the data looks like.
Server1 -- Date -- Other -- value... (7 Replies)
Hi Friends,
Hope all is well.
I have an input file like this
a gene1 10
b gene1 2
c gene2 20
c gene3 10
d gene4 5
e gene5 6
Steps to reach output.
1. Print unique values of column1 as column of the matrix, which will be
a
b
c (5 Replies)
JOIN(1) BSD General Commands Manual JOIN(1)NAME
join -- relational database operator
SYNOPSIS
join [-a file_number | -v file_number] [-e string] [-o list] [-t char] [-1 field] [-2 field] file1 file2
DESCRIPTION
The join utility performs an ``equality join'' on the specified files and writes the result to the standard output. The ``join field'' is
the field in each file by which the files are compared. The first field in each line is used by default. There is one line in the output
for each pair of lines in file1 and file2 which have identical join fields. Each output line consists of the join field, the remaining
fields from file1 and then the remaining fields from file2.
The default field separators are tab and space characters. In this case, multiple tabs and spaces count as a single field separator, and
leading tabs and spaces are ignored. The default output field separator is a single space character.
Many of the options use file and field numbers. Both file numbers and field numbers are 1 based, i.e., the first file on the command line is
file number 1 and the first field is field number 1. The following options are available:
-a file_number
In addition to the default output, produce a line for each unpairable line in file file_number.
-e string
Replace empty output fields with string.
-o list
The -o option specifies the fields that will be output from each file for each line with matching join fields. Each element of list
has either the form file_number.field, where file_number is a file number and field is a field number, or the form '0' (zero), repre-
senting the join field. The elements of list must be either comma (',') or whitespace separated. (The latter requires quoting to
protect it from the shell, or, a simpler approach is to use multiple -o options.)
-t char
Use character char as a field delimiter for both input and output. Every occurrence of char in a line is significant.
-v file_number
Do not display the default output, but display a line for each unpairable line in file file_number. The options -v 1 and -v 2 may be
specified at the same time.
-1 field
Join on the field'th field of file1.
-2 field
Join on the field'th field of file2.
When the default field delimiter characters are used, the files to be joined should be ordered in the collating sequence of sort(1), using
the -b option, on the fields on which they are to be joined, otherwise join may not report all field matches. When the field delimiter char-
acters are specified by the -t option, the collating sequence should be the same as sort(1) without the -b option.
If one of the arguments file1 or file2 is '-', the standard input is used.
EXIT STATUS
The join utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
For compatibility with historic versions of join, the following options are available:
-a In addition to the default output, produce a line for each unpairable line in both file1 and file2.
-j1 field
Join on the field'th field of file1.
-j2 field
Join on the field'th field of file2.
-j field
Join on the field'th field of both file1 and file2.
-o list ...
Historical implementations of join permitted multiple arguments to the -o option. These arguments were of the form
file_number.field_number as described for the current -o option. This has obvious difficulties in the presence of files named 1.2.
These options are available only so historic shell scripts do not require modification and should not be used.
SEE ALSO awk(1), comm(1), paste(1), sort(1), uniq(1)STANDARDS
The join command conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BSD July 5, 2004 BSD