mobility-database-catalogs
mobility-database-catalogs copied to clipboard
Set the bounding box coordinates to null when out of range
What problem is your feature request trying to solve? We extract the coordinates of the bounding box from a given dataset and keep these coordinates without checking their values. Sometimes, we end up extracting invalid coordinates (out of range). The coordinates should be set to null in such a case.
Describe the solution you'd like Make sure that the extracted coordinates are valid. If not, set the coordinates to null.
Suggestion from a consumer perspective: While it's not valid GTFS, it would be good to still get a bounding box for such GTFS feeds based on the valid stops in the feed, as the feed otherwise might go undetected.
How about this: Rather than returning a null
bounding box, ignore those stops that have invalid/missing coordinates and calculating the bounding box only based on valid stops.