#21020 closed defect (duplicate)
Mapillary image date is not displayed
Reported by: | pyrog | Owned by: | taylor.smock |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin mapillary | Version: | |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- press plugin preferences
- deselect "Display hour when the picture was taken"
- press Okay
- press plugin preferences
- select "Display hour when the picture was taken"
- press Okay
What is the expected result?
The date/time must be displayed
What happens instead?
The image id is displayed
Please provide any additional information below. Attach a screenshot if possible.
Revision:17919 Build-Date:2021-06-02 20:30:01 Identification: JOSM/1.5 (17919 en_GB) Mac OS X 11.4 OS Build number: macOS 11.4 (20F71) Memory Usage: 872 MB / 2048 MB (139 MB allocated, but free) Java version: 16.0.1+9, Azul Systems, Inc., OpenJDK 64-Bit Server VM Look and Feel: com.apple.laf.AquaLookAndFeel Screen: Display 69732928 1280×800 (scaling 2.00×2.00) Maximum Screen Size: 1280×800 Best cursor sizes: 16×16→16×16, 32×32→32×32 System property file.encoding: UTF-8 System property sun.jnu.encoding: UTF-8 Locale info: en_GB Numbers with default locale: 1234567890 -> 1234567890 VM arguments: [-Djpackage.app-version=17919, --add-exports=java.desktop/com.apple.eawt=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=/Applications/JOSM.app/Contents/MacOS/JOSM] Dataset consistency test: No problems found Plugins: + Mapillary (2.0.0-alpha.12.3) + SnapNewNodes (1557488602) + apache-commons (35524) + apache-http (35589) + buildings_tools (35756) + cadastre-fr (35758) + ejml (35458) + geotools (35458) + jaxb (35543) + jna (35662) + jts (35458) + opendata (35640) + photo_geotagging (35738) + photoadjust (35770) + scripting (30798) + utilsplugin2 (35691) Tagging presets: + https://raw.githubusercontent.com/OpenNauticalChart/josm/master/INT-1-preset.xml Map paint styles: - ${HOME}/Downloads/Styles_ColourGPSData-style.mapcss Last errors/warnings: - 00039.659 E: Failed to locate image 'object--wire-group' - 00039.857 E: Failed to locate image 'regulatory--dual-lanes-cyclists-and-pedestrians--g1' - 00041.264 E: Failed to locate image 'regulatory--texts--g1' - 00041.266 E: Failed to locate image 'regulatory--texts--g2' - 00041.567 E: Failed to locate image 'void--car-mount' - 00041.569 E: Failed to locate image 'void--dynamic' - 00041.571 E: Failed to locate image 'void--ego-vehicle' - 00041.572 E: Failed to locate image 'void--ground' - 00041.586 E: Failed to locate image 'void--static' - 00041.901 E: Failed to locate image 'warning--kangaroo-crossing--g1'
Attachments (2)
Change History (8)
by , 4 years ago
Attachment: | Capture d’écran 2021-06-20 à 19.50.10.png added |
---|
by , 4 years ago
Attachment: | Capture d’écran 2021-06-20 à 19.49.50.png added |
---|
comment:1 by , 4 years ago
1568042686344
is milliseconds since epoch, which is Mon 9 September 2019 09:24:46.
I've been meaning to fix that, but I've been more worried about the v3 Mapillary API shutting down, so I've been focused on the basics for the Mapillary v4 API (image viewing). This is the second bug report on this, so I'll take the time to fix this visual bug.
Thanks for the feedback -- it helps me prioritize.
comment:2 by , 4 years ago
Sometime (randomly ?) the date is displayed.
This is an "real" issue because it's not possible to know if the picture is up to date, or is i.e. 5 years old.
comment:3 by , 4 years ago
That is probably due to mismatched APIs (vector rules give me ms since epoch, api gives me ISO timestamps, iirc). I'm still using the v3 API, but in a largely v4 manner. I've got a release with mostly v4 API calls that I rolled back due to reports of rate limiting.
I'll check the rate limiting tomorrow, or I can cross my fingers and hope that it is fixed, and release the v4 API version today. I'm personally inclined to so that tomorrow, when I know I can ping someone at Mapillary if it is still rate limited.
comment:5 by , 4 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Closed as duplicate of #21002.
Mapillary Preferences