ppawel / osmonitor Goto Github PK

On map view.

OSmonitor shows 10 components for S8 when in my opinion there are just 9. Components number 6 and 9 are problematic ones. Both these components consist of stretch of S8 from Domasław (theoretically from Kobierzyce) to A4 near Wrocław in one direction, and eastern part of S8 in Warsaw in the other. But this Warsaw part is also component 3 (which is fine in both directions). Hence there is one extra component.

Now the paths are not really shortest - they are just any path from A to B. Should be shortest in terms of way length (not node count) - use Dijkstra!

as discussed, not sure where to start to explain it

the tag should be generic as it is not welcome that application specific tags are used in OSM. I wonder if only "road_components" would work

There are missing wikipedia links for roads in poland e.g. ref 243-250

Currently, ways tagged as "in construction" are completely skipped and often this leads to road becoming disconnected only for this reason. Maybe it could be marked differently to avoid thinking about the road as broken.

bicycle=no for trunk check
http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions#Default
Default is 'yes' for trunk. In Poland it is usually (default?) not allowed to use trunks (S class road).

On administrative report there are no links to wikipednia. In Poland this can be used:

http://pl.wikipedia.org/wiki/Wojew%C3%B3dztwo_XXX
http://pl.wikipedia.org/wiki/Powiat_YYY

http://suncobalt.dyndns.org:8080/browse/road_report/PL/DK86

If there is no input length, it can be misleading that the road is green.

Seems to be an error in data when it happens - Mapnik considers them as normal roads.

http://geowebhost.pl/osmonitor/browse/road/DK37
component 1 isn't in relation:
http://www.openstreetmap.org/browse/way/34956893

Why is it reported as disconnected?

http://geowebhost.pl/osmonitor/browse/road/DK76

Very strange road, not handled well by OSMonitor now.

Now that OSMonitor has a proper frontend, it can display more information about a road. The tricky thing is the road input data (length) which is on the wiki.

The idea is to add something similar to road length verification - take area numbers from Wikipedia or some such and verify if OSM boundaries have proper area. This will prevent boundaries from being too badly mapped at least.

in order to ensure postgres responsiveness during updates and report creation it would be good to have those tasks running with a lower priority

Dodanie złego teryt:terc do relacji powiatu powoduje, że osmonitor zgłasza 'no relation' dla takiego powiatu.
Tak było dla powiatu rypińskiego i wielickiego, http://www.openstreetmap.org/browse/relation/2616008/history

These things happen sometimes.

For road with no relation and no segments link "show in OSMonitor" don't work and give error: NoMethodError in BrowseController#road

eg. http://suncobalt.dyndns.org:8080/browse/road/PL/DW225

It should show empty page with refresh button.

Looks like a bug.

Some roads are in the planning/construction stages and don't need to be reported on but still would be nice to have them together with other roads on one page for completeness.

One solution is to interpret some string (like "noreport") in the user notes column and skip the road.

Można dodać również sprawdzanie obecności tagu vehicle_plate_code=.

Idąc dalej, można zrobić także ich weryfikację na podstawie artykułów w wikipedii, bo tam są podane wyróżniki w infoboksach.

There's a problem somewhere for couple of roads, e.g. DW941, DK52 and probably more.

Example: S1 in Poland has three segments and it does not mean it's disconnected.

http://suncobalt.dyndns.org:8080/browse/road_report/PL/S6
component 2 is dual carriageway, but begining and end becomes into single carriageway so osmonitor can't find start & end node

See DW472 for example - there are parts in Czech Republic.

Strange situation:

http://geowebhost.pl/osmonitor/browse/road/PL/DW713

Serbia has no route ref for motorways. They currently have Mxx and Rxxx roads. A M raod road can go over motorways, trunks etc although it is most of the time primary -> M must be at minimum primary or above (trunk, motorway). Same applies to R roads in theory...but same here, a R road should be secondary or higher

last update: 2012-07-14 06:38:07 by Smolenski Nikola Smolenski (changeset 12213800)
The Link goes to
http://www.openstreetmap.org/user/Nikola

afaik the user has changed its OSM user name

E.g.

DK relations should be named "Droga krajowa nr X"
DW relations should be named "Droga wojewódzka nr Y"
Motorways (A) should be named "Autostrada AX"
Expressways (S) should be named "Droga ekspresowa nr SX"

Will be useful to have two more validation messages:

• not all relation members have correct ref tag
• not all roads with ref tag are part of relation

Server time is GMT+4, Poland is GMT+2 - timestamp is confusing. Switch to GMT.

Some (a lot? most?) roads don't have relations but still they have a lot of ways with appropriate "ref". Another graph can be constructed from those ways and reported on.

Wikipedia pages contains information about direction of way and many connected ways. Eg.

http://pl.wikipedia.org/wiki/Droga_wojew%C3%B3dzka_nr_303

Shows that dw303 is near / connected with roads 92, 302, 304, 313 and 32

So it is easy to extract this information form wiki. Monitor can check connection between road and data in wiki page.

From wiki it can look like table with columns
Road Id | List of connected roads | notes | status
dw303 | 302, 304... | … | raport

Connection between roads can be easy check (union of nodes) and maybe check of short link connection.

Examples of boundaries with two occurrences with the same name:

powiat średzki
powiat bielski

Geographical location should be verified in this case (to see if the boundary is geographically within its parent's boundary).

Perhaps "implement by doing" and roll out reports for another country in the process?

S12 & S16 are only on paper
I suggest to remove them from the report

This will be useful for kendzi who is doing comparison between relation "distance" tag and Wikipedia length information.

• Component 1 looks like it's disconnected.
• No end node markers between components - why?
• This roundabout is suspect: http://www.openstreetmap.org/?zoom=18&lat=52.19079&lon=21.52797&layers=BTFT

It should be possible to easily track regressions for roads - for example when someone breaks the relation or road length etc.