Custom mesh as an optional field in route request

antarctica / PolarRoute-server

Backend server for serving PolarRoute and MeshiPhi assets and managing their calcuation using Django & Celery.

MIT License

0 stars 0 forks source link

Custom mesh as an optional field in route request #5

Open davidwilby opened 3 months ago

davidwilby commented 3 months ago

At some point, route requests will need to be able to be requested to be calculated using a specific mesh.

davidwilby commented 1 month ago

I actually disagree with this design, I think that the mesh that is used should be decided in the back end, not in the request.

davidwilby commented 1 month ago

I've had a partial change of heart here in thinking that within a devtools interface in SIIS it might be useful to be able to specify the particular mesh used. Will think more on this but I still don't want mesh specification to be a part of a publicised API.