Outdated Osmose markers

[aixbrick]

Hello,

it's the first time posting in Github, so sorry if I make anything wrong :-).

Osmose seems to be (in parts) outdated or is not able to "see" the correction. The problem reported in https://osmose.openstreetmap.fr/de/issue/5fc24656-56d8-83f5-60cf-c454217b0f60 has been solved 7 month ago, but Osmose still shows "footway used with maxspeed=20".

Another recent example: https://osmose.openstreetmap.fr/de/issue/96e313ae-509a-2f5f-4b65-dc7603c802ae. I corrected it, together with other building intersections, 4 days ago but Osmose still reports it.

Maybe something similar to #1301?

Regards

[atorger]

I see lots of these problems as well in northern Sweden were I'm mapping a lot. That is problems that has been fixed weeks or months ago still appears as errors on the map. Like this one: http://osmose.openstreetmap.fr/en/issue/1e550b31-47a3-1422-9110-0e5713ba6336

I have lost count the number of times I've opened up an error in JOSM just to see that it's already fixed. It's very annoying and time-wasting.

[frodrigo]

https://osmose.openstreetmap.fr/de/issue/5fc24656-56d8-83f5-60cf-c454217b0f60

Issue still here.

key	value
source	13301
item	9004
class	9004005
lat lon	50.7638964 6.089354
title	en {{0.value}} used with {{1.key}}={{1.value}}
en	{{0.value}} used with {{1.key}}={{1.value}}
subtitle	en footway used with maxspeed=20
en	footway used with maxspeed=20
timestamp	2021-12-27 07:46:50+00:00
source code

key	value
elem_index	0
type id	W 717518812
maxspeed	20
highway	footway
maxspeed	20
name	Abteiblick
username	Philipp_Sto

There is many issues of this kind linked to the new activation of differential update this summer. But here it is on a MapCSS/Sax plugin, that unusual.

https://osmose.openstreetmap.fr/de/issue/96e313ae-509a-2f5f-4b65-dc7603c802ae.

It gones.

Maybe something similar to #1301?

Unsure.

I see lots of these problems as well in northern Sweden were I'm mapping a lot. That is problems that has been fixed weeks or months ago still appears as errors on the map. Like this one: http://osmose.openstreetmap.fr/en/issue/1e550b31-47a3-1422-9110-0e5713ba6336 I have lost count the number of times I've opened up an error in JOSM just to see that it's already fixed. It's very annoying and time-wasting.

Sorry to hear that, the new differential update save CPU and power. But yes, it come with many issues and few time to fix these.

I move your content to it own issue #1379. And I already have a fix.

[frodrigo]

The koln.osm.pbf extract is not corrupted.