| Evaluating area tag |
OK |
There are still some cases where ways are not detected correctly as way or area |
| Evaluating name tag |
OK |
|
| Evaluating ref tag |
OK |
|
| Evaluating oneway tag |
OK |
|
| Evaluating housenumber tag |
OK |
|
| Evaluating width tag |
OK |
|
| Evaluating layer tag |
OK |
|
| Evaluating bridge and tunnel tag |
OK |
|
| Evaluating lanes tag |
Missing |
This however should be easy to implement. It should also be easy to extend the style sheet to draw separating lines based on the data. |
| Evaluating junction=roundabout |
OK |
junction=roundabout is evaluated and oneway=true is automatically implied. |
| Support for resolving multipolygon relation |
OK |
|
| Merging of adjacent ways with same tag values |
OK |
|
| Generating reduced detail version of areas for faster drawing in low zoom |
OK |
|
| Generating reduced detail version of ways for faster drawing in low zoom |
OK |
|
| Adress lookup |
OK |
We currently evaluate city nodes, city areas and administrative boundaries to build a hierachical index of named regions down to streets. |
| Adress lookup |
OK |
We currently evaluate city nodes, city areas and administrative boundaries to build a hierachical index of named regions down to streets. |
| Support for restriction relation |
Initial |
Restriction relations will be evaluated as part of the routing algorithm, we currently have no support for drawing restriction information. |
| Handle support for water areas, oceans and similar. |
OK |
We can render coastlines and water areas on any zoom level. There are though some visual artefacts on low zoom if coastline data is not complete |
| Handle support for world wide country borders. |
Missing |
We would need to choose a similar aproach as with coastline detection. |