[GraphHopper] Generating routing files

[Jiří Mlavec]

On 18. 7. 2014 10:58, Peter wrote:
> Hey Menion,
>
> *> Issue 1* osmreader.acceptWay=car,bike
>
> You'll have to set chShortcuts=no like you did but be sure you removed 
> the gh folder before you import again otherwise graphhopper will load 
> and fail (but should report with meaningful error?).
I do this always (remove previous directory). I have tried it again just 
to be sure and same result.
>
> But keep in mind that with chShortcuts=no you cannot really use GH on 
> mobile devices (too much RAM required), or vote for magic issue #1 ;)
> https://github.com/graphhopper/graphhopper/issues/1
>
Thanks, I'll watch this issue.
>
> > *Issue 2 *osmreader.acceptWay=car,bike,foot,mtb
>
> You can set osmreader.bytesForFlags=8
> note: this isn't tested that much :)
>
I'll check it once it will be possible to go over issue 1, thanks.
>
> > Otherwise I ride during a week almost 300 km with car only using 
> GraphHopper and it works really well.
> > What I really miss are roundabouts, exits from highways and too much 
> "go straight" orders on places where it's really not needed.
>
> Yes, turn instructions are suboptimal. See these issues for some 
> discussion about it:
> https://github.com/graphhopper/graphhopper/issues/94
> https://github.com/graphhopper/graphhopper/issues/185
>
> Where #94 contains a workaround from a user, but this won't work 
> properly if CH is active.
>
I already watch there threads ;)
>
> > Anyway routing is fast and quite precise. Nice work.
>
> Thanks! Still keep in mind that car routing is without turn 
> restrictions (is top priority currently)
>
> Kind Regards,
> Peter.
>
>

Ok, so to sumarize it (mainly for me if I understand all correctly)

1. it's not possible to create one routing pack for car, bike, foot for 
Android devices because of memory limits (I agree, they are tight - but 
it's a lot better on 4.x devices)
2. it's not possible to route over more then one pack. So if I provide 
for users separate routing packs for every country, it's possible to use 
only one file at time
3. improved instructions are planned (mainly roundabouts), but not yet 
implemented
4. turn restrictions are not yet implemented

Hmm mainly because of first two issues, I see serious problems with some 
public distribution for now. I'll have to watch your progress then and 
provide working solution just for private group of users on Locus forum. 
They are really good in testing and may provide you valuable feedback :)


> On 18.07.2014 10:43, Jiří Mlavec wrote:
>> *Hello Peter,*
>>
>> I'm trying to search some information about generating routing files, 
>> but no success, so it will be nice, if you may point me on correct 
>> way. I'm trying to generate routing files for Android (on Android 
>> using latest graphhopper-0.4-SNAPSHOT-android) and ...
>>
>> Sample map - czech-republic-latest.osm.pbf,  390 MB
>>
>> _Generating_
>> osmreader.acceptWay=car
>>   result: 93 MB, works fine
>>
>> osmreader.acceptWay=foot
>>   result: 140 MB, works fine
>>
>> osmreader.acceptWay=bike
>>   result: 150 MB, works fine
>>
>> *Issue 1*
>> osmreader.acceptWay=car,bike
>> generator ends on:
>> /Exception in thread "main" java.lang.IllegalStateException: Multiple 
>> encoders are active. cannot return one:bike,car//
>> //    at 
>> com.graphhopper.routing.util.EncodingManager.getSingle(EncodingManager.java:329)/
>>
>> after set 'prepare.chShortcuts=no'
>>   result: 93 MB (exactly same as car only), don't work!
>>
>> requests on car or bike route ends with
>> /java.lang.IllegalStateException: Cannot load the graph when using 
>> instance of com.graphhopper.storage.LevelGraphStorage and location: 
>> /storage/emulated/0/Locus/mapsVector/czech-republic-latest.osm-gh//
>>
>> *Issue 2*
>> osmreader.acceptWay=car,bike,foot,mtb
>> ends immediately on
>> /Exception in thread "main" java.lang.IllegalArgumentException: 
>> Encoders are requesting more than 32 bits of way flags. Decrease the 
>> number of vehicles or increase the flags to take long.//
>> //    at 
>> com.graphhopper.routing.util.EncodingManager.registerEncoder(EncodingManager.java:200)/
>>
>> Is there anything I can do, to fix it. Mainly first issue.
>>
>> If answer already exists, please point me on correct place.
>>
>> *Below line*
>>
>> Otherwise I ride during a week almost 300 km with car only using 
>> GraphHopper and it works really well. What I really miss are 
>> roundabouts, exits from highways and too much "go straight" orders on 
>> places where it's really not needed. Anyway routing is fast and quite 
>> precise. Nice work.
>>
>> with regards,
>>     Menion
>>
>>
>> _______________________________________________
>> GraphHopper mailing list
>> GraphHopper at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/graphhopper
>
>
>
> _______________________________________________
> GraphHopper mailing list
> GraphHopper at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/graphhopper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20140718/bb252db7/attachment.html>