What is the best way to craft the route for geo stuff?

drewrwilson commented 9 years ago

Hey @techieshark,

To complete #29, I hardcoded a new route /geo as the route for the geojson for all stands. But now I'm realizing that it could contain all the same data as the /stands route but just be in a different format: geojson instead of json.

So I'm wondering what is the best design:

Keep as-is: this /geo route as separate even though the query is the same as the /stands and we'll deliver the response in geojson so it needs to have a different rout.
Or is there a way to add a parameter to the /stands right to specify that the response should be geojson? When I try to define a route as /stands/geo restify reads geo as the :id for this other route: /stands/:id
Curveball option: Should we just make /stands always return geojson for both the fronted and the map? We would then need to update the frontend to make sure we're getting the correct attributes from the new geojson response.

drewrwilson commented 9 years ago

Two ideas from @techieshark:

X-HEADER-TYPE=geojson

or

/stands?format=geojson

techieshark commented 9 years ago

Is this still relevant? I thought we were just pulling /stands and then converting on the fly now?

drewrwilson commented 9 years ago

Yeah it is not relevant anymore we can close it On Dec 19, 2014 5:16 PM, "Peter W" notifications@github.com wrote:

Is this still relevant? I thought we were just pulling /stands and then converting on the fly now?

— Reply to this email directly or view it on GitHub https://github.com/drewrwilson/lestandsjs/issues/31#issuecomment-67719079 .

drewrwilson / lestandsjs

What is the best way to craft the route for geo stuff? #31