UrbanOccupationsOETR_1532_Ottoman_campaign_1840s_settlements_dataset

Open data API in a single place

Provided by Zenodo

Get early access to UrbanOccupationsOETR_1532_Ottoman_campaign_1840s_settlements_dataset API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2022.09.15 00:00
Created
2022.09.14
Available languages
English
Keywords
geospatial modelling, least cost path, slope gradient, network analysis
Quality scoring

Dataset description

This dataset contains the data used for the below-mentioned publication of our transport network and least-cost path model. It analyzes 16th- and 19th-century transport networks between Istanbul and Sofia. The historical settlement data is based on work by the UrbanOccupationsOETR (https://urbanoccupations.ku.edu.tr/)  and POPGEO_BG projects. If you would like to use the dataset for further publication, please use the credentials specified below: Kabadayi, M Erdem, Piet Gerrits, and Grigor Boykov. “Geospatial Mapping of a 16th Century Transport Corridor for Southeast Europe.” Digital Scholarship in the Humanities 37, no. 3 (2022): 788–812. https://doi.org/10.1093/llc/fqab084.  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks