Update Traffic Data and Incidents Tools
Update Traffic Data
How to use Update Traffic Data Tool in Arc Toolbox ArcMap ArcGIS??
Update Traffic Data |
Path to access the tool
:
Update
Traffic Data Tool, Server Toolset, Network Analyst Tools Toolbox
Update Traffic Data
Downloads live traffic
data from a web service and stores it in a dynamic traffic format (DTF) file,
which is a file that network datasets can read for live-traffic analysis and display.
1. Provider
Choose the name of your traffic data provider and the region.
- HERE North America
- HERE Europe
- HERE South America
- HERE Middle East & Africa
- HERE Asia Pacific
- TomTom North America
- TomTom Europe
2. User Name
The user name authorized
by the data provider to download traffic data. The tool fails to execute if the
user name cannot be authenticated by the data provider.
If the Provider
parameter is TomTom North America or TomTom Europe, use "APIKEY" as
the parameter value.
3. Password
The password provided by
the data provider to download traffic data. The tool fails to execute if the
password cannot be authenticated by the data provider.
4. Regions
Check the regions for
which you want to download traffic data.
5. Traffic Data Output Folder
The folder in which the DTF
file will be created. If the folder is empty, the tool creates a
TrafficIndex.xml file along with the DTF file. For subsequent tool runs, the
tool updates TrafficIndex.xml and creates a DTF file.
If you download data
from multiple data providers, a unique folder should be specified for each data
provider.
6. Expected Update Interval in Minutes
The time interval in
minutes after which the downloaded traffic data is no longer up-to-date, and
the data provider makes available refreshed data. After this interval has
elapsed, it is recommended that you rerun the tool and download the latest
data.
7. Prediction Cutoff in Minutes
The time interval (in
minutes) for which the predictive traffic data is processed by the tool. Data
providers may supply predictive data for the next 24 hours, week, or other time
period. The time-span value for this parameter is used to limit the amount of
predictive traffic data that is processed by the tool to speed up tool
execution. For example, if your traffic provider has a prediction depth of 24
hours, but you need only one hour of prediction depth, you can save time by
specifying 60 here.
8. Compress Data
- Checked—Downloads the TrafficIndex.xml and DTF files, then creates copies of the DTF files in a zipped folder. Use this option if network datasets will connect to the live traffic data via a geoprocessing service; transferring the zipped folder of DTF files to clients is quicker than transferring the DTF files themselves.
- Unchecked—Downloads the TrafficIndex.xml and DTF files without creating copies of them in a zipped folder. Use this option if network datasets will connect to the live traffic data via a folder connection.
9. Maximum File Age in Minutes (optional)
The time interval (in
minutes) for which the traffic files (that is, the DTF files) will be kept in
the traffic data output folder. This parameter facilitates deleting traffic
files that are no longer required.
When the tool is rerun, any traffic data files
that are older than the maximum file age are deleted automatically. The default
value is 720 minutes (12 hours).
10. Speed Unit (optional)
The speed units when downloading data from a custom traffic feed. This parameter is ignored if you are using one of the standard commercial feeds that are documented in the Provider parameter.
- MPH—Miles per hour. This is the default.
- KPH—Kilometers per hour.
Specifying the proper
speed units of a custom traffic feed ensures the network dataset will interpret
the speed values correctly.
Update Traffic Incidents
How to use Update Traffic Incidents Tool in Arc Toolbox ArcMap ArcGIS??
Update Traffic Incidents |
Path to access the tool
:
Update
Traffic Incidents Tool, Server Toolset, Network Analyst Tools Toolbox
Update Traffic Incidents
Creates a point feature
class containing live traffic-incident data from a web service. Traffic
incidents include events such as accidents and road construction.
1. Provider
Choose the name of your traffic-incident data provider and the region.
- HERE North America
- HERE Europe
- HERE South America
- HERE Asia Pacific
- HERE Middle East & Africa
- TomTom North America
- TomTom Europe
2. User Name
The user name authorized
by the data provider to download incidents. The tool fails to execute if the
user name cannot be authenticated by the data provider.
If the Provider
parameter is TomTom North America or TomTom Europe, use APIKEY as the parameter
value.
3. Password
The password provided by
the data provider to download traffic-incident data. The tool fails to execute
if the password cannot be authenticated by the data provider.
4. Regions
Check the regions for
which you want to download traffic-incident data.
5. Incidents Feature Class Location
The geodatabase in which
the output feature class will be created. This workspace must already exist.
6. Incidents Feature Class Name
The name of the feature
class to be created. If the tool has been run before and the feature class already
exists,
the tool will delete existing features and create new ones based on the
most recent incident data.
7. Time Zone Boundaries (optional)
The polygon feature
class whose features delineate time zones. By providing this feature class,
incidents occurring within time zone boundaries can be reported in local time,
not only Coordinated Universal Time.
If you don't provide a
time zone boundaries feature class, incident start and end times can be
reported in Coordinated Universal Time (UTC) only; all local time fields are
assigned null values. Occasionally, certain incidents from traffic feeds such
as weather events have null geometries. In this situation, the local time
fields are assigned null values even if the time zone boundaries feature class
is provided.
Setting the Time Zone ID
Field property is required if you provide a time-zone-boundaries feature class.
8. Time Zone ID Field (optional)
The text field, from the
time-zone-boundaries feature class, that contains Windows time zone
identifiers.
The values in this field correspond to time zone keys in the Windows registry. You can follow similar steps to those outlined in the topic Adding time zones to a network dataset to find proper time zone names for the polygons in your input feature class.
Comments
Post a Comment