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
So OIN's spec also requires HTTP content-range, which nginx 1.2.1 provides, but apparently whatever Rails is doing to serve files does not. We could set up a separate nginx instance to just serve static files, though.
So this would require a new function in the maps_controller.rb which would output JSON in this format with all the information we're able to provide, at a route like https://mapknitter.org/maps/<map-slug>/metadata.json. But as we are transitioning potentially to image-centric listings instead of map-centric, would we want to quickly change this to display for each image, instead?
Under the new exporter, we may have a GeoTiff for each image, but even a JPG would be OK to report in this format. Some of the fields we'll need to research a bit more using the above link.
https://github.com/openimagerynetwork/metadata-spec/blob/master/sample.json
https://github.com/openimagerynetwork/metadata-spec
The text was updated successfully, but these errors were encountered: