Messages

@tommi:

I think so. How should penalty calculation work?

First I was thinking in this way:
A) If I set x = 100 m and y=10 m the route from point A to point B should be calculated so there is no local route section which has more than 10 m to ride uphill for a distance of 100 m, the total distance might be 30 km.
B) If I set x = 200 m and y=10 m the route from point A to point B should be calculated so there is no local route section which has more than 10 m to ride uphill for a distance of 200 m, the total distance might be 35 km.

I think this calculation can be implemented in Locus by using local parameters:

Let's consider a track, automatically splitted into 100 sections A=A0 to B=A100: If section A3 to A4 (x meter) has a total number of uphill meters y the sub-route-section from A3 to A4 should be recalculated with parameter z which describes the additional % of longer distance for this section. The parameters x, y and z should be set in the app by the user. As a result the app could propose the total number of altitude meters the rider has to go uphill plus the total distance from A to B.

---

I would really appreciate if this total altitude uphill meters optimization can be done directly in Locus. I was searching in the internet for a similar tool which does not quite do what I want (with parameters x,y,z and numbers of the total distance and uphill meters as output) but there are some suggestions here:

http://bicycles.stackexchange.com/questions/30583/app-to-find-the-shortest-route-with-the-least-amount-of-climbs/30827#30827

http://bicycles.stackexchange.com/questions/18951/topography-aware-route-planning

Sorry, this was a rhetorical question to explain that brouter at least internally uses altitude data to calculate the penalty for up and down.

What do you mean with "with Brouter you don't have the altitude data"?
The track in Locus allows to download the altitude data and then you can view it in the diagram.

Are the altitude data merged with pure OSM data inside of the rd5 files? So that BRouter can calculate the used altitude?

I think so. How should penalty calculation work? What I don't know is if brouter adds the altitude info to the track points. But for me this is not so important as Locus can do it

What do you mean with "with Brouter you don't have the altitude data"?
The track in Locus allows to download the altitude data and then you can view it in the diagram.

@Menion: my point is that I just want to have all bulk data for Locus on ext SD. This includes vector maps, Pois, srtm data and last but not least routing data.

You wrote, user should put the *.gh next to vector maps. This is just what I did.
The logic in Locus is there to find vector maps in extra folder. It just does not seem to work for  *.gh.

Hi Menion,
referring to your english post in the german part of the forum, precisely this one:
http://forum.locusmap.eu/index.php?topic=4661.msg37837#msg37837
I have problems with graphhopper data folder on external sd card.
I've placed all my vector maps at
/storage/extSdCard/LocusMassData/mapsVector
according http://www.locusmap.eu/locus-run-since-update-device-android-4-4-2-kitkat/#solutionC .

The vector maps are in sub folders for the continents. Locus is happy to use the vector maps from there.

In the same folder /storage/extSdCard/LocusMassData/mapsVector I have put the folder _germany.osm-gh
So it looks like:
/storage/extSdCard/LocusMassData/mapsVector/Europe/*.map
/storage/extSdCard/LocusMassData/mapsVector/_germany.osm-gh

The Graphhopper Addon doesn't find its data folder and complains I should place the data at /storage/emulated/0/Locus/mapsVector.
If I put the _germany.osm-gh to the recommended location in the Locus folder, GraphHopper Addon finds its data folder and I can use the router..
But due to free space limits I want to put all those bulk data to external storage.

As Balloni did, I deleted  the app data of GraphHopper addon. Next time I started the addon again it showed me the hint to put the data to internal storage as before.

Any idea?
Thanks,
Tommi

OK, I know what you mean. But I enjoy a bit if fun and brainwork on the road. I am not a robot ... :-)

Ok, Michael. My comment was about the capabilities of brouter and not about your personal preference ;-)

Navigation calculation does not require internet if you use BRouter. My reply refers to your yellow be-aware.

Brouter only does route calculation, no navigation!
Navigation instructions are calculated by Locus but just based on the calculated route (or on any other gpx track) without knowledge of any road information.

Though I'm a fan of a dark theme, I think topcaser's need can be  excellently fulfilled by selection of the black map (Maps/online/blank/dark).

Ohne Navigationsanweisungen wie maxxuwe sagt.

Mit Navigationsanweisungen (Achtung! das sind berechnete Hinweise zu Richtungsänderungen ohne Wissen über Straßen/Wege etc., keine echten Abbiegehinweise!) musst du "Kopie erstellen" wählen und dort "Trackrichtung umkehren" anklicken.
Und danach mit der Kopie wie gehabt arbeiten.

Langer Tap auf die obere Leiste und von dort Leiste ändern. Die rechte Leiste wird quasi wie eine Verlängerung der oberen Leiste behandelt.
Vielleicht sind dir die Einstellungen verlorengegangen.

Hallo,
in der oberen Menüleiste lange drücken und dann Leiste ändern auswählen. Die rechte Leiste ist die verlängerte obere Leiste.

Es geht - na ja - so ein bisschen zumindest:
1) Setze POIs 1, 2, ..., n auf die Karte
2) Starte "Route hinzufügen und Messen"
3) Tippe POI 1 an
4) Tippe auf das "+" im Popup für POI1
5) Weiter bei 3) für den nächsten POI ... bis zum letzten POI
6) POIs verschieben bis die Route passt
7) Route abspeichern

Wenn man dafür Quick POIs benutzt geht das eigentlich recht geschwind

edit: bei 6) verschiebt man nicht die POIs sondern die grünen Punkte, die Bestandteil der Route sind

Hey, GraphHopper 0.4 is out!
https://karussell.wordpress.com/2015/03/09/releasing-graphhopper-0-4-and-the-graphhopper-directions-api/

Wouldn't it be a good opportunity to update Locus integration of GraphHopper?
The outdoor season is coming soon and the questions for offline routing and navigation in Locus don't stop.

Yes and two more missing features ... one way roads and roundabouts. Anyway to be true I do not know if any of these issue is solved ...

Give us a new version and new data and we'll find out

I'm not really surprised.
What we've got up to now is the very first version of the Locus GraphHopper app, so to say an alpha or pre-alpha version.
Making a solution mature needs users testing it and giving feedback followed up by the developers fixing and improving it - none of these two conditions were met till now