Download count of all items and class for one territory or BBOX ?

[pierzen]

It is possible to have Summary reports with count of issues for items/class using item=xxxx. These issues are listed on top of the report, followed by individual issues.

But the Summary count is not added to the json files. The possibility to download independantly these summary counts would facilitate monitoring various mapping projects using BBOX to define territories. I suggest to have an option to download only summary statistics by item / class.

example http://osmose.openstreetmap.fr/en/issues/open?item=xxxx&bbox=11.17026,9.027054,12.13714,9.724464

would return this same countent in a json file

#	source	age	item	cl	title	count
3595	Osmosis_Building_Overlaps- nigeria	19h	0 overlapping building	1	Building intersection	101
3595	Osmosis_Building_Overlaps- nigeria	19h	0 overlapping building	2	Large building intersection	227
3595	Osmosis_Building_Overlaps- nigeria	19h	0 overlapping building	4	Gap between buildings	16
3596	Osmosis_Polygon- nigeria	2d	1040 invalid polygon	1	Invalid polygon	3
3597	Osmosis_Highway_VS_Building- nigeria	2d	1070 objects overlap	1	Highway intersecting building	419

...

[frodrigo]

The counts are not dynamics value. The are only computed par class and area once a day.

I think we cannot compute it on the fly for any bbox, it will take too long.

[pierzen]

What I propose is simply to offer the possibility to download in a json file these daily count as they appear presently in the HTML list. It could be done simply by adding on the top of the HTML List a .json summary icon to download the summary in a json file and a parameter that would let query this summary from an url link.

[frodrigo]

What I propose is simply to offer the possibility to download in a json file these daily count as they appear presently in the HTML list. It could be done simply by adding on the top of the HTML List a **.json summary** icon to download the summary in a json file and a parameter that would let query this summary from an url link.

Ok, can be done.

But just to be sure, the bbox does not apply on this data on the html view. The bbox only apply to the list of issues at the bottom part.

[pierzen]

What I understand is that the summary in the upper part shows the count of issues in the BBOX at the time of the last processing, and this count corresponds to the sum of the issues listed in the bottom part (where the listing could extend to more then one page). Example : http://osmose.openstreetmap.fr/en/issues/open?item=xxxx&bbox=3.409049,6.591079,3.435189,6.613591 For 2022-01-01, the summary counts 11 issues with item=0 overlapping building, class=2. This count corresponds to the issues listed at the bottom of the report.

[frodrigo]

What I understand is that the summary in the upper part shows the count of issues in the BBOX at the time of the last processing, and this count corresponds to the sum of the issues listed in the bottom part (where the listing could extend to more then one page). Example : http://osmose.openstreetmap.fr/en/issues/open?item=xxxx&bbox=3.409049,6.591079,3.435189,6.613591 For 2022-01-01, the summary counts 11 issues with item=0 overlapping building, class=2. This count corresponds to the issues listed at the bottom of the report.

Yes, you are right, the bbox is used for the count.

[pierzen]

To illustrate the possibilities of monitoring Osmose issues extracting data from the Osmose API, I copy/pasted Issues count summary reports by Item from the HTML-List to a spreadsheet. I then used a conversion Function Source_to_country_and subcontinent and aggregated data by Sub-continent.

These summary count of issues offer a lot of possibilities for monitoring

• Summary count by Sub-continent, country, regions
• Summary count for a BBOX that correspond to a specific mapping project

Below, the Issues count summary table for items 0, 1010 and 1040 is by sub-continent. source summary for item 1010 : https://osmose.openstreetmap.fr/en/issues/open?item=1010

Since Report of individual items returns counts by source, we can determine the country from the source field and aggregate by Sub-continent.

Osmose Geometry / Topology issues reported : Count of issues by items and sub-continent, 2022-01-03

subcontinent	0 overlapping building	1010 duplicated node	1040 invalid polygon
Africa central	93 576	1	66
Africa east	153 005	4	772
Africa north	54 468	1	77
Africa southern	14 696	9	15
Africa west	129 078	4	143
America central&carribean	51 294	10	349
America north	91 868	217	1 833
America south	274 183	31	562
Antartica	11	18
Asia east	85 828	245	505
Asia south	160 114	200	574
Asia south-east	368 349	568	460
Asia west	53 309	8 068	22 508
Europe east	175 976	38	481
Europe north	57 763	15	683
Europe south	131 425	28	517
Europe west	143 348	13	660
Oceania	18 043	181	113
Planet	2 056 334	9 651	30 318