Custom query (1088 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (106 - 108 of 1088)

Ticket Owner Reporter Resolution Summary
#1157 dkastl kalxas fixed pgrouting fails to install after postgis update
Description

From logs (build10344):

===============================================================
install_pgrouting.sh
===============================================================
gpg: keyring `/tmp/tmpHDcaw_/secring.gpg' created
gpg: keyring `/tmp/tmpHDcaw_/pubring.gpg' created
gpg: requesting key B65ADE33 from hkp server keyserver.ubuntu.com
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)
OK
E: Unable to correct problems, you have held broken packages.
ERROR: pgRouting Package install failed! Aborting.
#1233 live-demo@… hamish fixed TinyOWS quickstart failure
Description

Hi,

no luck with the 7.0rc2 quickstart for TinyOWS, there are a couple of problems:

  • 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.
  • the quickstart asks you to enable the WFS plugin in QGIS but it doesn't exist. if you go to the Fetch plugins there is a WFS 2.0 Client v.0.8.4 by J. Weichland, but you get the same NameSpace error as below.
  • no matter, Add WFS Layer is available from the menu anyway, add name and url as per quickstart, then ok, then Connect. but it leads to this error:
      ErrorConfigFile: No layer NameSpace prefix defined
    

and that's as far as you get.

/usr/lib/cgi-bin/tinyows does exist in the filesystem.

Hamish

#1234 dkastl hamish fixed pgRouting: PostGIS database ways table bad import os OSM data
Description

Hi,

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.