I checked a few web frameworks like Laravel, Slim, express.js, etc. None of them has support for query string parameters. I wonder why this happened. I mean the query string is part of the URI and according to the URI standard the path contains the hierarchical and the query string the non-hierarchical part of the URI. Since the complete URI is the resource identifier, not just the path we should use the query string for routing as well. At least this is my logic. For example I think /people?search=keywords is a completely valid resource identifier. Still what I can do with these frameworks is router.get('/people') and then an if-else statement in the controller. So the question is what am I missing here, why is the query not part of the routing?

Hi I am trying to find out what road attributes tagged on OpenStreetMap cause Google maps to choose or avoid road segments when routing bikes. I want to implement some low cost interventions to improve bicycle route finding within my city to make cycling more accessible to people. Do things like “designated bike routes” marked in OpenStreetMap cause Google maps to prefer those streets for bikes when finding routes? If so I’m planning on trying to push city council to adopt a bike route map I am working on so that I can then in good faith add that info into OpenStreetMap and hopefully get Google maps and similar programs to stop recommending busy streets with no accommodations for bike.

I am trying to make some code as reusable as possible, so it is easy to create a new version of the code to experiment with.

i am trying to create a route between two points. i did it like that :
var rp = GmapControl.MapProvider as RoutingProvider;

Compiled with problems:
×
ERROR
src/app/user/user.component.html:3:72 – error NG5002: Void elements do not have end tags “input”