Custom query (1088 matches)


Show under each result:

Results (46 - 48 of 1088)

Ticket Resolution Summary Owner Reporter
#1139 fixed Upgrade pgRouting to version 2.0.0 dkastl dkastl

With OSGeo Live 7.0 pgRouting should be upgraded to version 2.0.0, but the packages on Launchpad have not been build yet. Once this is done, update the install script as well.

#1157 fixed pgrouting fails to install after postgis update dkastl kalxas

From logs (build10344):

gpg: keyring `/tmp/tmpHDcaw_/secring.gpg' created
gpg: keyring `/tmp/tmpHDcaw_/pubring.gpg' created
gpg: requesting key B65ADE33 from hkp server
gpg: /tmp/tmpHDcaw_/trustdb.gpg: trustdb created
gpg: key B65ADE33: public key "Launchpad PPA for Georepublic" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
E: Unable to correct problems, you have held broken packages.
ERROR: pgRouting Package install failed! Aborting.
#1234 fixed pgRouting: PostGIS database ways table bad import os OSM data dkastl hamish


moving this into its own ticket from #1233.

  • connect to pgrouting PostGIS database in QGIS works, but the ways table doesn't look very healthy, all links back to one spot. or maybe that is the shortest path from a->b? as-is doesn't look healthy anyway. see screenshot.

I can confirm that the "all links back to one spot" problem in the pgrouting PostGIS db was not present in the 6.5 version of the live disc, so this is a new pgRouting problem too. (& perhaps a separate issue to the TinyOWS failure)

I'm guessing that it can only mess up the routing results.

thanks, Hamish

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.