Knooppuntnet issues
About | Planner | Analyse | Monitor | Issues | ||||||||||||||||
Node network issues in the fieldAn obstacle on your route? Is the sign missing? - The Netherlands: meldpunt routes. - Belgium: - France : Suricate. Map issueOpenStreetMap and knooppuntnet are different open projects. Therefore support concerns need to address OpenStreetMap for "data" issues, and knooppuntnet for "software" issues. For instance, problems with the underlying map data (key and value omissions, way connection errors, inconsistencies, etc.) can cause the knooppuntnet planner to miss the very best routes. Once the underlying map data is fully complete and correct, knooppuntnet should produce expected results. The knooppuntnet data is frequently updated from the OpenStreetMap database (OSM for short). Most of the data requires constant vigilance to remain relevant and accurate with numerous organizations moving, or going in or out of business each month. Supplying correcting map information to the OpenStreetMap organization is very easy. You can simply just report problems, and that by itself is very helpful. Or you can actually roll up your sleeves and edit the map data directly. After registering you can use the free user programs to edit the underlying data directly.
Knooppuntnet software issueFor issues with knooppuntnet itself you can contact the author via the OpenStreetMap messaging system, or you can create an issue on github. - Contact author at vmarc (requires login on OpenStreetMap website). - Verify if your issue is already documented in github. If you cannot find an issue that matches your problem, you can create a new issue (this requires github login). |