[pgrouting-dev] Support for Time Constraints

[Jay Mahadeokar]

> Hi Jay,
>
> I think that instead of just random times, I would take a different
> approach to generate this data. If we think about "rush hour" around a major
> city, the highways (based on road class) flowing into the city in the
> morning would get reduced average speeds you could apply curve like average
> speed*percent based on 6am (90%), 7am(75%), 8am(45%), 9am(50%), 10am(85%)
> and do something similar in the evening rush. It might be too hard to figure
> on direction of flow in/out bound so apply the curve to all traffic. The
> assumption is that the highways are congested which will force traffic onto
> side streets. You might want to also reduce the lower class speeds by say a
> constant 80% during rush hour.
>
> If we can get OSM data then it should be easy to populate the table with
> that data.
>
> -Steve
>

I am trying to write plpgsql query to generate time-dependent data
corresponding to the ways table in pgrouting workshop. As suggested by Steve
above, instead of generating random data, I will follow patterns (see above
message) so that the data is nearer to the real worlds scenario.

So, now I need to make distinction between highways, streets etc. I saw the
attribute class_id in ways table. It has 14 distinct values:
 class_id

----------


102


122


106


111


108


100


109


112


101


110


401


119


117

      114

Any specific meaning attached to these values? I did not find any
information on the pgRouting-workshop website [1].


Thanks in advance.

[1] http://workshop.pgrouting.org/chapters/topology.html

-- 
Regards,
-Jay Mahadeokar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20110612/76a86af0/attachment-0001.html