Releases: pgRouting/osm2pgrouting
v2.3.0
To view the full list of issues:
Main changes are:
- Cost should not return the same value
- Added a points of Interest table
- Some default one_way values are taken into consideration
- Relations are also considered
- New mapconfig_for_pedestrian.xml
New Flags
--attributes Include attributes information.
--tags Include tag information.
--chunk arg (=20000) Exporting chunk size.
--no-index Do not create indexes (Use when indexes
are already created)
To packagers
A new dependency: libpqxx-dev
v2.2.0
The new documentation can be found here:
https://github.com/pgRouting/osm2pgrouting/wiki/Documentation-for-osm2pgrouting-v2.2
With this release the following changes have being done:
osm2pgRouting 2.2.0
- Adding foreign keys to the tables.
- Added a progress bar.
- New mapconfig_for_bicycles.xml
- Improved the C++ code.
- remove the use of pointers to avoid leaks.
- Table
osm_ways_tagsbecause information is redundant.
osm2pgrouting-2.1.0
With the release of osm2pgrouting 2.1.0, we start re-factoring of the code.
Various bugs have been fixed, connection flags with the database have the same name as of psql,
Its several times faster than version 2.0
To see the full list of changes check the list of Closed Issues on Github.
This is the documentation
osm2pgrouting-2.1.0-RC1
With the release of osm2pgrouting 2.1.0, we start re-factoring of the code.
Various bugs have been fixed, connection flags with the database have the same name as of psql,
Its several times faster than version 2.0
To see the full list of changes check the list of Closed Issues on Github.
This is the documentation
osm2pgrouting-2.1.0-beta
With the release of osm2pgrouting 2.1.0, we start re-factoring of the code.
Various bugs have been fixed, connection flags with the database have the same name as of psql,
Its several times faster than version 2.0
To see the full list of changes check the list of Closed Issues on Github.
This is the documentation
osm2pgrouting-2.1.0-alpha
Alpha for osm2pgrouting v2.1.0
osm2pgrouting 2.1.0-alpha NOTES
pgRouting new 2.1 release can handle osm ids with bigint in the following functions:
pgr_dijkstrapgr_ksppgr_drivingDistance
The purpose of these release is to make;
- the
osm_idavailable to pgRouting, and - have a time based cost /reverse_cost columns based on the speed limits of the segments.
New ways table structure
Column | Type | Modifications
-------------------+---------------------------+----------------
gid | bigint |
class_id | integer |
length | double precision |
length_m | double precision | new column
name | text |
source | bigint |
target | bigint |
x1 | double precision |
y1 | double precision |
x2 | double precision |
y2 | double precision |
cost | double precision | name changed from 'to_cost'
reverse_cost | double precision |
cost_s | double precision | new column
reverse_cost_s | double precision | new column
rule | text |
one_way | integer | new column
maxspeed_forward | integer |
maxspeed_backward | integer |
osm_id | bigint |
source_osm | bigint | new column
target_osm | bigint | new column
priority | double precision |
the_geom | geometry(LineString,4326) |
New ways_vertices_pgr table structure
Column | Type | Modifications
----------+----------------------+----------------------------------------------------------------
id | bigint |
osm_id | bigint | new column
cnt | integer |
chk | integer |
ein | integer |
eout | integer |
lon | numeric(11,8) | new column
lat | numeric(11,8) | new column
the_geom | geometry(Point,4326) |
Indexes:
"ways_vertices_pgr_pkey" PRIMARY KEY, btree (id)
"vertex_id" UNIQUE CONSTRAINT, btree (osm_id)
"ways_vertices_pgr_gdx" gist (the_geom)
"ways_vertices_pgr_osm_id_idx" btree (osm_id)
osm2pgrouting v2.0.0
osm2pgrouting version 2.0.0
osm2pgrouting v2.0.0 - RC 1
Release Candidate 1 of osm2pgrouting v2.0.0
osm2pgrouting v2.0.0 - Beta
Beta of osm2pgrouting v2.0.0.
osm2pgrouting v2.0.0 - Alpha
Alpha for osm2pgrouting v2.0.0