GraphService.ts/GraphDataProvider.ts exceptions when caching data

Imagery, data, and integrations
1

I have been using the Mapillary-js 4.1.2 runtime in a web page to display a map and navigate through street level imagery for some time. I use the jsdelivr version.

I mostly use default viewer constructor options, with caching enabled but with the sequence UI disabled (default is enabled, not sure if this matters). The cover is disabled too.
Not sure if this is important but the problem can happen, eg., with SF downtown imagery.

In all cases when landing, caching is performed and the spatialedges event is eventually fired with status.cached = true. This seems logicial.

However, I currently observe two issues, which I am developing below.

  1. Very often, I get the following errors (many entries) in the Javascript console:

Origin: GraphService.ts:340
Test: Failed to cache tile data (SOME_ID). MapillaryError: Failed to fetch data
at GraphDataProvider.ts:282:22

The spatialedges event nevertheless does fire, with status.cached=true, and navigation arrows show up.

  1. Sometimes, navigation arrows do not show up at all, when they should. In rare instances, only one faint (low opacity) arrow shows up. Recreating the viewer from scratch using the same imageId does show all arrows, however just calling viewer.moveTo() using the same id does not cure the problem, which is very problematic.

In the Network pane of Edge, I see no errors at all, just 200 status codes. Everything seems ok. Some ā€˜images?ā€¦ā€™ graph queries return 0-byte content, but still with a 200 status code. ā€˜images?ā€¦.ā€™ queries matching SOME_ID (as introduced above) seem to return valid content.

One thing I tried is to disable caching. This seems to solve the problem, but offers a less smooth navigation experience obviously.

Do you have any idea about could be wrong? I have a Maplibre map inset somewhere in my page that downloads coverage tiles when landing too, and this is working fine.

2

Thanks for reporting! I think maybe image density in the area (you mention SF downtown) could be the cause here. Can you share some image IDs where youā€™ve experienced this behaviour in the past?

3

Sure, this definitely happens around image id 802941794144066, typically upon landing. It does not always happen, though, just very frequently.
Also, disabling caching only seems to solve the issue (of arrows not showing up). I canā€™t be sure because I have not tested enough and the API does not let me determine if arrows are indeed fully ā€œloadedā€ or not (beyond the spatialedges event which does not seem to be sufficient for this purpose).

4

Thanks! Looks like the API requests get very close to timeout (30 seconds) in the area around that image so I can imagine that there could be situations where the requests time out and that would be the cause of the errors you see. Weā€™ll look into optimizing this API query for areas with high image density.

1 Like
5

Sounds good. It is true this area is very dense. I will just disable caching for now and see how it goes in the future. Thanks for your insight and quick replies.

6

Just as I was sending the message I did notice I also got the same warnings in the console and the same unexpected behavior (missing arrows) with caching disabled :-(.

7

Weā€™ve made updates to optimize the loading experience and now the arrows load significantly faster and you should not experience missing arrows even in the most densely captured area. Let us know if you experience any more problems.

1 Like
8

Thank you! I will soon have the possibility to test thoroughly.

9

I donā€™t know if I have done something wrong, but the situation seems much worse than before.

I am now getting plenty of errors, such as:

Failed to cache spatial images (556151223013153). MapillaryError: 105 (MLYApiException, AAc4NZL5ā€¦ā€¦ā€¦..auQ): The parameter image_ids must have at most 30 elements, 200 found.

Actually, I canā€™t get arrows to load at all in that area anymore.

Still using Mapillary JS 4.1.2.

10

Hi @andynewmanny - Iā€™m able to see arrows on Mapillary for both images you specified: https://www.mapillary.com/app/?pKey=802941794144066 and https://www.mapillary.com/app/?pKey=556151223013153 and they show up pretty quickly. Is that working for you?

11

Hi ive been having the same issue. im making a geoguessr game and cant seem to get the arrows to appear because of an MapillaryError: 105 error. when i do it on icognito the first round works but after it doesnt. This makes me believe its something to do with the cache. Have you found a solution because im stumpped

12

Sorry I was away last week. Thanks for your reply.
I just tested with Edge on Windows 11 (no extension installed, not in incognito mode), and the first link immediately gave me these errors, see the capture below:

mapillary_error
mapillary_error1913Ɨ1105 692 KB

These, now, are the errors I am getting using the Mapillary JS 4.1.2 control on my own web site:

mapillary_error2
mapillary_error2553Ɨ990 84.8 KB

URLs related to ā€˜500 Internal Errorā€™ lines are like this:

https://graph.mapillary.com/images?image_ids=1449714029078538,1402850574213495,1632055944096459,28223991380578506,1313035833260281,2528949507275800,2070052510074267,1061384912422583,1136864148230870,1011572180899161,1291804558755820,2774341642744440,3890448841271495,1330584614787757,1996422817528986,1946929512500867,1257041685369322,1555160398484910,1308205480409560,1159998242178717,1515079735827633,544326064705558,1150515622865789,492622943874204,1005717758060552,1419748632332775,1361190511979977,1161744072329792,3999151470413351,1167591251675451,495542629830211,1613937052632615,1815136552586681,2670029226719141,1154787516261899,1296088415059225,1288294209192404,2073887926369940,1630078371723944,1621362625931952,1657038041868704,583277447929788,1330639375037277,1271788943883725,2015322422303767,1165367581678276,1647905856161562,1630072037611190,406268252512842,1114661703474142,1204155358094039,3547548012204495,3965867630406688,2759028010950629,1325340235446133,1905405483632381,1067557064904558,1354022719282613,28676088875339345,1679755892972430,463982013261832,1149991886490379,2074145986776329,568605202669317,2118836981880776,1702947763966815,2344795782666000,1168172921514928,478345081981033,579115874921817,1007383537974224,1317218129427296,1938726909953032,2386752271693791,549778024123795,1167404644807636,2823133741178467,1326083958807851,1187654406128816,407437642391489,2005783716514211,1143798973809054,1572586087477059,1802225503930200,1670021323603709,501984086290041,1336129304204595,1161008762210134,1763454264402959,1193987571973590,1009788771033577,1138689614303158,1835796213888649,1266549417793258,1720320671848204,1181914106933587,1100911678436491,1359872422061866,1298905041363105,527800419581803,1159047094819844,1244986716601678,1616595223076041,1895937390902033,508755895279578,1819971865492833,1358747495481136,1085367483400112,2065135277322788,1345839066434776,1294436664999657,1696562547873816,549036461471442,1109370254022557,1637528433816599,28200477672900899,1773096229897802,1917826485690883,1730482267800900,1005074644791708,1138191171305320,1651947972427202,1171622468156818,546687404447300,1141664347591675,1157355742452991,1878230366249064,1667462520810434,1462030798097258,1126239875609448,1011975610949094,1694364194789442,485021997950063,1137850024638037,1005448904812048,1114513296668698,1791174535010246,1189729676054518,1134342494745050,1345354836650199,2187909941660460,3958959347709878,3348350445300750,1128358102305304,584254584419939,468822946061944,1651214829079039,2589347454596267,1669248857008803,2018044562038312,1302184044378813,1420355372063403,1170482351332338,1031071172202592,1353477982562588,1010347850965253,1710251496190859,1317420656178610,1135158528005927,1304781213910744,1217774506636528,1887931311970388,4118882825009019,1630316677847562,1130870884676086,1533843260587709,530829300006037,1022026789687423,2186783538382700,1108384440743966,1102074321655907,1010469620925387,1590442721862115,1146416660826431,1125597971989384,538938424179864,1452276605732369,566043169603787,1541048653259003,1133602311637930,1006068034711929,1026070952673137,1626543274910402,523077490809858,1062871778942391,1180842710419630,1008771937811883,1685717285353008,1332389704568086,1696221744642981,1687830368757228,1119156846329115,1789828398226485,1092267245971769,1609868292962659,470857119211136,1115005033178791,1152208923169285,1156842266016320,1115780726429613&fields=id,computed_geometry,geometry,sequence,altitude,atomic_scale,camera_parameters,camera_type,captured_at,compass_angle,computed_altitude,computed_compass_angle,computed_rotation,creator,exif_orientation,height,merge_cc,mesh,organization,quality_score,sfm_cluster,thumb_1024_url,thumb_2048_url,width

I tried to disable caching when using your control, by using cache: false in the initial configuration, but it didnā€™t solve the problem.

I am completely stuck because of these issues, this unfortunately is a complete showstopper for me :frowning:

13

@nikola - any ideas?

14

Thanks for the error logs, looks like the issue affecting MJS in your web app is different than on mapillary.com. Weā€™ll investigate.

15

The errors when using Mapillary JS 4.1.2 should be fixed now. Weā€™ll continue to work on improving the performance and stability of these API endpoints.

16

Thanks for your prompt response to the issue. Unfortunately, it is still not working for me. I am getting another error now (and no arrows), here on Edge :

image
image1334Ɨ744 382 KB

(Quick note: in my previous message you may have noticed the Ghostery browser extension in the capture - it is actually not active, hence the icon was greyed out ; I had tried to uninstall it altogether, to no avail).

In another location in Paris, I am getting "Service temporarily unavailableā€ errors today, this time with Chrome :

image
image1301Ɨ728 356 KB

In this latter case, some arrows, not all of them, erratically appear.

17

The density of the images in those areas is so high it makes it difficult to fetch all nearby images for showing navigation arrows. Weā€™re working on reducing the amount of data required for this functionality to improve performance and stability.

18

Can disabling the cache or decreasing the cache depth help? Again, I tried with cache: false, it didnā€™t work. Is there a way to reduce the number of image_ids (which are neighboring ids, I guess) ? Any hint about what could help would be welcome. Anything really, as this makes map navigation completely unusable in most large cities.