is it possible to use a filter to display only the latest tracks?
2 Likes
yes, i am aware of that. however, i can only limit a period of time. outside the period, everything falls out, no matter how old the recording is. i would like to have a slide switch like the one on your screenshot for 360 degree recordings. if i activate it, it only shows 360 degree recordings. a switch like this for only the most recent recordings, or another solution.
Do you mean that you want to see the latest capture in a particular area regardless of how old it is? So if an area has captures from 2019 and 2020 only you want to see the 2020 capture, and at the same time if an area has captures from 2022 and 2023 you want to see the 2023 capture?
1 Like
if there is only one track in the section, then it should be displayed. if there are two, three, four tracks or more, then the most current of the possible tracks should be displayed. but i just realized myself that this will probably not work, because then it would always have to be the same tracks. as soon as someone turns left instead of right, it no longer fits.
the more tracks there are on a street, the more confusing i find it. yes, you can use the filter, but it’s not really suitable for this, because you would first have to look at what you want to filter out. and so you filter out tracks that you actually want to see. simply because they match the filter you set.
1 Like
Gotcha, yes, the captures display can be a bit overwhelming. Thanks for this feature suggestion, we’ll add this to our backlog for something to look at in the future!
1 Like
@boris While we are at the topic of dates and timestamps on Mapillary; please finally render locale specific timestamps everywhere in the web app, especially in the sequence feed. This pseudo English time format is really annoying and confusing. 
Filtering in ISO 8601 is fine and understandable but reading timestamps in pseudo English is annoying. Please also render the complete full precision timestamp in the … image details sub‑menu because 
seconds and sub‑seconds sometimes do matter. I really appreciate the fact that the Mapillary Streets map layer and the rest of the website have finally been internationalized, while though with dumb AI, it is better than nothing. However, please put in some final effort to polish the map UI as well.
1 Like
Hi @GITNE, for timestamps in the web app I see things like “Jun 15, 2023” is this what you mean by “pesudo English”? I understand that we could localize this, but is there confusion about what date this represents?
Thanks for the request on seconds/subseconds
Also the website (with the exception of /app) and the mobile apps are now translated into 22 languages (by humans, not AI translation)
1 Like
… things like “Jun 15, 2023” is this what you mean by “pseudo English”?
[…] but is there confusion about what date this represents?
Right, confusion sometimes happens more with the time part of the format when quickly scrolling through the feed. For example, most of the world does not use AM/PM suffixes nor does “mix up” days and months but orders granularity from largest to smallest or vice versa. This situation becomes particularly annoying when you know that there is an easy fix for this in JavaScript. In other words, there is a built‑in function available that renders to locale specific timestamps with a simple parameter flag.
Thanks for the request on seconds/subseconds
I am not the first and only one to request this already long time ago. So, I guess many people would be happy to see it too.
Also the website (with the exception of /app) and the mobile apps are now translated into 22 languages (by humans, not AI translation)
Maybe not by AI directly but by humans using AI to do their job? 
Since I have been in the business of software i18n and l10n for some years now, sometimes I can tell. Maybe some translators did their work without context, hence some messages read strange or make little sense? Anyway, overall the majority of messages look great.
1 Like
Gotcha, thank you - that makes sense! We’ll put this on the backlog (cc: @nikola).
In terms of translation, yes, sometimes the translators may not understand a lot about street level imagery and the context (though they shouldn’t be using AI for their job) - but glad to hear that the majority of the messages look great. 
1 Like
@GITNE - quick follow-up on this: thanks to your request the web app now displays timestamps in the local locale format. You can also now find precise seconds and milliseconds as well in the “Capture time” section of “Advanced” in Image details.
Thank you again for the suggestion and thanks @nikola for the implementation!
3 Likes
Hey, this looks great! Thank you for finally implementing.
However, I have one omission and perhaps a little nitpick to report:
- The timestamp marked with the red rectangle is not rendered to current locale.
- Imho, for the sake of consistency, capture time should be placed below “Captured on” in the “Image details” section and be labeled “Captured at” because it is actually a detail, not advanced stuff. Additionally, when the web app is going to get fully localized in the future, “Captured on” and “Captured at” are going to translate congruently in many languages because in many languages you can distinguish between time of day and day of year, like in English.
1 Like
How do I have to interpret the filter icon ?
I see two mountains and a star in it.
I’m seeing the same thing you are
Yeah, I’d guess to interpret it the same way.
@boris Please keep in mind that symbols are highly specific to a culture. Symbols can be very effective in quickly and efficiently transporting even complex concepts in one culture but can also be easily misinterpreted in others. The challenge in getting them right is as old as the written history of mankind.
Anyway, I have seen people use a funnel symbol for filters, which imho is not a good representation of a filter either and perhaps rather more misleading than helpful. The simplest filtering device known to mankind is a sieve. However, creating an unambiguous sieve symbol is very difficult. So, maybe sticking to localizable text is the only viable option?
Only recently, I think since it has been reintroduced by Android or Google, people used to amuse me when they referred to a menu symbol as the “hamburger button”, which is absolutely understandable.
1 Like
@nikola Thank you for updating the timestamp formatting of the current image.
However, I have noticed something off in the formatting of “Capture time”. It is actually not locale specific but NN:NN:NN.NNN for every locale. This should not be. The correct formatting of a Date object would be something like this:
toLocaleTimeString(undefined,{hour:"numeric",minute:"numeric",second:"numeric",fractionalSecondDigits:3});
Unfortunately, you cannot use timeStyle together with fractionalSecondDigits in the options parameter but since hour, minute, and second default to "numeric" you can define them explicitly with fractionalSecondDigits instead of timeStyle to get the intended result. 
I have also noticed that there is something off with the timestamp formatting on images either. 
Something tells me that the formatting is forced manually, which is not really a good thing to do, especially when it comes to the order of datums. Let the browser/user agent do its thing and better use dateStyle and timeStyle whenever possible. So, we should expect output on a Date object like this:
toLocaleString(undefined,{dateStyle:"medium",timeStyle:"short"})
dateStyle:"medium" should be short enough in all locales for the current layout.