162 |
Mapper let's users visualize datasets (problem instances) and solutions (routes) that are formatted according to
163 | the Vehicle Routing Problem REPository (VRP-REP) specifications.
164 |
165 |
More about VRP-REP and the specification can be found on our website.
166 |
167 |
Jump to
168 |
169 |
178 |
179 |
To use
180 |
181 |
182 |
183 |
184 |
185 |
If you don't have your own data
186 |
187 |
If you don't already have VRP-REP compliant datasets or solutions, select "Sample data".
188 |

190 |
191 |
From here, select "Plot sample dataset and solution" to view the Christofides et al. (1979) CMT01 instance
192 | and its solution.
193 |
194 |
You can also choose to download the source files for sample data using the "Download" button.
195 |
196 |
197 |
198 |
199 |
200 |
If you do have your own data
201 |
202 |
If you have your own VRP-REP compliant instances and solutions, then from the Mapper landing page,
203 | first select "Upload instance" to browse to and select a VRP-REP compliant dataset.
204 |
205 |

207 |
208 |
Once you have uploaded an instance, the upload solution functionality becomes available. Select "Upload solution."
209 |
210 |

212 |
213 |
From the modal that appears, you have two options to input a solution (a route or set of routes):
214 |
215 |
216 | - You may select "Browse" to select a VRP-REP compliant solution, or
217 |
218 | - You may simply input a sequence of integers into the text field. This sequence of integers should be separated
219 | either by commas or whitespace. After you input a sequence, hit the "Plot" button.
220 |
221 |
222 |
Note that whenever a new solution is uploaded or a new route is entered, the existing routes will be cleared.
223 |
224 |
225 |
226 |
227 |
228 |
229 |
230 |
Toggling route display
231 |
232 |
If you have uploaded a solution file that contains more than one route, you can toggle the display of the routes by clicking on the routes' legend entries.
233 |
234 |

235 |
236 |
237 |
238 |
The XML schema defining the VRP-REP solution format is available here.
239 |
240 |
A description of the format:
241 |
242 |
243 | -
244 |
The root element must be a <solution>
element, and it must contain a string attribute identifying
245 | the instance
(method
is optional).
246 |
247 |
248 | -
249 |
Within <solution>
must be at least one <route>
element with a mandatory
250 | and unique id
attribute (integer). <route>
elements may also contain any
251 | other attributes you want to add. For example, if your file reports the solution to a VRP with a limited
252 | fleet, you can add an attribute vehicle_id='X'
to the <route>
element, indicating
253 | that the route is serviced by vehicle 'X'.
254 |
255 |
256 | -
257 |
Within <route>
must be at least 2 <node>
s, each with a mandatory id
attribute (integer). <node>
elements may contain any child elements you wish to add. For
258 | example, if your file reports the solution to a VRP with split delivery, you can add to the <node>
element a <quantity>X</quantity>
child, indicating that the route services X units
259 | of the node's demand.
260 |
261 |
262 |
263 |
A sample solution file:
264 |

266 |