Sponsored Content
Top Forums Shell Programming and Scripting How to append some strings line by line? Post 302208259 by xinoo on Monday 23rd of June 2008 12:21:31 PM
Old 06-23-2008
How to append some strings line by line?

I would like to append the numbers 1, 2, 3, 4 and so on to the lines of the file:
Adam Wilkins | Colorado | 36
John Butler | Los Angeles | 47
Cassey Johnson | Minneapolis | 25
Albert Aniston | Miami | 19
....
Tony Legler | Sacramento | 55
Matt Simmons | New York | 38

Output would look like this:
Adam Wilkins | Colorado | 36 | 1
John Butler | Los Angeles | 47 | 2
Cassey Johnson | Minneapolis | 25 | 3
Albert Aniston | Miami | 19 | 4
.....
Tony Legler | Sacramento | 55 | 9
Matt Simmons | New York | 38 | 10

I know this is simple for Unix gurus Smilie
Maybe someone can enlighten me on this?
Many thanks.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Joining lines in reverse. append line 1 to line 2.

Hi I have used many times the various methods to append two lines together in a file. This time I want to append the 1st line to the second and repeat for the complete file.... an example This is the file owns the big brown dog joe owns the small black dog jim What I want is ... (7 Replies)
Discussion started by: dwalley
7 Replies

2. Shell Programming and Scripting

Append line that does not contain pipe to it previous line

Hi All, I have a file which contains data as below When we see no pipe character in the line. append those lines to the previous line with pipe character till we get the next line with pipe character with ~(concat with ~) Input file looks like: 1080530944|001|john.l.bonner|Acknowledge|CN... (11 Replies)
Discussion started by: ainuddin
11 Replies

3. Shell Programming and Scripting

Append each line to next previous line in a file

Hi all, Please help me in providing sample code to append the following 4 lines in one row. Input : A1/EXT "BAPBSC10/07B/00" 523 090530 0115 RXOCF-430 HY1711 1 EXTERNAL ALARM DOOR ALARM Output should be : A1/EXT "BAPBSC10/07B/00" 523 090530 0115 ... (8 Replies)
Discussion started by: sudhakaryadav
8 Replies

4. Shell Programming and Scripting

shell script to read a line in gps receiver log file and append that line to new file

Hi, I have gps receiver log..its giving readings .like below Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GPSD,R=1 $GPGSV,3,1,11,08,16,328,40,11,36,127,00,28,33,283,39,20,11,165,00*71... (3 Replies)
Discussion started by: gudivada213
3 Replies

5. Shell Programming and Scripting

Append line count to each line

Hello forum, I need to append the total line count to the end of each line in a file. The file where this line count needs to be appended is generated by this script: The script does a word frequency count by the first column of a file. if I add wc -l at the end then the line count... (4 Replies)
Discussion started by: jaysean
4 Replies

6. Shell Programming and Scripting

Append next line to previous line when one pattern not found

Hi, I need help for below scenario.I have a flat file which is having records seperated by delimiters which will represent each record for oracle table.My Control file will consider each line as one record for that table. Some of the lines are aligned in two/three lines so that records are... (4 Replies)
Discussion started by: kannansr621
4 Replies

7. Shell Programming and Scripting

find a certain line and append text to the end of the line

After I create printer queues in AIX, I have to append a filter file location within that printers custom file. within lets say test_queue.txt I need to find the row that starts with :699 and then I need to append on the end the string /usr/local/bin/k_portrait.sh. Now I've gotten the sed... (2 Replies)
Discussion started by: peachclift
2 Replies

8. UNIX for Dummies Questions & Answers

How to remove fields space and append next line to previous line.?

awk 'BEGIN{FS = "Ç"} NR == 1 {p = $0; next} NF > 1 {print p; p = $0} NF <= 1 {p = (p " " $0)} END {print p}' input.txt > output.txt This is what the input data file looks like with broken lines Code: 29863 Ç890000000 Ç543209911 ÇCHNGOHG Ç000000001 Ç055 ... (4 Replies)
Discussion started by: cumeh1624
4 Replies

9. Shell Programming and Scripting

Append Next line with current Line bassed on condition

Hi, I have an XML file and I am tring to extract some data form it, after lot of data cleaning process, I ended up with an issue, and need your urgent support. my current input data in below format: <Node>xxxxxx <Node>yyyyy</Node> <Node>zzzzzz <Node>12345</node> I need... (9 Replies)
Discussion started by: rramkrishnas
9 Replies

10. Shell Programming and Scripting

Remove new line starting with a numeric value and append it to the previous line

Hi, i have a file with multiple entries. After some tests with sed i managed to get the file output as follows: lsn=X-LINK-IN0,apc=661:0,state=avail,avail/links=1/1, 00,2110597,2094790,0,81,529,75649011,56435363, lsn=TM1ITP1-AM1ITP1-LS,apc=500:0,state=avail,avail/links=1/1,... (5 Replies)
Discussion started by: nms
5 Replies
SoGeoOrigin(3)							       Coin							    SoGeoOrigin(3)

NAME
SoGeoOrigin - The SoGeoOrigin class is used to specify an absolute geographic location against which geometry is referenced. FILE FORMAT/DEFAULTS: SYNOPSIS
#include <Inventor/nodes/SoGeoOrigin.h> Inherits SoNode. Public Member Functions virtual SoType getTypeId (void) const SoGeoOrigin (void) virtual void doAction (SoAction *action) virtual void callback (SoCallbackAction *action) virtual void GLRender (SoGLRenderAction *action) virtual void getBoundingBox (SoGetBoundingBoxAction *action) virtual void getMatrix (SoGetMatrixAction *action) virtual void pick (SoPickAction *action) virtual void getPrimitiveCount (SoGetPrimitiveCountAction *action) Static Public Member Functions static SoType getClassTypeId (void) static void initClass (void) Public Attributes SoSFVec3d geoCoords SoMFString geoSystem Protected Member Functions virtual const SoFieldData * getFieldData (void) const virtual ~SoGeoOrigin () Static Protected Member Functions static const SoFieldData ** getFieldDataPtr (void) Additional Inherited Members Detailed Description The SoGeoOrigin class is used to specify an absolute geographic location against which geometry is referenced. FILE FORMAT/DEFAULTS: GeoOrigin { geoSystem ['GD', 'WE'] geoCoords 0 0 0 } A common problem when dealing with geographic data is the reduced floating point precision you often get. UTM coordinates are often in the 10^5 a 10^6 magnitude, and this leaves very little precision for details at that position. The SoGeo nodes are therefore useful when you want to keep your data in its original system, but still get good floating point precision when rendering. Coin needs a local Cartesian coordinate system when rendering. When a SoGeoOrigin node is used, Coin will create a coordinate system at the SoGeoOrigin position, and all geometry (and the camera) in the scene graph will be projected into that coordinate system. The coordinate system will always have the Z axis point up from the ground. The Y axis will point towards the north pole, and the X-axis is found using the right hand rule. A scene graph should only contain one GeoOrigin node, and all geometry in the scene graph will, as stated earlier, be rendered relative to this position. This means that the precision will be best if the GeoOrigin position is as close to actual camera position as possible. If you move around on a large area, it might therefore be a good idea too actually move the GeoOrigin postition instead of the camera. To place geometry in the scene graph, you can either use an SoGeoSeparator node or an SoGeoCoordinate node. When using a GeoSeparator node, all geometry inside that separator will be rendered relative to its geo-system position and orientation, and you then use regular shapes and regular SoCoordinate3 nodes to specify data (the points in an SoCoordinate3 must be adjusted to be relative to the GeoSeparator position). The SoGeoCoordinate node on the other hand can contain double precision geo-coordinates, and that node will internally recalculate the double precison array to a single precision array which is relative to the SoGeoOrgin node. One note regarding UTM projections: Since it's quite common to assume a flat earth when working with UTM data, it's possible to supply a 'FLAT' keyword for UTM coordinate systems: GeoOrigin { geoSystem [ 'UTM', 'Z17', 'FLAT' ] geoCoords 846889 4313850 0 } Example scene graph: GeoOrigin { geoSystem 'GD' geoCoords 40.77 -73.97 0 } GeoSeparator { # New York, NY geoSystem 'GD' geoCoords 40.67 -73.94 0 BaseColor { rgb 0 1 0 } Cube { width 25000 height 25000 depth 25000 } Translation { translation 0 0 30000 } Text2 { string 'New York' } } GeoSeparator { # Los Angeles, CA geoSystem 'GD' geoCoords 34.11 -118.4 0 BaseColor { rgb 1 0 0 } Cube { width 25000 height 25000 depth 25000 } Translation { translation 0 0 30000 } Text2 { string 'Los Angeles' } } GeoSeparator { # Washington, DC geoSystem [ 'UTM', 'Z17' ] geoCoords 846889 4313850 0 BaseColor { rgb 0 1 1 } Cube { width 25000 height 25000 depth 25000 } Translation { translation 0 0 30000 } Text2 { string 'Washington' } } # add a small geogrid GeoCoordinate { geoSystem 'GD' point [ 32 -120 0, 32 -110 0, 32 -100 0, 32 -90 0, 32 -80 0, 32 -70 0, 34 -120 0, 34 -110 0, 34 -100 0, 34 -90 0, 34 -80 0, 34 -70 0, 36 -120 0, 36 -110 0, 36 -100 0, 36 -90 0, 36 -80 0, 36 -70 0, 38 -120 0, 38 -110 0, 38 -100 0, 38 -90 0, 38 -80 0, 38 -70 0, 40 -120 0, 40 -110 0, 40 -100 0, 40 -90 0, 40 -80 0, 40 -70 0 42 -120 0, 42 -110 0, 42 -100 0, 42 -90 0, 42 -80 0, 42 -70 0 ] } DrawStyle { style LINES } BaseColor {} ShapeHints { vertexOrdering COUNTERCLOCKWISE } QuadMesh { verticesPerRow 6 verticesPerColumn 6 } Since: Coin 2.5 Constructor &; Destructor Documentation SoGeoOrigin::SoGeoOrigin (void) Constructor. SoGeoOrigin::~SoGeoOrigin () [protected], [virtual] Destructor. Member Function Documentation SoType SoGeoOrigin::getClassTypeId (void) [static] This static method returns the SoType object associated with objects of this class. Reimplemented from SoNode. SoType SoGeoOrigin::getTypeId (void) const [virtual] Returns the type identification of an object derived from a class inheriting SoBase. This is used for run-time type checking and 'downward' casting. Usage example: void foo(SoNode * node) { if (node->getTypeId() == SoFile::getClassTypeId()) { SoFile * filenode = (SoFile *)node; // safe downward cast, knows the type } } For application programmers wanting to extend the library with new nodes, engines, nodekits, draggers or others: this method needs to be overridden in all subclasses. This is typically done as part of setting up the full type system for extension classes, which is usually accomplished by using the pre-defined macros available through for instance Inventor/nodes/SoSubNode.h (SO_NODE_INIT_CLASS and SO_NODE_CONSTRUCTOR for node classes), Inventor/engines/SoSubEngine.h (for engine classes) and so on. For more information on writing Coin extensions, see the class documentation of the toplevel superclasses for the various class groups. Implements SoBase. const SoFieldData ** SoGeoOrigin::getFieldDataPtr (void) [static], [protected] This API member is considered internal to the library, as it is not likely to be of interest to the application programmer. Reimplemented from SoNode. const SoFieldData * SoGeoOrigin::getFieldData (void) const [protected], [virtual] Returns a pointer to the class-wide field data storage object for this instance. If no fields are present, returns NULL. Reimplemented from SoFieldContainer. void SoGeoOrigin::initClass (void) [static] Sets up initialization for data common to all instances of this class, like submitting necessary information to the Coin type system. Reimplemented from SoNode. void SoGeoOrigin::doAction (SoAction *action) [virtual] This function performs the typical operation of a node for any action. Reimplemented from SoNode. void SoGeoOrigin::callback (SoCallbackAction *action) [virtual] Action method for SoCallbackAction. Simply updates the state according to how the node behaves for the render action, so the application programmer can use the SoCallbackAction for extracting information about the scene graph. Reimplemented from SoNode. void SoGeoOrigin::GLRender (SoGLRenderAction *action) [virtual] Action method for the SoGLRenderAction. This is called during rendering traversals. Nodes influencing the rendering state in any way or who wants to throw geometry primitives at OpenGL overrides this method. Reimplemented from SoNode. void SoGeoOrigin::getBoundingBox (SoGetBoundingBoxAction *action) [virtual] Action method for the SoGetBoundingBoxAction. Calculates bounding box and center coordinates for node and modifies the values of the action to encompass the bounding box for this node and to shift the center point for the scene more towards the one for this node. Nodes influencing how geometry nodes calculates their bounding box also overrides this method to change the relevant state variables. Reimplemented from SoNode. void SoGeoOrigin::getMatrix (SoGetMatrixAction *action) [virtual] Action method for SoGetMatrixAction. Updates action by accumulating with the transformation matrix of this node (if any). Reimplemented from SoNode. void SoGeoOrigin::pick (SoPickAction *action) [virtual] Action method for SoPickAction. Does common processing for SoPickAction action instances. Reimplemented from SoNode. void SoGeoOrigin::getPrimitiveCount (SoGetPrimitiveCountAction *action) [virtual] Action method for the SoGetPrimitiveCountAction. Calculates the number of triangle, line segment and point primitives for the node and adds these to the counters of the action. Nodes influencing how geometry nodes calculates their primitive count also overrides this method to change the relevant state variables. Reimplemented from SoNode. Member Data Documentation SoSFVec3d SoGeoOrigin::geoCoords Used for specifying the geographic coordinates. For the GD system this should be <latitude> <longitude> <elevation>. For UTM it is <easting> <northing> <elevation>, and for GC it is simply <x> <y> <z>. SoMFString SoGeoOrigin::geoSystem Used to specify a spatial reference frame. Coin currently supports three different systems. Support for more systems might be added in the future. o o o The 'GD' and 'UTM' systems can, for future support, have an ellipsoid specification. The default is 'WE' which is the WGS84 ellipsoid, the only ellipsoid currently supported in Coin. Author Generated automatically by Doxygen for Coin from the source code. Version 3.1.3 Wed May 23 2012 SoGeoOrigin(3)
All times are GMT -4. The time now is 06:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy