![]() This plan is not obligatoire but needed for the Inreach option. Over 500 euros plus the cost of the Inreach ‘plan’. My last three treks, I have seen places with no network. Of course if I had hurt myself, fallen down, broken a bone etc, well then that would have been a real problem. Yes yes this does exist and so I couldn’t get hold of my wife just to say, all okay, no problems, tent up, etc. Last year while out trekking I got caught out in an area with no telephone network what so ever. I’ll try very briefly to explain but there are lots about in on the web and better written than me. In three treks I found myself in a area with no telephone GSM at all. Believe me, no telephone coverage is still quite often. This works even when there is no telephone network available as it uses satellite coverage. ![]() It sends a ‘I need help message’ when you push a certain button. Inreach means that the device is capable of calling for help (‘calling’ not vocal like a telephone. Basically the same as the 64s, with most of my gripes with the 64s corrected. This year 2020 I bought the Garmin Inreach 66i model. even if it did get better with updates after a rather long wait. Why ? A while back in 2017 I wrote about the Garmin 64s that I had but wasn’t really happy about some of the workings on it. If you continue, conflicting files will be replaced losing the previous content.įor now I said no and I am running QMapShack using a local compiled version with a recent git checkout.The battery is still 3/4 full after being on for more than 9 hours Bye bye the 64S. Proj-6.0.0-37.1.x86_64 conflicts happen when two packages attempt to install files with the same name but different contents. After the operation, additional 9.3 MiB will be used.Ĭontinue? (y): y The following NEW package is going to be installed: Installed proj5 despite file conflicts and got a working QMapShack. Other question: Would it be appropriate to open a bug on ? That looks good only libproj.so.13, so not sure where that libproj.so.15 in the ldd output comes from > objdump -p /usr/bin/qmapshack | grep NEEDED Note, however, that this alternative shows only the direct dependencies of the executable, while ldd shows the entire dependency tree of the executable I read “PROJ 6 has undergone extensive changes” and that is not yet supported by QMapShack:Ĭhecking the YaST Software Management I see proj has no non-6.0.0 versions, but I have libproj13 installed than gives 5.2.0-31.6Ī safer alternative when dealing with untrusted executables is: $ objdump -p /path/to/program | grep NEEDED ![]() So had a look at the and saw that version 6.0.0 has been released and “projinfo” reveals I am running that. "īut that gives me "parameter error: no arguments in initialization list’ My $proj = Geo::Proj4->new(init => "epsg:32661") or die "parameter error: ".Geo::Proj4->error. Please contact the package maintainer of your distribution to fix it.") The translation tables for EPSG projections usually stored in /usr/share/proj are missing. ![]() ,tr("QMapShack detected a badly installed Proj4 library. ProjPJ pjsrc = pj_init_plus("+init=epsg:32661") That runs fine, so it looks like the proj4 library is installed, only QMapShack is missing something that was available before the update. Or die "parameter error: ".Geo::Proj4->error. My $proj = Geo::Proj4->new(proj => "merc", Installed that and executed a small test program: #!/usr/bin/perl Tried to search for the proj4 package (sudo zypper se proj4) but could not find it, only a perl-Geo-Proj4 package. I did update my Tumbleweed system this morning and after a reboot I tried to start QMapShack, but it refuses to start saying “QMapShack detected a badly installed Proj4 library”: ![]()
0 Comments
Leave a Reply. |