Results 69 issues of Andi

Fixes #2395. This PR adds a new encoded value `development=country/residential/city` distinguishes country roads from residential areas and residential areas from city centers. The calculation is rather simple, but seems quite...

new feature

Probably the simplest measure for road steepness that could be implemented as encoded value is the average slope of an edge, i.e. the elevation difference between the tower nodes divided...

new feature

When we use `areas` in a custom model file we might face the issue of having to copy and paste large amounts of geojson data into the custom model file...

improvement

The GH server still supports not specifying a `profle` and using the `vehicle`,`weighting`,... parameters instead (LegacyProfileResolver). While the GH Directions API will probably support these parameters for legacy reasons for...

This will be a big refactoring task that we will have to split into several smaller issues. We can keep a list of related issues here and also discuss the...

refactoring

I took a look at the usage of access flags in PT. We are currently trying to move access flags into the weighting as much as possible (#1835). The biggest...

The A* heuristic (h) must fulfill two properties so we can use it the way we use it: 1) The heuristic must be 'admissible', i.e. it must never overestimate the...

bug

Encoded values are often very simple. We take some OSM tags as input to a `TagParser` and set some bits to store some value like the `RoadClass`. However, there are...

refactoring

The properties file uses our own format, based on DataAccess. This is pretty annoying to work with when we open the file in a text editor. Can we use some...