Potsdam in topographic maps 1: 25 000, single sheet from the role Potsdam from 1956

Open data API in a single place

Provided by Landesvermessung und Geobasisinformation Brandenburg (LGB)

Get early access to Potsdam in topographic maps 1: 25 000, single sheet from the role Potsdam from 1956 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:42
Created
1956.12.30
Available languages
English
Keywords
125.000, opendata, karte, bodenbedeckung, historisch, vermessung
Datasource
Official portal for European data link
Quality scoring

Dataset description

These historical maps are reprints from the period from 1770 to 1882 on different scales. This period is followed by the role of Potsdam. It contains 9 maps and 2 aerial photographs of the city of Potsdam in scale 1: 25 000 included. The individual sheets cover the period from 1848 to 1999. They are also to be obtained individually. These historical maps are reprints from the period from 1770 to 1882 on different scales. This period is followed by the role of Potsdam. It contains 9 maps and 2 aerial photographs of the city of Potsdam in scale 1: 25 000 included. The individual sheets cover the period from 1848 to 1999. They are also to be obtained individually.
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.

api.storeBuilt by Apitalks

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

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks