I don't have correct solution, but problem is: you have WGS coordinates and you don't specify coordinate system. Therefore, those are just planar coordinates, with distances less than 0.01 units between points. Of course there aren't any points added, when you try to segmentize them with 10 units value.
–
user1702401Jan 16 '13 at 15:50

Result geometry is now from startpoint to closest point on line to used point. no reason to segmentize or anythign else. This need that data is "LINESTRING" type, MULTI* wont work

Also point and linestring data has to be in same srid, you can transform dat using ST_Transform(...)

-- select one point from table, get closests line and return linegeometry
-- which is from start to closestpoint
SELECT ST_Line_Substring(a_linestring, 0 , ST_Line_Locate_Point(a_linestring, a_point))
FROM lines l , point p
WHERE p.id =1 ORDER BY ST_Distance(a_linestring, p.a_point) LIMIT 1

Hi thanks for your answer. The reason for splitting the line into many points, is I'm routing from a road to a utility line, but closest point on the utility line is not the closest point on the line i can drive/route to, so finding nearest line, split that line into many points and then try to route to the points (binary search) and find shortest routing distance.
–
dk_nlsJan 17 '13 at 10:37

so do you have "utility" road in your data ?
–
simplexioJan 17 '13 at 10:54

I have one table with all roads, and one table with all cables. (I'm using commercial routing lib to do the routing, since I'm running postgres 9.2 and haven't had any luck with getting pgrouting to run on my dev. setup yet). I'm able to get my routes now, but there might be smarter ways?
–
dk_nlsJan 17 '13 at 11:59