Avoid or include a large amount of POIs in route-planning

[easbar]

@Tiefi

when passing those same blocked areas along with the request?

Anything you do in a client custom model that you pass along with the request you can also do with a server-side custom model you setup in your configuration file.

@Tiefi

I think if I modify the PBF by including the points or polygons, they would not be accessible when planning routes with GH, right? Since route planning only looks at road attributes (besides blocked areas that are passed along with the request).

We did some work towards using OSM relations to set road attributes for roads located within the area of relations here: Add landuse encoded value based on closed-ring ways tagged with landuse=* by easbar · Pull Request #2765 · graphhopper/graphhopper · GitHub. But for the use case you are describing I think using the custom area feature, or the using the location index like karussell suggested would be ideal.