HomeMicrosoftWish List


Convert Stops to Pushpins in Microsoft Streets & Trips
SpadesFlush
Pushpins are an easy way of sharing location data from one map view or itinerary to another. It would be nice if Stops (or waypoints) could be easily converted to Pushpins so that those data points could be shared as Pushpins on multiple itineraries.
SpadesFlush
I know it has taken me more than two years to come up with a work-around solution to this deficiency in Streets and Trips but I offer it nonetheless and also in full recognition of the fact that this does not seem to be a burning issue for you other S&T users nor Microsoft who does not seem to be inclined to deal with it.

The following steps convert multiple route stops to a pushpin set. One route is converted to one set but, of course, you can combine multiple sets into one map file.

1. Open the S&T map file that is populated with the stops you want to convert and export that file to GPX [Data>Export to GPX file], naming it anything you like.

2. Open that GPX file in Excel as an XML file, a prompted choice, and clicking on "Yes" when queried about the 'schema'.

3. Save that file [File>Save as] (without doing anything to it) as an XLS or XLSX file named anything you like but bearing in mind that whatever you name it will be the new pushpin set's name.

4. Revert to S&T and open a file (either a fresh file or a preferred target file) and import that XLS/XLSX file [Data>Import data wizard]. The data wizard will now take you through steps to convert that data file to a pushpin set. At this stage you need to be careful that only three columns are active and all the others are inactive. To do this, un-tick the box entitled "First row contains column headings" in the second wizard pane and then find the three columns that S&T will use for pushins: Latitude, Longitude and Name. Select from the drop-down choices in the "Data type" row the respective appropriate heading. In my experimentations, I found that Latitudes are in the F54 column (in other words quite far to the right), Longitudes are in the F55 column, and Names are in the F60 column. At this point, the "Finish" box, the middle one of five at the bottom of this wizard panel should be clickable (i.e., not grey-ed out) and you should click on it. That will produce a new pushpin set and the map will zoom to a view of those new pushpins.

5. It is probably a good idea to save this newly-created file after each pushpin set is created as I have had S&T "crash" in the process of doing the step 4 conversion once in a while.

6. Repeat as required for multiple routes.

Note that using this approach also could be the basis for combining multiple route files into a single route. A standard capability of S&T is to convert pushpins to stops, so all one need do is to do the above for multiple sets and then select those sets for conversion to stops [Add pushpins as stops] and calculate a new route.
MisterMoonlight
Wow!

Nice workaround to get that new feature.

Well done
Marvin Hlavac
Nice one! It has been added to our tips page.
SpadesFlush
Thanks, guys.
SpadesFlush
I would like to revise my Step #2 above and suggest that you open the GPX file selecting the "As a read-only workbook" option rather than the "As an XML table" because that format is easier to work with for these purposes. We learn by doing.

Also, you might prefer entering the column headings in the first row ("Latitude", "Longitude", "Name", and others and then using that row when you import the data. It gives you somewhat more control and it is useful if you are incorporating a lot of secondary data about your pushpins, such as addresses, telephone numbers, contact names, into your pushpin balloons. For instance, this could be very useful in a sales management environment, subject to Keith's observations, if any.
GoneNomad
Quote:
Originally Posted by SpadesFlush
Pushpins are an easy way of sharing location data from one map view or itinerary to another. It would be nice if Stops (or waypoints) could be easily converted to Pushpins so that those data points could be shared as Pushpins on multiple itineraries.
I agree that this should be built in to S&T. And I'd also like to have a way to convert groups of the built-in POIs into waypoints or pushpins. I don't think pushpins need to be treated differently and separately from the built-in POI "places" either.

BTW, it looks like the oldest version of Excel that will open .XML files is 2003:
"XL2000 does not support this, and neither does XL2002 - it was first implemented in XL2003.
What I did when a supplier switched to issuing XML files was to use OpenOffice to open the file (it's a free download) and then save it from there as a proper .xls file.
"
ref.: http://www.excelbanter.com/showpost.php?p=907187&postcount=2

Looking at what is in different .GPX files that either have only pushpins in them (no route) or route points (no pushpins), it appears to me that the difference is that routes are referred to as "rte" and route points are referred to as "rtept" and pushpin points are referred to as "wpt"

A record in the GPX file that is imported into S&T as a pushpin point looks like this:
<type>Church's r2 (from church's website)</type></wpt><wpt lat="38.6594717589191" lon="-90.2179675012716"><name>Churchs Chicken</name><desc>3525 North Grand Blvd, St. Louis, MO 63107</desc>
and the entire list of pushpin points is immediately preceded by "<wpt>" and followed by "</wpt></gpx>"

A record in the GPX file that is imported into S&T as a route point looks like this:
<time>Invalid DateTime-06:00</time></rtept><rtept lat="40.8227467071265" lon="-97.1700020134449"><name>near Goehner</name><time>Invalid DateTime-06:00</time></rtept>
and the entire list of route points is immediately preceded by "<rte>" and followed by "</rte></gpx>
"

So if you export a .GPX from S&T, then open it in any text editor capable of saving back out as .XML, search & replace the appropriate text strings to convert all the "rtept" to "wpt" and then re-import the .GPX file into S&T, that should convert all the route points to pushpin points.

I don't have anything on this computer to test that with, but anyone finds that this works, let me know.

Based on the minor differences in the GPX files, it sure looks like it wouldn't be difficult for Microsoft to add a routepoint-to-pushpin conversion feature, and that would sure make it easier.
laptopgpsworld.com About