<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Can you check if a route through the
streets get the street names? If yes, then something is wrong with
your code.<br>
<br>
BTW: there is a LocationIndexSC which has the edgeFilter enable -
you should enable this shortcut filter too as you only need normal
edges I think. Also keep in mind that for now the lookup of
LocationIndexTree only grabs locations in the 8 zones around the
query zone, which is sufficient for finding the closest edge but
not sure if for you.<br>
<br>
> It is not easy to update to the latest version, since i
changed essential things to achieve my goals.<br>
<br>
For just grabbing the neighborhood streets?<br>
<br>
<br>
> I simply try to get all edges that are in my direct
environment.<br>
<br>
Can you disable CH? Then it should be easier<br>
<br>
Regards,<br>
Peter.<br>
<br>
PS: in a future version (not pushed yet) the LocationIndexTree is
better to (mis)use for other purposes.<br>
<br>
</div>
<blockquote
cite="mid:CAL83n092cD+-wFp6ris5wF+7BD1uWcXCHdT1h3ZbC=3CVWZ=Yg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>1000x Thanks!!! <br>
<br>
</div>
This solved the problem as you said:<br>
<br>
EdgeExplorer ee = graph.createEdgeExplorer(edgeFilter);<br>
ee.setBaseNode(nodeID);<br>
<br>
while(ee.next()){<br>
resultSet.add(graph.getEdgeProps(ee.getEdge(),
ee.getAdjNode()));<br>
}<br>
<br>
<br>
</div>
<div>The only thing is that i still have no street names on all
roads. I would have checked the OSM ways for a streetname, but
in my screenshot you can see, that some edges are purple which
means that it has a name and doesn't has a name at the same
time!<br>
<br>
> what are you trying to solve? I'm not sure I can follow
you as this all is already implemented in GraphHopper ...<br>
</div>
<div>I simply try to get all edges that are in my direct
environment.<br>
<br>
</div>
<div>> Using the latest version would give you GPS exact
results and we make sure no other (already solved) problems
are involved.<br>
</div>
<div>It is not easy to update to the latest version, since i
changed essential things to achieve my goals.<br>
<br>
</div>
<div>Regards,<br>
Andreas<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/12/16 Peter K <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:peathal@yahoo.de"
target="_blank">peathal@yahoo.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> Maybe i understand the problem... Could it be that an
edge explorer<br>
> only iterates over edges of which the base node is
the base node?<br>
> Makes sense somehow.<br>
> Now is the problem: How can i find an edge to which a
given node is<br>
> the adjacent node?<br>
<br>
</div>
Not sure if I understand completely. Maybe the problem you
are having is<br>
that with CH a node is only connected to nodes with a higher
level but<br>
still you should get all edges. And since you don't want
shortcut edges<br>
this cannot be the problem. Hmmh.<br>
<br>
Or maybe the API is unclear? 'base' and 'adjacent' node is
dependent of<br>
how you traverse the graph, not e.g. if this direction is
accessible for<br>
car. E.g. if you have a simple graph '1-2-3' and you do<br>
<br>
iter = explorer.setBaseNode(1)<br>
while(iter.next()) {<br>
edgeIds.add(iter.getEdge());<br>
}<br>
=> you'll only get one edge id with adjacent node '2'<br>
<br>
iter = explorer.setBaseNode(2)<br>
while(iter.next()) {<br>
edgeIds.add(iter.getEdge());<br>
}<br>
=> you'll get two edge ids with adjacent node '1' and '3'
where the<br>
order is not defined<br>
<br>
Regards,<br>
Peter.<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>