DBTR — Municipal Road Place name — (TPS_GLI)

Open data API in a single place

Provided by Regione Emilia Romagna

Get early access to DBTR — Municipal Road Place name — (TPS_GLI) API!

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

Dataset information

Country of origin
Updated
2025.08.30 22:00
Created
2021.02.17
Available languages
English
Keywords
open-data, toponimi-numeri-civici, gestione-viabilita-indirizzi, cartografia-tecnica-regionale, eu, dbtr, database-topografico, ctr, toponimo-scritta-cartografica, topografia
Quality scoring

Dataset description

The road name has a dual function: on the one hand, it identifies an area of the municipal territory where, in addition to the area more specifically used for the circulation of vehicles and/or pedestrians, other areas of public land may be otherwise equipped. In addition, the road name corresponds to a portion of the road network to which a given municipality assigns a given ‘name’ (e.g. Piazza Saffi), element of the municipal road to which the Civic Numbers refer. Place names are assigned regardless of the patrimony of the road. The road network must therefore also be completed with only pedestrian routes, either because they have their own place name and number (e.g. “Galleria Mazzini” of Forlì) or because they are part of the projection on the road network of civic numbers accessible by internal passages rather than by the road on the front of the building. The same Road Element can contribute to the construction of the route of more than one placename in situations where the boundary between different municipalities stands on the edges of the road itself; within a municipality conversely, a Road Element can be aggregated to form a single Road Mouse. A route characterised by the same name that crosses several localities or hamlets where the civic numbering is assigned locally to the locality itself must be treated as “Road Toponym” marked not only by the name of the road but also by the name of the locality/fraction. In the Regional Topographic Data Base is represented only by its own track.
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