[go: up one dir, main page]
Menu ▾ ▴

#41 How to load background tiles? Unspecific error.

v1.5
open
nobody
None
5
2020-09-21
2019-02-17
Joachim Schneider
No

Hello,
I'm just trying Vikin 1.7 on Windows 10. When I try to load a background map I alsway get an error message in the status bar "Error downloading a tile" (translated back to English). Not anything specific. How can I find out what the actual problem is? I have tried different map providers, so it seems not to be this. I think I was asked at first start if I want to activate internet fuctionality, I have answered yes.
regards
Joachim

Discussion

  • Rob Norris

    Rob Norris - 2019-02-21

    The best way to self diagnose issues is to run Viking with extra information output, controlled by command line parameters.
    So to do this on Windows (it's a bit more involved than the Linux command line) start the command prompt.
    Then change to the folder Viking is installed in, typically:

    cd "C:\Program Files\Viking"

    Run viking with the parameters '-Vd', and redirect the output to a file (for some reason on Windows the text output is not shown in the terminal). e.g.:

    viking.exe -Vd 2>1 > %TMP/viking.log

    Close Viking.
    Then open the file, e.g.:

    notepad %TMP/viking.log

    Hopefully this can provide more clues as to what is happening.
    Attach the output (or just copy the seemingly relevant bits) here for further assistance.

     

  • Marc Compere

    Marc Compere - 2020-09-20

    running viking -V generates more output, listed below, but the same question remains.

    what's the problem and how to fix??? Viking looks like it could be outstanding, but the basics are not functioning now with v1.8 and compiled from source on Ubuntu 18.04.5.

    ** (viking:29919): WARNING **: 11:46:02.898: Unknown map type
    * Trying 13.226.51.132...
    * TCP_NODELAY set
    * Connected to api.tiles.mapbox.com (13.226.51.132) port 443 (#0)
    * ALPN, offering http/1.1
    * successfully set certificate verify locations:
    * CAfile: /etc/ssl/certs/ca-certificates.crt
    CApath: /etc/ssl/certs
    * SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
    * ALPN, server did not agree to a protocol
    * Server certificate:
    * subject: CN=api.mapbox.com
    * start date: Mar 5 00:00:00 2020 GMT
    * expire date: Apr 5 12:00:00 2021 GMT
    * subjectAltName: host "api.tiles.mapbox.com" matched cert's "api.tiles.mapbox.com"
    * issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
    * SSL certificate verify ok.

    GET /styles/v1/mapbox/outdoors-v9/tiles/256/15/8972/13675?access_token=pk.eyJ1Ijoicndub3JyaXMiLCJhIjoiY2lxc294anN2MDA5bWhzbWFseWsxMW1ydiJ9.HcybKtZsiG6RVuOHg481Kg HTTP/1.1
    Host: api.tiles.mapbox.com
    User-Agent: viking/1.8 libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
    Accept: /

    < HTTP/1.1 401 Unauthorized
    < Content-Type: application/json; charset=utf-8
    < Content-Length: 44
    < Connection: keep-alive
    < Date: Sun, 20 Sep 2020 15:46:03 GMT
    < X-Powered-By: Express
    < Access-Control-Allow-Origin: *
    < Access-Control-Allow-Methods: GET
    < Cache-Control: max-age=60,s-maxage=300
    < X-Content-Type-Options: nosniff
    < ETag: W/"2c-mbs4WeZIt3tmYvk6HtTC1rbvKjQ"
    < X-Cache: Error from cloudfront
    < Via: 1.1 dcaec0b05596b42ef5dab9e145ac961e.cloudfront.net (CloudFront)
    < X-Amz-Cf-Pop: MIA3-C3
    < X-Amz-Cf-Id: MAKTCpUa3lY_t8hPeAsDc69NiEjkhIftti6dH3cVyt9KupuUj3_qKQ==
    <
    * Connection #0 to host api.tiles.mapbox.com left intact

    ** (viking:29919): WARNING **: 11:46:03.259: curl_download_uri: http response: 401 for uri https://api.tiles.mapbox.com/styles/v1/mapbox/outdoors-v9/tiles/256/15/8972/13675?access_token=pk.eyJ1Ijoicndub3JyaXMiLCJhIjoiY2lxc294anN2MDA5bWhzbWFseWsxMW1ydiJ9.HcybKtZsiG6RVuOHg481Kg

    ** (viking:29919): WARNING **: 11:46:03.259: Download error: /home/comperem/.viking-maps/Mapbox-Outdoors/15/8972/13675.png
    * Found bundle for host api.tiles.mapbox.com: 0x7f126400a8e0 [can pipeline]
    * Re-using existing connection! (#0) with host api.tiles.mapbox.com
    * Connected to api.tiles.mapbox.com (13.226.51.132) port 443 (#0)

    GET /styles/v1/mapbox/outdoors-v9/tiles/256/15/8972/13676?access_token=pk.eyJ1Ijoicndub3JyaXMiLCJhIjoiY2lxc294anN2MDA5bWhzbWFseWsxMW1ydiJ9.HcybKtZsiG6RVuOHg481Kg HTTP/1.1
    Host: api.tiles.mapbox.com
    User-Agent: viking/1.8 libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
    Accept: /

    < HTTP/1.1 401 Unauthorized
    < Content-Type: application/json; charset=utf-8
    < Content-Length: 44
    < Connection: keep-alive
    < Date: Sun, 20 Sep 2020 15:46:03 GMT
    < X-Powered-By: Express
    < Access-Control-Allow-Origin: *
    < Access-Control-Allow-Methods: GET
    < Cache-Control: max-age=60,s-maxage=300
    < X-Content-Type-Options: nosniff
    < ETag: W/"2c-mbs4WeZIt3tmYvk6HtTC1rbvKjQ"
    < X-Cache: Error from cloudfront
    < Via: 1.1 dcaec0b05596b42ef5dab9e145ac961e.cloudfront.net (CloudFront)
    < X-Amz-Cf-Pop: MIA3-C3
    < X-Amz-Cf-Id: Y1R-HjGPmryz_sTxyc1Vu3MzIVnNCfNC0Axd3cIrxB0t7JZ8kQxL4w==
    <
    * Connection #0 to host api.tiles.mapbox.com left intact

    ** (viking:29919): WARNING **: 11:46:03.441: curl_download_uri: http response: 401 for uri https://api.tiles.mapbox.com/styles/v1/mapbox/outdoors-v9/tiles/256/15/8972/13676?access_token=pk.eyJ1Ijoicndub3JyaXMiLCJhIjoiY2lxc294anN2MDA5bWhzbWFseWsxMW1ydiJ9.HcybKtZsiG6RVuOHg481Kg

     

    • Rob Norris

      Rob Norris - 2020-09-21

      The free tier Mapbox tile service (which was Viking's default) has been discontinued.

      The latest source code should be using OpenTopoMap as the default map.

      You can select a different Map provider each time and/or set a different default map provider:

      Edit --> Layer Defaults --> Map... --> <<choose Map Type>> --> OK

      You can add further Map Providers, although you have to manually create/edit a configuration file as mentioned in the Viking manual and some examples are here:
      https://sourceforge.net/p/viking/wikiallura/Maps/

       

      Last edit: Rob Norris 2020-09-21

  • Marc Compere

    Marc Compere - 2020-09-21

    Hello Rob,

    SOLVED.

    Outstanding!

    OpenTopoMaps was not an option in the menu settings you described, but I chose Bing, closed, then re-opened and - viola. Imagery.

    I'm pretty stoked about this working. I've been using Google Earth Pro Desktop and, it's good for sure, but it cannot split a waypoint track into two different tracks at a certain waypoint. Google Earth has some editing features but Viking is much better, in what I've seen in the menus anyhow.

    I'll be exploring and trying it out quite a bit in the future.

    Thanks for your prompt and useful response.

    Marc

     

  • Marc Compere

    Marc Compere - 2020-09-21

    By the way, I compiled Viking v1.8 on Ubuntu 18.04.5 using these steps listed below.

    I migrated to Ubuntu 20.04.1 and all the packages had been suggessfully re-installed after the upgrade and the only minor re-installation was sudo apt-get install libmapnik-dev.

    The full set of packages to compile Viking v1.8 from source on Ubuntu 18.04 or 20.04 was:
    download source from: https://sourceforge.net/projects/viking/

    tar xvf viking-1.8.tar.bz2

sudo apt-get install intltool
sudo apt-get install libcurl3-dev
sudo apt-get install libgdk-pixbuf2.0-dev
sudo apt-get install libgtk2.0-dev
sudo apt-get install gnome-doc-utils
sudo apt-get install libgeoclue-2-0
sudo apt-get install libgeoclue-2-dev
sudo apt-get install libgexiv2-dev
sudo apt-get install liboauth-dev
sudo apt-get install libgps-dev
sudo apt-get install libbz2-dev
sudo apt-get install libmagic-dev
sudo apt-get install libsqlite3-dev
sudo apt-get install nettle-dev
sudo apt-get install libmapnik-dev

    then:

    ./configure
make ; make install

    then make the map change from default Mapbox tile service to Bing or possibly the others as you said:

    Edit --> Layer Defaults --> Map... --> <<choose Map Type>> --> OK

    Marc

     

Log in to post a comment.