Wait,. .. when was the 'noname' layer gone? Yves
Le 7 novembre 2019 08:06:27 GMT+01:00, Christian Quest <cqu...@openstreetmap.fr> a écrit : >We've been "addressing the address topic" for more than 5 years in >France >with our BANO project. > >Here is an overlay I created back then to show existing and missing >address >data in OSM compared to available OSM compatible sources. > >http://osm13.openstreetmap.fr/~cquest/leaflet/bano.html#16/48.7908/2.6542 > >Green: the address is in OSM (and the named road too) >Blue: address is missing but the road name exist in OSM >Red: address missing and we found no road with that name nearby > >If you want to make missing data obvious, you should no dimm the >shapes, >but make them highly visible. >The goal with the above rendering became "dégommer du rouge" (get rid >of >red). > > >Le mar. 5 nov. 2019 à 19:43, Steve Coast <st...@stevecoast.com> a écrit >: > >> Hello >> >> >> >> Maps have three basic components: Display (does it look nice?), >Routing >> (Can I get from a to b?) and Geocoding (Where is this address?). >> >> >> >> OSM is extremely good at the first one, and pretty good at the second >one. >> But it’s pretty deficient in the third area: address data. >> >> >> >> The question is, how can we fix this? Addresses are a big, big >problem in >> terms of how much data we need to go collect. There are a few ways >forward >> with outside commercial or government data, but they tend to be >difficult >> because the data is patchy or licensed in ways that aren’t very >compatible >> with OSM. >> >> >> >> It seems like it would be a good idea to think about this from the >bottom >> up in a community way, and this doesn’t really exist in OSM right >now. It >> seems like we need better feedback loops to: >> >> >> >> 1. Community can see where the address data is (and isn’t), >because >> it’s not very obvious today when using osm.org >> 2. Make the tools to add address data better so that it’s easier >to >> fix. >> >> >> >> To that end, here’s a tile server that highlights address data: >> >> >> >> >> >http://ec2-52-50-19-165.eu-west-1.compute.amazonaws.com/#10/39.7561/-104.9574 >> >> >> >> It shows roads with address data normally and kind-of hides other >roads, >> to make it obvious that “something is wrong with this map”. We could >have a >> tag (maybe it exists already) that says “this road doesn’t have >addresses” >> and/or a tag that says “this road is complete”. (right now it’s just >got >> Colorado and Utah in it). >> >> >> >> When OSM started, the map looked very broken and incomplete because >there >> was missing data all over the place. This created a large incentive >to go >> fix the map. The idea with this tileserver is to do the same thing >and make >> the map look broken to create a large incentive to fix it. If we, one >day, >> switched the main osm.org site to using this rendering then it would >> create an urgent need to find all the addresses in the places where >they >> exist. It could also be done on a temporary basis for a few weeks, or >on a >> per-country basis or some other slow introduction to see if it >worked. It’s >> just an idea. >> >> >> >> On the tools side, there’s much that can be done to make collecting >and >> entering addresses easier. I’ve been collecting UI/UX changes to >tools >> (e.g. iD or Go Map!) that would make addresses better: >> >> >> >> https://wiki.openstreetmap.org/wiki/Address_SIG >> >> >> >> It also seems worthwhile to create a group of people interested in >> addressing in OSM (an address special interest group or working >group) to >> push these ideas forward so that we can “finish” OSM by getting all >the >> addresses done. >> >> >> >> What do you think? >> >> >> >> Best >> >> >> >> Steve >> >> >> _______________________________________________ >> talk mailing list >> talk@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk >> > > >-- >Christian Quest - OpenStreetMap France
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
