-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find any metrics for MLD in the data. #5227
Comments
@linuzer First thing I'd do would be to look at the size of your How exactly did you merge the .osm.pbf files together? |
@danpat Thanks for the quick response! The file sizes seem OK, the merged ones are significantly bigger than the single ones. Here is the exact merge commands (tried both, but no difference):
|
@linuzer Hmm, not sure then. Could be something to do with your custom profile, does it work if you use the default |
Didn't try that yet, but cerainly I will try! Is there something I could do to track further down the error? For example, can I find out what exactly is osrm-routed missing in the file(s)? |
You can examine the contents of the files using Maybe try comparing the internal file list (the output of |
Sorry, I'm a bit confused... What file contents do you mean? From the PBF (that doesn't seem to be a tar)? If I call it like you mentioned: Some additional peaces of information: ThenI tried the preparation with the default car.lua, which did not make any difference. Finally I tried the spain-latest.osm.pbf (so far I only tried portugal-latest.pbf) and to my suppries here the same error happens. That means, the error has nothing to do with the merge or extract, it seems to be something in the spain-latest.pbf from geofabrik.de that causes the error! |
The main difference is that Can you paste the full output of |
Thanks for your ongoing help! I apreciate it a lot! First, here are the contents of the two osrm.* files. I'll put the output of the osrm-* commands in a seperate post. Here portugal-latest.osrm.*:
And here the contents of spain-latest.osrm.*:
|
Here is the output of the three commands. I'm running all of this in Windows, which I hope does not make a difference, but explains the wired characters at the end of each line...
|
@linuzer It looks like the Compare the output of Unfortunately I don't have much ability to debug a problem like this on Windows - maybe check your free memory? You should also check the return code from |
You were right, the osrm-partition and osrm-customize seems to escape premature. The whole process worked already very stable on Windows using much bigger extracts, like germany-latest. I also verified again the memory consumption, but this does not seem to be a problem. I have 32 GB on that machine and the usage comes never over 9 GB with the spain file. Unfortunately I'm fixed to Windows, since I need to use the .net binding of OSRM. Does the return-code tell you anything? |
Unfortunately no. I'll give |
@danpat: Were you able to reproduce the error with spain-latest on your Mac-Machine? I also tried several things, which confuses me a bit: Tried the same spain-latest with the (same) 5.18.0 release on an Ubuntu-VM ... and it worked! Then I recompiled on Windows the whole osrm.net library (which in turn downloads precompiled OSRM-libraries and DLLs in version 5.18.0): No success, same error. Then I compiled OSRM on Windows by myself (that worked), but same error. Then I tried the CH-algorithm toolchain (osrm-extract and osrm-contract): And this worked! Unfortunately I could have had that CH-idea already a lot earlier, but I didn't -- so now I can not tell, if it is a problem with the MLD-code, especially inside osrm-partition, or something related with the precompiled Windows-binaries I used so far. So for me I have right now a workaround using the CH-algorithm, but all this is still quite confusing to me... |
I always get the above error on calling:
osrm-routed.exe .\data\portugal-spain.osrm -a MLD
I prepared "portugal-spain.osrm" from "portugal-spain.osm.pbf", which I merged myselfe form "portugal-latest.osm.pbf" with "spain-latest.osm.pbf" using both, "osmium" and "osmosis".
If I use the prepared "portugal-latest.osrm" from the original file "portugal-latest.osm.pbf", everything works. So I guess it has to do with the merge-process. But this and the preperation of the data didn't show any errors - as fas as I can tell.
So I'm running out of ideas what exactly could cause this error.
Anyone has an idea? Or could it be a bug in some way?
Here are the commands I executed:
.\bin\osrm-extract .\data\portugal-spain.osm.pbf -p .\bin\CustomProfile.lua
.\bin\osrm-partition .\data\portugal-spain.osrm
.\bin\osrm-customize .\data\portugal-spain.osrm
.\bin\osrm-routed .\data\portugal-spain.osrm -a MLD
Thanks a lot for any hint!
The text was updated successfully, but these errors were encountered: