Geographical map of the Electorate of Brandenburg, map from 1758

Open data API in a single place

Provided by Landesvermessung und Geobasisinformation Brandenburg (LGB)

Get early access to Geographical map of the Electorate of Brandenburg, map from 1758 API!

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

Dataset information

Catalog

Landesvermessung und Geobasisinformation Brandenburg (LGB) catalog

Country of origin

Germany

Updated

2026.03.09 11:43

Created

1758.12.29

Available languages

English

Keywords

karte, kultur, opendata, bodenbedeckung, historisch, stadtplanung, vermessung, historische-karte, forschung

Datasource

Official portal for European data link

Quality scoring

Dataset description

The map titled — Geographical map of the Electorate of Brandenburg... — was stabbed in the middle of the 18th century by Mätthäus Albrecht Lotter and published around 1758 by Tobias Conrad Lotter in Augsburg. It sets the region on a scale of approx. 1: 550 000. The LGB copied the old colored copper engraving. The reproduction took place in cooperation with the Brandenburg State Archives. There is the original copper engraving, which served as a template. The card has a size of 67 cm x 59 cm.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service