[Requirements] 8. Get All Map Features In A BBox

[Rubix982]

Is your feature request related to a problem? Please describe.
This issue deals with the 8th requirement from the PRD extracting all map features within a BBox

Describe the solution you'd like
The base requirements are,

1. Bbox coordinates as an argument
2. Layer as argument (points or traffic signs)
3. Filter argument 1: Value list as argument (only one value or multiple values or “all”)
4. Filter argument 2: other -- date first seen, last seen, more?

Describe alternatives you've considered
NA

Additional context
Maybe split this into 2 functions, one for traffic signs and one for points

Output is a GeoJSON object

[Rubix982]

@OmarMuhammedAli aren't first_seen and last_seen properties instead of fields?

[OmarMuhammedAli]

@Rubix982 Yes, they're properties. We generally have no fields associated with requests for tiles endpoints in general I think.

[Rubix982]

So the filtering will be done after the data has been retrieved as a GeoJSON.

What,

• kind of filtering are you thinking of performing with the properties?
• What kind of inputs do you imagine being sent by the users
• What functions do you need for that?

Maybe I can create issue(s) for these and work on that.

[OmarMuhammedAli]

• User inputs should be:

  1. layer: either map feature point or traffic sign
  2. bbox: a list of the bounding box coords
  3. filters: a list of filter values supported by the API to be applied on the returned tiles

• I can think of filtering as 2 separate processes for now:

  1. filtering related to the filter values dictated by the user
  2. Checking if the returned map features actually lie within the box (There're 2 utility issues created for that: [Utility] Check if given features exist within the bounding box #27 and [Utility] Check bounding box validity #40

• I need to give that more thought, the same goes for the previous points.

I will keep replying to this comment If I think of anything else