Map feature API endpoint not working with timestamp parameters

Imagery, data, and integrations Mapillary integrations
1

Hi there,

We’ve been using the Map features API endpoint to download traffic signs and all filter parameters work other than the timestamp parameters. The moment these are plugged in the request (start_last_seen_at, end_last_seen_at), the responses are either off in terms of the expected results or no data is returned at all. All this using the same bounding box with and without timestamp parameters.

For example, the moment we introduce this parameter “end_last_seen_at” = ”2024-01-16T00:00:00Z”, within the CURL below:

curl --location --max-time 100 ’https://graph.mapillary.com/map_features?fields=id,object_type,object_value,first_seen_at,last_seen_at,aligned_direction&bbox=-74.05790237,4.69843017,-74.05181180,4.70185870&end_last_seen_at=2024-01-16T00:00:00Z&object_values=regul*&access_token=MLY|XXXXX’

We get responses before and after the selected date, which doesn’t make sense. See sample response below:

        {
            "id": "292046145896969",
            "object_type": "trafficsign",
            "object_value": "regulatory--no-u-turn--g1",
            "first_seen_at": "2016-01-10T10:48:25+0000",
            "last_seen_at": "2016-01-10T10:48:25+0000",
            "aligned_direction": 291.49164
        },
        {
            "id": "2933741083575744",
            "object_type": "trafficsign",
            "object_value": "regulatory--yield--g1",
            "first_seen_at": "2018-11-28T08:08:24+0000",
            "last_seen_at": "2025-10-06T10:51:30+0000",
            "aligned_direction": 193.62357
        },
        {
            "id": "2934258453524007",
            "object_type": "trafficsign",
            "object_value": "regulatory--yield--g1",
            "first_seen_at": "2018-11-28T08:08:14+0000",
            "last_seen_at": "2025-10-06T10:51:25+0000",
            "aligned_direction": 193.8195
        },
        {
            "id": "822807145322375",
            "object_type": "trafficsign",
            "object_value": "regulatory--yield--g1",
            "first_seen_at": "2017-10-01T12:52:37+0000",
            "last_seen_at": "2021-10-13T17:25:36+0000",
            "aligned_direction": 197.16995
        },

And if we instead introduce this timestamp parameter start_last_seen_at = 2024-01-16T00:00:00Z, we get 0 data back, despite there clearly being data that fall within this timestamp, as shown in the response above.

curl --location --max-time 100 'https://graph.mapillary.com/map_features?fields=id,object_type,object_value,first_seen_at,last_seen_at,aligned_direction&bbox=-74.05790237,4.69843017,-74.05181180,4.70185870&start_last_seen_at=2024-01-16T00:00:00Z&object_values=regul*&access_token=MLY|XXXX'

@boris or @knikel can you help us understand what is happening here and/or if there is a bug?

@alien9

2

I also have noticed some issues with the timestamps as well recently. I attempted to filter 10/17/2025 (2025-10-17T00:00:00) to 10/18/2025 but it yielded zero results. They appear on the mapillary site using those filtering parameters but not when I try to utilize the API. Even more strange, when I expand the filtering range to 10/1/2025 to 11/1/2025 the images are returned - I added some additional checks to return the images’ dates and it showed 10/17/2025 for the ones in question. Very strange.

3

@canales Did you find a work around to this issue? Im still experiencing the same problem.

4

@knikel are you able to take a look at this?