at the end my solution is the following one: 1) create a table with all the possible routes; 2) use search function of pmapper to query my track; 3) use a route layer in background: it is in the mapfile but not in config.xlm; in this way I can use it and see the query results like an highlight;
this is a workaround because I didn't figure out to use dynamically the pgrouting inside pmapper. I think an advantage is faster reply of server but every time I change a route I have to regenerate my table. Actually it isn't a problem because I create a php ad hoc -- View this message in context: http://pmapper-users-p-mapper-users-mailing-list.993774.n3.nabble.com/pmapper-users-pgrouting-tp4025437p4025614.html Sent from the pmapper-users -- p.mapper users mailing list mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
