Performance of API is dependent on the number of features that query will return , Currently we have a validation of area but having only area validation may not make sense because its about the features and the size of file we are returning from that place , For example small dense area may contain high no of OSM features and larger less populated area can contain smaller no of OSM features ! The idea is to have a validation of approx. max no of features before processing the request on API , May be we can give warning to the user when it crosses the max no of rows. ( Topic of Discussion ) We can determine how much no of features we should keep on validation based on the performance .
cc : @omranlm @JorgeMartinezG @ramyaragupathy @robsavoye
Relates to :
Performance of API is dependent on the number of features that query will return , Currently we have a validation of area but having only area validation may not make sense because its about the features and the size of file we are returning from that place , For example small dense area may contain high no of OSM features and larger less populated area can contain smaller no of OSM features ! The idea is to have a validation of approx. max no of features before processing the request on API , May be we can give warning to the user when it crosses the max no of rows. ( Topic of Discussion ) We can determine how much no of features we should keep on validation based on the performance . cc : @omranlm @JorgeMartinezG @ramyaragupathy @robsavoye Relates to :
164
174