[GraphHopper] Map-matching Android

[Robin Hunter]

Hi Peter,

Really stupid question this time - hopefully the last!

I have on my desktop the a new full repository clone, but it has no tags 
showing version 0.4.1, which is the version on Android.

Android Studio does not want to get the 0.5-SNAPSHOT, as it cannot 
resolve it, so what do I need to do to revert the git clone to your 
version 0.4.1?

Thanks,

Robin


On 2015-06-19 12:53, Peter wrote:
> Hi Robin,
> 
> if you have the identical GraphHopper version on Android AND on your
> desktop creating the graphhopper files, there should be no mismatch.
> 
> Please make sure that you use on all sides e.g. 0.4.1 (no version=1 in
> the string) or 0.5-SNAPSHOT (with version string)
> 
> If this string does not match then it should not be forced with hacks 
> as
> it is likely that file format changes were introduced.
> 
> Regards,
> Peter
> 
> On 19.06.2015 13:50, Robin Hunter wrote:
>> Hi,
>> 
>> Getting close but another small issue.
>> 
>> When I generate the map file it creates a properties file that
>> contains the accept string:
>> car|speedFactor=5.0|speedBits=5|turnCosts=false|version=1, this will
>> not compare as an exact lower case match to the encodingManager which
>> is expecting only car|speedFactor=5.0|speedBits=5|turnCosts=false
>> 
>> This is in the method loadExisting() in GraphHopperStorage.
>> 
>> How can I either add the |version=1 to the encodingManager or drop the
>> |version=1 from the properties file?
>> 
>> Many thanks,
>> 
>> Robin
>> 
>> 
>> 
>> 
>> 
>> On 2015-06-19 08:11, Peter wrote:
>>> Hi Robin,
>>> 
>>> as there was a problem in the Readme, would you just read and try 
>>> again?
>>> See also:
>>> https://github.com/graphhopper/map-matching/issues/25
>>> 
>>>> 2) Secondly, I did include graphHopper.setCHEnable(false);
>>> 
>>> You will definitely need this, but make sure you also disable ch when
>>> you import the pbf on your desktop, e.g. in the config.properties 
>>> with:
>>> 
>>> prepare.chWeighting=no
>>> 
>>>> noting that it seems that the javax XML code will not allow an OSM 
>>>> map
>>> to be loaded directly in Android
>>> 
>>> Yes, it does not work yet. But currently there was no high demand yet 
>>> as
>>> importing it on the device requires lots of memory.
>>> 
>>> Regards,
>>> Peter
>>> 
>>> On 19.06.2015 08:58, Robin Hunter wrote:
>>>> Hi,
>>>> 
>>>> I have a full -gh directory so that graphhopper on Android will load
>>>> the map (noting that it seems that the javax XML code will not allow
>>>> an OSM map to be loaded directly in Android) and I am now trying to
>>>> get the map-matching working.
>>>> 
>>>> This fails in one of two ways -
>>>> 
>>>> 1) Firstly, I did not include graphHopper.setCHEnable(false);
>>>> 
>>>> In this instance the graph is loaded as a LevelGraphStorage type but
>>>> this is not allowed in the LocationIndexTree constructor and I 
>>>> cannot
>>>> find a mechanism to get the baseGraph passed that does not cause a
>>>> error, for example class cast exception.
>>>> 
>>>> 2) Secondly, I did include graphHopper.setCHEnable(false);
>>>> 
>>>> In this instance I get Cannot load the graph when using instance of
>>>> com.graphhopper.storage.GraphHopperStorage due to a hashcode
>>>> verification check in loadNodesHeader().
>>>> 
>>>> 
>>>> 
>>>> So far I have not found a mechanism to get to the point where I can
>>>> create a MapMatching object.
>>>> 
>>>> Any help appreciated.
>>>> 
>>>> Thanks,
>>>> 
>>>> Robin
> 
> 
> _______________________________________________
> GraphHopper mailing list
> GraphHopper at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/graphhopper