External Map Applications - Revision history

Anw: test

2024-05-17T06:19:14Z

test

← Older revision		Revision as of 08:19, 17 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
	~~[[Category:TEST\|150]]~~

Anw: test

2024-05-14T12:54:53Z

test

← Older revision		Revision as of 14:54, 14 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
	[[Category:TEST]]		[[Category:TEST\|150]]

Anw: test

2024-05-14T12:50:41Z

test

← Older revision		Revision as of 14:50, 14 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
			[[Category:TEST]]

Anw: Undo revision 6764 by Anw (Talk)

2024-05-14T12:22:23Z

Undo revision 6764 by Anw (Talk)

← Older revision		Revision as of 14:22, 14 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
	~~[[Category:TEST]]~~

Anw: test

2024-05-14T11:12:15Z

test

← Older revision		Revision as of 13:12, 14 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
			[[Category:TEST]]

Anw at 12:24, 11 May 2011

2011-05-11T12:24:44Z

← Older revision		Revision as of 14:24, 11 May 2011
Line 47:		Line 47:
	# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[C-TMS]] location with the calculated data and marks the request as processed.		# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[C-TMS]] location with the calculated data and marks the request as processed.
	# The end-to-end process typically takes less than a second or so.		# The end-to-end process typically takes less than a second or so.

			[[Category:C-TMS_Key_Functionality\|150]]
			[[Category:C-TMS User Guide\|A-150]]

Admin at 11:58, 12 November 2010

2010-11-12T11:58:00Z

Crisfordm: /* Drive Time and Distance Calculation using External Map Application */

2009-06-15T15:51:11Z

Drive Time and Distance Calculation using External Map Application

← Older revision		Revision as of 17:51, 15 June 2009
Line 9:		Line 9:
	</ul>		</ul>

	By introducing ~~PC Miler~~ or MapPoint the following [[MTS]] functionality is made available:		By introducing NAVTEQ or MapPoint the following [[MTS]] functionality is made available:

	<ul>		<ul>
	<li>~~PC Miler~~ or MapPoint allow for Times and Distances to be generated on the fly, by passing in the source and destination long/lat coordinates, and then calculating the journey based on a road network using various road speeds depending on the class of road used.</li>		<li>NAVTEQ or MapPoint allow for Times and Distances to be generated on the fly, by passing in the source and destination long/lat coordinates, and then calculating the journey based on a road network using various road speeds depending on the class of road used.</li>
	</ul>		</ul>

Line 22:		Line 22:
	# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[MTS]] Trip Stops with the calculated data and marks the request as processed.		# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[MTS]] Trip Stops with the calculated data and marks the request as processed.
	# The end-to-end process typically takes a second or so and usually occurs in real time.		# The end-to-end process typically takes a second or so and usually occurs in real time.


	== Latitude/Longitude Calculation using External Map Application ==		== Latitude/Longitude Calculation using External Map Application ==

Crisfordm at 09:53, 31 December 2008

2008-12-31T09:53:32Z

Crisfordm at 14:38, 30 December 2008

2008-12-30T14:38:54Z

← Older revision		Revision as of 16:38, 30 December 2008
Line 1:		Line 1:


	== Drive Time and Distance Calculation using External Map Application ==		== Drive Time and Distance Calculation using External Map Application ==

← Older revision		Revision as of 08:19, 17 May 2024
Line 50:		Line 50:
	[[Category:C-TMS_Key_Functionality\|150]]		[[Category:C-TMS_Key_Functionality\|150]]
	[[Category:C-TMS User Guide\|A-150]]		[[Category:C-TMS User Guide\|A-150]]
	~~[[Category:TEST\|150]]~~

← Older revision		Revision as of 13:58, 12 November 2010
Line 1:		Line 1:
	== Drive Time and Distance Calculation using External Map Application ==		== Drive Time and Distance Calculation using External Map Application ==

	When a customer needs to deliver to new locations on a regular basis, there needs to be a method by which [[~~MTS~~]] can gain reasonably accurate drive times and distances for the journey legs that it creates.		When a customer needs to deliver to new locations on a regular basis, there needs to be a method by which [[C-TMS]] can gain reasonably accurate drive times and distances for the journey legs that it creates.
	There are other methods that already exist within [[~~MTS~~]], such as Pythagoras and Time & Distance Matrix: -		There are other methods that already exist within [[C-TMS]], such as Pythagoras and Time & Distance Matrix: -

	<ul>		<ul>
	<li>Pythagoras - calculating the distance using Pythagoras (plus a wiggle factor) then using an average speed to calculate the drive time. Note that the distance unit, i.e. miles or kilometers, is determined by the system parameter GEO_DT_DISTANCE_UNITS which is configured by the superuser in conjunction with the [[~~MTS~~]] Application Team.</li>		<li>Pythagoras - calculating the distance using Pythagoras (plus a wiggle factor) then using an average speed to calculate the drive time. Note that the distance unit, i.e. miles or kilometers, is determined by the system parameter GEO_DT_DISTANCE_UNITS which is configured by the superuser in conjunction with the [[C-TMS]] Application Team.</li>
	<li>Time & Distance Matrix – a matrix of times and distances, held in a table, which needs to be pre-populated using the output from another system (such as Paragon Routing).</li>		<li>Time & Distance Matrix – a matrix of times and distances, held in a table, which needs to be pre-populated using the output from another system (such as Paragon Routing).</li>
	</ul>		</ul>

	By introducing NAVTEQ or MapPoint the following [[~~MTS~~]] functionality is made available:		By introducing NAVTEQ or MapPoint the following [[C-TMS]] functionality is made available:

	<ul>		<ul>
Line 16:		Line 16:

	In summary, the functional process is as follows (using MapPoint as an example):		In summary, the functional process is as follows (using MapPoint as an example):
	# [[~~MTS~~]] “Get Time and Distance” function is called when the drive time and distance is required between two trip stop locations (a journey leg), such as when pressing a “Calc Dist & Time” button.		# [[C-TMS]] “Get Time and Distance” function is called when the drive time and distance is required between two trip stop locations (a journey leg), such as when pressing a “Calc Dist & Time” button.
	# A request is queued to the MapPoint Interface program (named “CBDS Interface”). The request simply includes the data that the CBDS Interface program needs to calculate drive time and distance using MapPoint, such as location latitude and longitude (lat/Long) of each location.		# A request is queued to the MapPoint Interface program (named “CBDS Interface”). The request simply includes the data that the CBDS Interface program needs to calculate drive time and distance using MapPoint, such as location latitude and longitude (lat/Long) of each location.
	# The queued request is picked up by the CBDS Interface which then initiates a background MapPoint “session”. The lat/long of the two locations is used to pin-point the journey leg locations on a MapPoint map.		# The queued request is picked up by the CBDS Interface which then initiates a background MapPoint “session”. The lat/long of the two locations is used to pin-point the journey leg locations on a MapPoint map.
	# Once the two locations are pin-pointed on the map, a route is created between the two. The route follows the road network and considers the parameters configured in the CBDS Interface, such as whether to use KM or Miles and Road Speeds.		# Once the two locations are pin-pointed on the map, a route is created between the two. The route follows the road network and considers the parameters configured in the CBDS Interface, such as whether to use KM or Miles and Road Speeds.
	# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[~~MTS~~]] Trip Stops with the calculated data and marks the request as processed.		# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[C-TMS]] Trip Stops with the calculated data and marks the request as processed.
	# The end-to-end process typically takes a second or so and usually occurs in real time.		# The end-to-end process typically takes a second or so and usually occurs in real time.

Line 26:		Line 26:

	To achieve the best distance and drive time results using MapPoint, each location on a journey leg should have both latitude and longitude. This ensures that each location can be pin-pointed in an external map application without ambiguity.		To achieve the best distance and drive time results using MapPoint, each location on a journey leg should have both latitude and longitude. This ensures that each location can be pin-pointed in an external map application without ambiguity.
	However, in some cases locations will be provided without latitude and longitude (lat/long). In such situations the lat/long must be calculated when the location is created in [[~~MTS~~]]. Once the lat/long has been applied to the location, the standard process of calculating distance and drive time by lat/long can be followed.		However, in some cases locations will be provided without latitude and longitude (lat/long). In such situations the lat/long must be calculated when the location is created in [[C-TMS]]. Once the lat/long has been applied to the location, the standard process of calculating distance and drive time by lat/long can be followed.
	MapPoint can be used to calculate the lat/long for a location as long as the necessary address data is available for the location to be pin-pointed in MapPoint. The full set of address information is as follows:		MapPoint can be used to calculate the lat/long for a location as long as the necessary address data is available for the location to be pin-pointed in MapPoint. The full set of address information is as follows:

Line 42:		Line 42:
	In summary, the functional process is as follows (using MapPoint as an example):		In summary, the functional process is as follows (using MapPoint as an example):

	# When a Location is created in [[~~MTS~~]], the location is checked to see that if has lat/long. If not, the location is checked in more detail to see if it contains enough address data to calculate the lat/long. Typically the minimum address data required is as mentioned above, City, Postal Code and Country. If enough address data exists on the location a request is queued to the MapPoint interface program (CBDS Interface) to calculate the lat/long.		# When a Location is created in [[C-TMS]], the location is checked to see that if has lat/long. If not, the location is checked in more detail to see if it contains enough address data to calculate the lat/long. Typically the minimum address data required is as mentioned above, City, Postal Code and Country. If enough address data exists on the location a request is queued to the MapPoint interface program (CBDS Interface) to calculate the lat/long.
	# The queued request is picked up by the CBDS Interface (note that a lat/long calculation request is processed differently to a time and distance request) which then initiates a background MapPoint “session”. The locations for which lat/long is to be calculated is pin-pointed on a MapPoint map using the address data. (MapPoint provides numerous ways of pin-pointing locations, two of which are by lat/long as used in time and distance calculations, and by address as used here).		# The queued request is picked up by the CBDS Interface (note that a lat/long calculation request is processed differently to a time and distance request) which then initiates a background MapPoint “session”. The locations for which lat/long is to be calculated is pin-pointed on a MapPoint map using the address data. (MapPoint provides numerous ways of pin-pointing locations, two of which are by lat/long as used in time and distance calculations, and by address as used here).
	# Once the location is pin-pointed on the map, an algorithm is used to calculate the latitude and longitude of the location.		# Once the location is pin-pointed on the map, an algorithm is used to calculate the latitude and longitude of the location.
	# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[~~MTS~~]] location with the calculated data and marks the request as processed.		# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[C-TMS]] location with the calculated data and marks the request as processed.
	# The end-to-end process typically takes less than a second or so.		# The end-to-end process typically takes less than a second or so.

← Older revision		Revision as of 11:53, 31 December 2008
Line 1:		Line 1:
	== Drive Time and Distance Calculation using External Map Application ==		== Drive Time and Distance Calculation using External Map Application ==

	When a customer needs to deliver to new locations on a regular basis, there needs to be a method by which MTS can gain reasonably accurate drive times and distances for the journey legs that it creates.		When a customer needs to deliver to new locations on a regular basis, there needs to be a method by which [[MTS]] can gain reasonably accurate drive times and distances for the journey legs that it creates.
	There are other methods that already exist within MTS, such as Pythagoras and Time & Distance Matrix: -		There are other methods that already exist within [[MTS]], such as Pythagoras and Time & Distance Matrix: -

	<ul>		<ul>
	<li>Pythagoras - calculating the distance using Pythagoras (plus a wiggle factor) then using an average speed to calculate the drive time. Note that the distance unit, i.e. miles or kilometers, is determined by the system parameter GEO_DT_DISTANCE_UNITS which is configured by the superuser in conjunction with the MTS ~~Support~~ Team.</li>		<li>Pythagoras - calculating the distance using Pythagoras (plus a wiggle factor) then using an average speed to calculate the drive time. Note that the distance unit, i.e. miles or kilometers, is determined by the system parameter GEO_DT_DISTANCE_UNITS which is configured by the superuser in conjunction with the [[MTS]] Application Team.</li>
	<li>Time & Distance Matrix – a matrix of times and distances, held in a table, which needs to be pre-populated using the output from another system (such as Paragon Routing).</li>		<li>Time & Distance Matrix – a matrix of times and distances, held in a table, which needs to be pre-populated using the output from another system (such as Paragon Routing).</li>
	</ul>		</ul>

	By introducing PC Miler or MapPoint the following MTS functionality is made available:		By introducing PC Miler or MapPoint the following [[MTS]] functionality is made available:

	<ul>		<ul>
Line 16:		Line 16:

	In summary, the functional process is as follows (using MapPoint as an example):		In summary, the functional process is as follows (using MapPoint as an example):
	# MTS “Get Time and Distance” function is called when the drive time and distance is required between two trip stop locations (a journey leg), such as when pressing a “Calc Dist & Time” button.		# [[MTS]] “Get Time and Distance” function is called when the drive time and distance is required between two trip stop locations (a journey leg), such as when pressing a “Calc Dist & Time” button.
	# A request is queued to the MapPoint Interface program (named “CBDS Interface”). The request simply includes the data that the CBDS Interface program needs to calculate drive time and distance using MapPoint, such as location latitude and longitude (lat/Long) of each location.		# A request is queued to the MapPoint Interface program (named “CBDS Interface”). The request simply includes the data that the CBDS Interface program needs to calculate drive time and distance using MapPoint, such as location latitude and longitude (lat/Long) of each location.
	# The queued request is picked up by the CBDS Interface which then initiates a background MapPoint “session”. The lat/long of the two locations is used to pin-point the journey leg locations on a MapPoint map.		# The queued request is picked up by the CBDS Interface which then initiates a background MapPoint “session”. The lat/long of the two locations is used to pin-point the journey leg locations on a MapPoint map.
	# Once the two locations are pin-pointed on the map, a route is created between the two. The route follows the road network and considers the parameters configured in the CBDS Interface, such as whether to use KM or Miles and Road Speeds.		# Once the two locations are pin-pointed on the map, a route is created between the two. The route follows the road network and considers the parameters configured in the CBDS Interface, such as whether to use KM or Miles and Road Speeds.
	# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the MTS Trip Stops with the calculated data and marks the request as processed.		# Once the route is complete, the Distance and Drive Time are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[MTS]] Trip Stops with the calculated data and marks the request as processed.
	# The end-to-end process typically takes a second or so and usually occurs in real time.		# The end-to-end process typically takes a second or so and usually occurs in real time.

Line 27:		Line 27:

	To achieve the best distance and drive time results using MapPoint, each location on a journey leg should have both latitude and longitude. This ensures that each location can be pin-pointed in an external map application without ambiguity.		To achieve the best distance and drive time results using MapPoint, each location on a journey leg should have both latitude and longitude. This ensures that each location can be pin-pointed in an external map application without ambiguity.
	However, in some cases locations will be provided without latitude and longitude (lat/long). In such situations the lat/long must be calculated when the location is created in MTS. Once the lat/long has been applied to the location, the standard process of calculating distance and drive time by lat/long can be followed.		However, in some cases locations will be provided without latitude and longitude (lat/long). In such situations the lat/long must be calculated when the location is created in [[MTS]]. Once the lat/long has been applied to the location, the standard process of calculating distance and drive time by lat/long can be followed.
	MapPoint can be used to calculate the lat/long for a location as long as the necessary address data is available for the location to be pin-pointed in MapPoint. The full set of address information is as follows:		MapPoint can be used to calculate the lat/long for a location as long as the necessary address data is available for the location to be pin-pointed in MapPoint. The full set of address information is as follows:

Line 43:		Line 43:
	In summary, the functional process is as follows (using MapPoint as an example):		In summary, the functional process is as follows (using MapPoint as an example):

	# When a Location is created in MTS, the location is checked to see that if has lat/long. If not, the location is checked in more detail to see if it contains enough address data to calculate the lat/long. Typically the minimum address data required is as mentioned above, City, Postal Code and Country. If enough address data exists on the location a request is queued to the MapPoint interface program (CBDS Interface) to calculate the lat/long.		# When a Location is created in [[MTS]], the location is checked to see that if has lat/long. If not, the location is checked in more detail to see if it contains enough address data to calculate the lat/long. Typically the minimum address data required is as mentioned above, City, Postal Code and Country. If enough address data exists on the location a request is queued to the MapPoint interface program (CBDS Interface) to calculate the lat/long.
	# The queued request is picked up by the CBDS Interface (note that a lat/long calculation request is processed differently to a time and distance request) which then initiates a background MapPoint “session”. The locations for which lat/long is to be calculated is pin-pointed on a MapPoint map using the address data. (MapPoint provides numerous ways of pin-pointing locations, two of which are by lat/long as used in time and distance calculations, and by address as used here).		# The queued request is picked up by the CBDS Interface (note that a lat/long calculation request is processed differently to a time and distance request) which then initiates a background MapPoint “session”. The locations for which lat/long is to be calculated is pin-pointed on a MapPoint map using the address data. (MapPoint provides numerous ways of pin-pointing locations, two of which are by lat/long as used in time and distance calculations, and by address as used here).
	# Once the location is pin-pointed on the map, an algorithm is used to calculate the latitude and longitude of the location.		# Once the location is pin-pointed on the map, an algorithm is used to calculate the latitude and longitude of the location.
	# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the MTS location with the calculated data and marks the request as processed.		# Once the algorithm is complete the lat/long are returned from MapPoint to the CBDS Interface program. The CBDS Interface program then updates the [[MTS]] location with the calculated data and marks the request as processed.
	# The end-to-end process typically takes less than a second or so.		# The end-to-end process typically takes less than a second or so.