https://svn.boost.org/trac10/ticket/9345 <p> This task is related to <a class="ext-link" href="http://lists.boost.org/geometry/2013/11/2669.php"><span class="icon">​</span>Changes in WKB (read) behaviour proposal (WKT Part)</a> discussion on the list. </p> <p> We should try to add ability to consume/produce the M (measure) component from/to geometries encoded in OGC WKT and WKB formats. </p> <p> As Barend explained in the thread linked above: </p> <blockquote class="citation"> <p> We drop the M anyway (currently). We cannot handle it because our Point Concept does not contain model-values. Something additional would be necessary to be able to assign it to the point in question (strategy? policy? assigner?), which can do with it what it wants. An easy option would be assigning the M to the third dimension (if any), and that is probably currently the case (I have to check). </p> </blockquote> <p> I think a form of user-defined data assigner, similar to dimension assigners, which uses can enable for adapted geometries would be useful. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9345 Trac 1.4.3