A simple approach:
1. Import the CSV and delete all records with 0,0 for latitude and longitude. Those don't add anything.
2. Create a drawing of points. There are example topics that show how to do that. Each point now has a LineID attribute
3. With the focus on that drawing in the Transform pane choose Merge : points and group by LineID, saving the result into a new drawing called Merged points.
4. Open the Merged points drawing. All the "points" are still there, except now that instead of being separate point objects they are part of multipoints, where each multipoint object has all the former "points" that have the same LineID.
5. You can now use the Transform pane to Convert : line to convert those multipoints into lines if you make the following modification:
Press the Edit Query button, and in the query that is written, change the line
GeomConvertToLine( GeomConvertToPoint([Geom], FALSE) )
Make that modification, and then run the query by pressing the ! button in the main toolbar. You get a drawing of lines, with each line having the same LineID as the multipoint that was used to create it.
What's going on is that the Merge template uses a function to merge points grouped by LineID, but in the multipoints it creates each point as a separate branch. If you create lines from those, you create as many zero length lines as you have branches. So you have to collapse the multipoints of many branches into multipoints with only one branch each.
The quickest way to do that is to use the GeomConvertToPoint function with a FALSE argument (meaning, don't create separate branches) to convert the mulitipoints with branches into multipoints without branches (see the user manual for arguments to that function). Do that inside of the GeomConvertToLine function so it all happens in one go.
A caveat: The above is a risky method because it depends on the points appearing in the initial table in the order in which they should be used to define a line, for each LineID. That only will work if the CSV file presents all the points in the desired order, and if that order isn't changed in the table. You can't assume tables have any particular order, so taking advantage of the order in which records just happened to be added when the table was created is risky, although it does work in the case of simple things like importing a CSV.
A more elegant approach, if the PointID field gives the order of the points to be used as vertices for each particular LineID, would be to modify the query that does the Merge grouping by LineID to order the points being merged by their PointID. No doubt the SQL folks in this forum could provide an example that would be more elegant than whatever I could hack up. :-)