SQL/MM Spatial exception - start node not geometry start point

[3nids]

Running the same demo set as fot ticket 1613, produces the following error:

psql:strk.demo.sql:18: ERROR:  SQL/MM Spatial exception - start node not geometry start point.

CONTEXT:  SQL statement "SELECT ST_ChangeEdgeGeom(atopology, rec.edge_id, snapedge)"

PL/pgSQL function "topogeo_addpoint" line 83 at PERFORM
PL/pgSQL function "topogeo_addlinestring" line 111 at assignment

SQL statement "INSERT INTO test_topo.relation(topogeo_id, layer_id, element_type, element_id) SELECT 2, 1, 2, topogeo_addLineString('test_topo', '0102000020155500000B000000BAF06A7E96F92041CD9B5862AAAF01417C5F9E5897F92041C5021D65AAAF0141713D0A57BDF920415C8FC2F5B4AF01411F85EB51D7F92041F6285C8FB8AF014148E17A142CFA2041C3F5285CC1AF0141F6285C8F3AFA2041B81E85EBC7AF0141AE47E1FA50FA204166666666C6AF01415CA1BCED53FA2041A41C48D6C8AF014148E17A1460FA204114AE47E1D2AF0141D1AC322684FA2041A3ECA94C02B001418FC2F5A895FA2041D7A3703D1AB00141'::geometry, 0);"
PL/pgSQL function "totopogeom" line 116 at EXECUTE statement

[lrssvt]

I get the same error.

[3nids]

With debug output:

Edge within 0 distance from node still does not contain the node after snapping to it with tolerance 2.00256322663555e-09

[strk]

Didn't check yet but I suspect ST_Snap snapped the first point of the edge rather than snapping the first segment. Re-adding the first point might fix this case.

[strk]

Fixed with r9352 (yes, it was first point being snapped)