<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Icepack Street Router on API Documentation</title>
    <link>https://docs.icepack.ai/isr/</link>
    <description>Recent content in The Icepack Street Router on API Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 19 Dec 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://docs.icepack.ai/isr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configuration</title>
      <link>https://docs.icepack.ai/isr/configuration/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/configuration/</guid>
      <description>Overview The configuration for a Icepack Street Routing (ISR) model is designed to encapsulate the high-level features that are present in street-level routing problems. Often such street routing problems hinge on multiple collections along the same street segment (defined by the section of a road between two other roads). It would be unusual to split up such collections along a street and are rather required to make decisions between streets that are visited.</description>
    </item>
    <item>
      <title>Geocode</title>
      <link>https://docs.icepack.ai/isr/geocode/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/geocode/</guid>
      <description>Overview The term geocode is used to describe a pair of coordinates. In general, we mostly handle routing requests which are on the face of planet earth so we&amp;rsquo;ve biased the terminology used here in that direction.&#xA;In the context of the ISR model, we only currently support road network queries which means that the geocode here must be a longitude/latitude pair on the face of planet earth.&#xA;Applicable models ISR isr-z4foi53qznrv Geocode A longitude/latitude pair for routing on the face of planet earth which are used to determine entry and exit points on the road network.</description>
    </item>
    <item>
      <title>Offload Site</title>
      <link>https://docs.icepack.ai/isr/offloadsite/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/offloadsite/</guid>
      <description>Overview An offload site in the context of the ISR model is a location where the collections accrued on a trip are delivered. It&amp;rsquo;s common that an offload site corresponds to a dump site or similar location.&#xA;Applicable models ISR isr-z4foi53qznrv Offload Site Schema definition message OffloadSite { required string id = 1; required Geocode location = 2; required float fixedOffloadTime = 3 [default = 0.0]; required float offloadTimePerQuantity = 4 [default = 0.</description>
    </item>
    <item>
      <title>Collection</title>
      <link>https://docs.icepack.ai/isr/collection/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/collection/</guid>
      <description>Overview A collection is a particular location on the street which requires a collection to be performed. A collection has both a time and quantity which contribute to the constraints in the time dimension and vehicle capacity dimension, respectively.&#xA;A model will typically consist of many collections which are destined for a common offload site. We include the offload site in this current specification for future potential decompositions which may be required.</description>
    </item>
    <item>
      <title>Vehicle</title>
      <link>https://docs.icepack.ai/isr/vehicle/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/vehicle/</guid>
      <description>Overview The vehicle component of the ISR model describes important features of the vehicle such as its start and end locations for the day, its available working time and the maximum number it may load before the vehicle is required to visit an offload site.&#xA;Applicable models ISR isr-z4foi53qznrv Vehicle A model may contain multiple allowable vehicles for a particular solution. Each vehicle may have a different start/end location, available working time and capacity.</description>
    </item>
    <item>
      <title>Collection Sequence</title>
      <link>https://docs.icepack.ai/isr/collectionsequence/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/collectionsequence/</guid>
      <description>Overview A collection sequence is used to provide a fixed sequence to the solver, either to be used as a starting incumbent in a reoptimise procedure or as a fixed sequence to be evaluated for infeasibilities.&#xA;Applicable models ISR isr-z4foi53qznrv Collection Sequence The collection sequence is a list of task id&amp;rsquo;s, which are mostly collection identifiers with the dropoff site id&amp;rsquo;s where applicable. In other words, its the sequence that the vehicle should follow through collection, offloading and then potentially collecting again.</description>
    </item>
    <item>
      <title>Model</title>
      <link>https://docs.icepack.ai/isr/model/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/model/</guid>
      <description>Overview The model is a container for all the components that should be combined to describe a problem instance. In the case of the ISR model we&amp;rsquo;ll be required to provide all of the fields except for the collection sequence (which is optional).&#xA;Applicable models ISR isr-z4foi53qznrv Model The model defines an instance of the desired problem to be solved.&#xA;Schema definition message Model { required Configuration configuration = 1; repeated Collection collections = 2; repeated OffloadSite offloadSites = 3; repeated Vehicle vehicles = 4; repeated CollectionSequence collectionSequence = 5; } Fields configuration The configuration defining the costs, travel factors, units of measurement and collection policies for this model.</description>
    </item>
    <item>
      <title>Solve Request</title>
      <link>https://docs.icepack.ai/isr/solverequest/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/solverequest/</guid>
      <description>Overview Different actions can be performed against a model and the solve request object provides a mechanism to communicate the action to the solver.&#xA;Applicable models ISR isr-z4foi53qznrv Endpoint POST: https://api.icepack.ai/vehicle-router/solve/ Solve Request The solve request indicates what type of solve should be performed against a specified model.&#xA;Schema definition message SolveRequest { optional Model model = 1; optional string modelID = 2; repeated VisitSequence routes = 3; optional SolveType solveType = 4 [default = Optimise]; } Fields model The target model which should be solved (commonly specified).</description>
    </item>
    <item>
      <title>Solution Response</title>
      <link>https://docs.icepack.ai/isr/solutionresponse/</link>
      <pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://docs.icepack.ai/isr/solutionresponse/</guid>
      <description>Overview The solution response is produced by the API as an output object for a given solve request. This is considered the primary output from the Icepack engine. The solution response contains all the evaluation information for each vehicle, i.e. travel durations and distances between collections as well as the streets and matching information in the schedule.&#xA;Applicable models ISR isr-z4foi53qznrv Solution Response The solution response contains five core elements. The first is the objective cost of the schedule which is the total cost as evaluated by the engine given the input model parameters (such as the cost coefficient parameters by the configuration).</description>
    </item>
  </channel>
</rss>
