Skip to content
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

Here maps - street traffic map type no longer works #676

Open
JacekJagosz opened this issue Jun 16, 2024 · 7 comments
Open

Here maps - street traffic map type no longer works #676

JacekJagosz opened this issue Jun 16, 2024 · 7 comments

Comments

@JacekJagosz
Copy link
Contributor

After Here maps has moved to new developer portal I had to generate a new API key, but it seems all the features of Pure Maps work just as they used to. The only one I found broken is the street traffic map type, nothing is being loaded and I am left with a white screen.
Could anyone else see if they get the same issue?

SFOS 4.6
Pure maps 3.3.0-1.10.1.jolla
Here are the errors I get:

[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/284/173=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/283/174=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/282/171=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/283/172=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/283/173=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/284/171=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/282/173=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/284/174=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/282/174=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 5/17/10=>5 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/282/175=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/283/171=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/284/175=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/284/172=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/282/172=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 9/283/175=>9 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 4/8/5=>4 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/141/86=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/142/86=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/141/87=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/141/85=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/142/87=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 8/142/85=>8 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 3/4/2=>3 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 7/71/43=>7 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 7/70/43=>7 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 7/70/42=>7 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 2/2/1=>2 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 7/71/42=>7 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 6/35/21=>6 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 1/1/0=>1 for source raster: HTTP status code 403"
[W] unknown:0 - [ ERROR ]  "{unknown}[Style]: Failed to load tile 0/0/0=>0 for source raster: HTTP status code 403"
@rinigus
Copy link
Owner

rinigus commented Jun 17, 2024

It works over here. So, maybe there is something with the registration

@Izaic
Copy link

Izaic commented Jul 10, 2024

Same issue here on PostmarketOS edge on a Oneplus 6T using only the native package. The flatpak works fine once the API key is added and I accept the license.

Judging based on that fact, I believe this is a Postmarketos packaging issue. Perhaps it's the firewall blocking API access, or a edge build related bug.

@Izaic
Copy link

Izaic commented Jul 10, 2024

Update: Actually, I was wrong. I'm now getting 400 bad request errors on the flatpak as well. I will close the app and try it again tomorrow to see if it's just a api limit or if the issue still happens.

@Izaic
Copy link

Izaic commented Jul 10, 2024

puremapsflatpakerror.txt

Whats odd is that I didnt enable stadia and I get different errors, perhaps the settings arent being saved properly?

@omartijn
Copy link

omartijn commented Nov 6, 2024

I'm having the exact same issue. Maybe old accounts somehow still work? Could be worth it to create a new account and test with that.

@james1465
Copy link

At the time of writing Pure maps is using version 2 of the HERE tile API

HERE have deprecated version 2 of this API, and while they're not explicit about it - there are suggestions in their docs that version 2 may not be available to new accounts.

They've published a migration guide here:

https://www.here.com/docs/bundle/raster-tile-api-migration-guide/page/README.html

I was able to get HERE maps working on Pure again by changing the URLs in the json file to the new specification. For example in :

/usr/share/harbour-pure-maps/maps/here_4_traffic_day.json

The Tile URL line changes from

"tile_url": "https://3.traffic.maps.ls.hereapi.com/maptile/2.1/traffictile/newest/normal.traffic.day/{z}/{x}/{y}/512/png8?apiKey=#HERE_APIKEY#&ppi=500&pois&lg=#LANG#",

to:

"tile_url": "https://maps.hereapi.com/v3/base/mc/{z}/{x}/{y}/png8?ppi=400&size=512&style=lite.day&apiKey=#HERE_APIKEY#",

(Repeat for the other here_*.json files using the same pattern)

Note that the previous ppi of 500 is no longer available. The language short codes have also changed, so more work is needed here for to make this respect language settings other than default/english as I have omitted the lang parameter for now.

I don't want to submit a pull request for this yet as it might break this service for anyone using a legacy HERE developer account.

@omartijn
Copy link

omartijn commented Jan 4, 2025

Thanks, @james1465 that was just the kickstart I needed.

I turned it into a PR, fixing the language short codes as well: #691

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants