Bryan Haberberger
Bryan Haberberger
I don't mind doing it! I will look at it tomorrow or the 13th. I can't make the call this Friday 1/14, I will be out 1/14-1/18 but I can...
In Presentation API 3, there is context collision around the `type` property (when embedding the GeoJSON content in the service), where the service object `type` would have to be an...
Since the value for `navPlace` can be embedded, you can still provide your service that way like ```JSON { "navPlace":{ "id": "http://my.geo.service/GeoJSON/point/12,12/", "type":"Feature" } } ```
The draft PR is available at https://github.com/IIIF/api/pull/2089
See https://github.com/IIIF/api/issues/1246 for discussion around GeoJSON in IIIF. This is directly related to #135.
See https://github.com/IIIF/api/issues/1246 for discussion around GeoJSON in IIIF. This is related to #118, #119. #133, #135.
The solution to this will most likely be offered in connection with issue #118
Note that geocoding an image segment is not the same as geocoding a word in a transcription. One can imagine there is a canvas which contains the image of a...
There is a related issue on this point being discussed in https://github.com/IIIF/api/ at the following link https://github.com/IIIF/api/issues/1246. Perhaps using a `service` at all for this doesn't make sense. Alternatives are...
See https://github.com/IIIF/api/issues/1246 for discussion around GeoJSON in IIIF. A third party solution will involve that third party creating an Annotation that targets the first party's resource. IIIF Annotations can support...