by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 07 15:45
    rajhim2 labeled #1601
  • Aug 07 15:43
    rajhim2 labeled #1601
  • Aug 07 15:43
    rajhim2 labeled #1601
  • Aug 07 15:43
    rajhim2 labeled #1601
  • Aug 07 15:43
    rajhim2 assigned #1601
  • Aug 07 15:43
    rajhim2 opened #1601
  • Aug 07 04:48
    cvvergara labeled #1600
  • Aug 07 04:48
    cvvergara labeled #1600
  • Aug 07 04:48
    cvvergara labeled #1600
  • Aug 07 04:48
    cvvergara edited #1600
  • Aug 07 04:48
    cvvergara edited #1600
  • Aug 07 04:47
    cvvergara milestoned #1600
  • Aug 07 04:47
    cvvergara opened #1600
  • Aug 07 04:13
    krashish8 edited #1599
  • Aug 06 15:05
    cvvergara edited #1599
  • Aug 06 15:03
    krashish8 review_requested #1599
  • Aug 06 15:03
    krashish8 review_requested #1599
  • Aug 06 15:03
    krashish8 review_requested #1599
  • Aug 06 15:03
    krashish8 review_requested #1599
  • Aug 06 15:03
    krashish8 labeled #1599
Vicky Vergara
@cvvergara
The id of the edge 1 -> 2 is 1
The id of the edge 2 -> 1 is 1
and in both graphs:
The cost of the edge 1 -> 2 is 5
The cost of the edge 2 -> 1 is 6
Ashish Kumar
@krashish8
I see, there might be a problem with this when we are sorting directly based on the id.
Vicky Vergara
@cvvergara
right!
I remember once i did this query:
SELECT * FROM pgr_dijkstra(
    'SELECT 1 as id, source, target, cost, reverse_cost FROM edge_table',
    2, 3
);
and the results came quite fine, except the id of the edge
SELECT * FROM pgr_dijkstra(
    'SELECT 1 as id, source, target, cost, reverse_cost FROM edge_table',                                                                                                                                                        
    2, 3                                                                                                                                                                                                                         
);                                                                                                                                                                                                                               
 seq | path_seq | node | edge | cost | agg_cost                                                                                                                                                                                  
-----+----------+------+------+------+----------                                                                                                                                                                                 
   1 |        1 |    2 |    1 |    1 |        0                                                                                                                                                                                  
   2 |        2 |    5 |    1 |    1 |        1                                                                                                                                                                                  
   3 |        3 |    6 |    1 |    1 |        2
   4 |        4 |    9 |    1 |    1 |        3
   5 |        5 |    4 |    1 |    1 |        4
   6 |        6 |    3 |   -1 |    0 |        5
(6 rows)
Ashish Kumar
@krashish8
There's a -1
At the end
Oh. Thats fine
Vicky Vergara
@cvvergara
a path has N edges and N+1 nodes
using the first example of the documentation
Ashish Kumar
@krashish8
Yeah, that's correct
Vicky Vergara
@cvvergara
you can see that everything is ok, except the edge id
Ashish Kumar
@krashish8
Yes
Vicky Vergara
@cvvergara
for us, the id is just a label
we do recreate the graph, and all the edges it defines with the columns source target
source->target edge exists when cost>0 and its labled with the id given
target->source edge exists when reverse_cost>0 and its labled with the id given, but internally it has a different index
that is why .id(), and .idx()
id is the label from the user, and idx is the boost graphs index of the edge (or something of the sort)
So, we give the correct result even if the edge id does not make sense on a database

end of topic

Vicky Vergara
@cvvergara
@MarPetra There are new translations to be done on transifex
MarPetra
@MarPetra
Hi @cvvergara.
Ok
Vicky Vergara
@cvvergara
@MarPetra the translations are for pgRouting
Vicky Vergara
@cvvergara

topic: Conversation about labels

I am reviewing the issues on pgRouting main ropo, and I am thinking of a best way of labeling.
labeling by directory
labeling by directory/function
Example:
dijskstra
dijkstra/dijkstra
dijkstra/dijkstraCost
dijkstra/dijkstraVia
Create the label as needed, for example dijkstra/dijkstraCostnot needed yet as no issue about the function is there
The left part indicates the developer: internally where the code is located, the right part indicates precisely which function it affects
We also have issues defined as bugs that we can not reproduce as there is no data, query or anything to work with. Just a vague explanation.
Vicky Vergara
@cvvergara
So what about
bug/reproducible
bug/explanation
Vicky Vergara
@cvvergara
I created a Label Question because sometimes the user has a problem that marks as bug but its a matter of the way the query is done. Basically the kind of questions that need to go to places like: https://gis.stackexchange.com/
Vicky Vergara
@cvvergara
@MarPetra hey there are only two files left to finish up the translation changes, tell me when you are done.
Vicky Vergara
@cvvergara
@MarPetra I know I need to learn to count :-)
MarPetra
@MarPetra
Hahaha what happened?
Hi @cvvergara. I thought I was finished all translations
Vicky Vergara
@cvvergara
on the 27th there were more than 3, but I just noticed you 100% translated spanish, so I will do the release this week
Vicky Vergara
@cvvergara
@MarPetra Need to teach you how to move all the translations merged to master into develop
See you on the afternoon
MarPetra
@MarPetra
Hi @cvvergara, are you around?
Vicky Vergara
@cvvergara
Hey @MarPetra yes I am here
So, as you made the translations in master we need to move them forward to develop branch
I could have done it but, you made the translatios, so you will do it, for historical purposes
Lets jitsi
MarPetra
@MarPetra
ok
see you there
MarPetra
@MarPetra
@cvvergara @krashish8 @rajhim2 @prakashupes develop branch has been updated with latest documentation and translations
Vicky Vergara
@cvvergara
Thanks @MarPetra