invalid memory address or nil pointer difference
AmilaViduranga opened this issue · 4 comments
AmilaViduranga commented
hi team,
I got bellow snap shot issue when I run the instructions. I have added "PBF_FILE=muve.osm.pbf" in ".env" file and added that file to the "data/import" folder
please give help me to solve this
here is my fille link https://drive.google.com/file/d/1X4UlOPCezo4xzdZM8iYX52htOIMieSJS/view?usp=sharing
related issue with OSMNames/OSMNames#190
ImreSamu commented
please give help me to solve this
according to osmium check-refs
- your input osm file (muve.osm.pbf
) is not valid ...
osm@10e96446737b:/osm/data$ osmium sort muve.osm.pbf -o muve_sorted.osm.pbf
[======================================================================] 100%
osm@10e96446737b:/osm/data$ osmium check-refs muve_sorted.osm.pbf
[======================================================================] 100%
Node ID twice in input. Maybe you are using a history or change file?
This command expects the input file to be ordered: First nodes in order of ID,
then ways in order of ID, then relations in order of ID.
ImreSamu commented
it is not a valid osm file ... lot of nodes duplicated ..
osm@10e96446737b:/osm/data$ osmium cat muve.osm.pbf -t node -f opl | grep n844674876 | head
n844674876 v1 dV c0 t2010-08-03T11:31:55Z i0 u Tname=Kiribathgoda%20%Base%20%Hospital,amenity=hospital x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
n844674876 v1 dV c0 t i0 u Tamenity=hospital,name=Kiribathgoda%20%Base%20%Hospital,operator=Asanka,addr:city=Kiribathgoda x79.9292155 y6.9838357
AmilaViduranga commented
@ImreSamu , Is there any way to fix the file issues like you mentioned here ?
ImreSamu commented
Is there any way to fix the file issues like you mentioned here ?
imho:
- this is just the first detected problems ... maybe other problem can be exists;
- so it is easier to fix your workflow ; and try re-create the input files - on the good way ...
- You have to ask help - on the general osm developer forum .. describing your workflow; problem; input files ; expected results ...