You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of returning a list of results which contain GeoJSON fields, we may to return a GeoJSON collection with properties. This would simplify interactions between the sidebar and map on the frontend by reducing the amount of data transformations needed.
We just need to think about how to handle results with unavailable geometries (ex. HydroShare). Something else to consider is replacing the top-level result object with a FeatureCollection. This could work as long as we're able to attach properties for next/prev page URL, number of results, etc.
Instead of returning a list of results which contain GeoJSON fields, we may to return a GeoJSON collection with properties. This would simplify interactions between the sidebar and map on the frontend by reducing the amount of data transformations needed.
For example, instead of:
we could to:
We just need to think about how to handle results with unavailable geometries (ex. HydroShare). Something else to consider is replacing the top-level result object with a
FeatureCollection
. This could work as long as we're able to attach properties for next/prev page URL, number of results, etc.Ref: 317528a
The text was updated successfully, but these errors were encountered: