It closes #101 by including the created_on field on the order representation returned by the REST API
It is also connected to #96 since it adds the backend code for retrieving the email field from the request
It is also connected to #86 whereby it enables shapefile download requests to take into account the taxonomic_categories parameter. A request like the following (I'm using httpie as a client):
This request results in the server creating a shapefile clipped to the specified bounding box and with only the features whose parsed_taxonomy attributes match the ones in the request
Note that similar functionality is not yet available for downloads that request geopackage as the format (currently the geopackage code only takes into account the bounding box, not the taxonomies)
This PR addresses several issues:
It closes #101 by including the
created_on
field on the order representation returned by the REST APIIt is also connected to #96 since it adds the backend code for retrieving the email field from the request
It is also connected to #86 whereby it enables shapefile download requests to take into account the
taxonomic_categories
parameter. A request like the following (I'm using httpie as a client):This request results in the server creating a shapefile clipped to the specified bounding box and with only the features whose
parsed_taxonomy
attributes match the ones in the requestNote that similar functionality is not yet available for downloads that request
geopackage
as the format (currently the geopackage code only takes into account the bounding box, not the taxonomies)