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
The Peripleo v.1 API included a geo_bounds field that contained the geographical coverage of the item. If the items was not a place itself (which has inherent geo-coverage), but an object, the geo_bounds would be based on the places referenced by the object.
New Peripleo no longer has this type of de-normalization. Should we introduce some sort of workaround? Perhaps at least for the legacy interop of issue #118?
The text was updated successfully, but these errors were encountered:
The Peripleo v.1 API included a
geo_bounds
field that contained the geographical coverage of the item. If the items was not a place itself (which has inherent geo-coverage), but an object, thegeo_bounds
would be based on the places referenced by the object.New Peripleo no longer has this type of de-normalization. Should we introduce some sort of workaround? Perhaps at least for the legacy interop of issue #118?
The text was updated successfully, but these errors were encountered: