mansehej / delhimetroapi Goto Github PK

Hi,

Issue:
I was going through a project (more of a ripoff of your work 😅) that was using your API and found an issue that was raised at your end.

currently, your API raises an internal error (<500>) if the station name does not match the exact case.
example:

- This will raise an error : Error: could not handle the request

https://us-central1-delhimetroapi.cloudfunctions.net/route-get?from=aiims&to=INA

• While This is fine

https://us-central1-delhimetroapi.cloudfunctions.net/route-get?from=AIIMS&to=INA

I would suggest it would be great if you can either make all the station names to upper case or small case. That will solve this issue. An API must handle such data inputs.

keep up the good work 👍

This error is coming, whenever i try to call api.
Access to fetch at 'https://us-central1-delhimetroapi.cloudfunctions.net/route-get?from=Dwarka&to=Palam' from origin 'http://172.1.1.0:5000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-CORS' to fetch the resource with CORS disabled.

so please add the appropriate CORS headers to allow requests from my domain

Going from Karkarduma Court to IP Extention requires no interchange as they are both located on the Pinkbranch line.

However, the route returned by the API shows 2 interchanges -

1. Pinkbranch to Bluebranch at Anand Vihar
2. Bluebranch to Pinkbranch at Karkarduma

This happens due to 2 consecutive stations - Anand Vihar and Karkarduma lying on both the Bluebranch and Pinkbranch lines. This feature is unique to these 2 stations across the whole Delhi Metro Network.

This problem can be replicated by calling the api for any route on the Pinkbranch line that passes through both Anand Vihar and Karkarduma.

example: https://us-central1-delhimetroapi.cloudfunctions.net/route-get?from=IP%20Extension&to=Karkarduma%20Court