Frequently Asked Questions

Top  Previous  Next

Why does MPRouteWriter fail to write all the field data for my pushpins?

 

This can happen for a number of reasons. The most common reason is that the pushpin must exist and have all the expected field data.

 

MPRouteWriter will only report a waypoint's pushpin data if MapPoint can find a unique matching pushpin for the waypoint. The pushpin's name has to match the waypoint's name exactly.

 

Multiple pushpins with the same name can also result in blank field data. See Why does MPRouteWriter sometimes match the 'wrong' pushpin to a waypoint? below for information on fixing this.

 

It is also strongly recommended that the pushpin Name2 field is avoided when importing pushpin data. MapPoint will usually concatenate the Name and Name2 fields. Although this should be okay in theory, practice has shown that MapPoint then has trouble matching the resulting waypoint and pushpin names. Set Name2 (if detected) to 'ignore' when importing or linking input data.

 

Corrupt, null, or missing field values will also be written as empty cells. MPRouteWriter will report the presence of such data fields with a warning message after processing has completed. It is also possible to have pushpins which have not been located (eg. if a data link has been refreshed). These are reported with empty location fields.

 

 

 

Why does MPRouteWriter sometimes match the 'wrong' pushpin to a waypoint?

 

This can happen because you have multiple pushpins with the same name. These pushpins might be in different datasets. Pushpins with non-unique names are controlled with the Resolve duplicate matching pushpins checkbox on the main MPRouteWriter panel.

 

The default is for this checkbox to be cleared. This is the fastest option, and results in MPRouteWriter reporting the first pushpin that has a matching name. It will not compare duplicates. You should ensure that your pushpins have unique names, if you use this option.

 

Setting this checkbox will cause MPRouteWriter to find all pushpins with a matching name. It will then choose the pushpin that is closest to the waypoint. Note that this option can take a few minutes, especially if you have a lot of pushpins on your map.

 

 

 

How are rest stops detected?

 

Rest stops (or breaks) can be automatically inserted into a route by MapPoint and MPRouteWriter. You can switch them on or off, set the interval between breaks, and the length of the breaks. These rest breaks appear in the route directions. MPRouteWriter can detect these and include them in the route output. Do this by setting the Output Rest Stops check box on the MPRouteWriter panel, and then set the rest stop length and interval.

 

Each geographic edition marks the rest stop with a different set of words. MPRouteWriter uses these same words in the output data. These words are:

 

MapPoint Edition

Rest Stop Words

North America

Rest break

Europe: Engish

Rest break

Europe: German

Pause

Europe: French

Halte

Europe: Italian

Sosta

Europe: Spanish

Parada de descanso

 

 

How do I create a route from pushpins whilst specifying a particular order?

 

This can be performed using the MPRouteReader panel.

 

 

Why is MapPoint not including a specified rest stop or waypoint time in the total time?

 

This happens when the stop occurs at the end of the day. The stop would take the time past the specified daily driving time (typically 8 hours), so MapPoint counts the stop as a part of the post-driving rest time - i.e. it is not included. This is only a problem if the route takes at least one day.