Final report of the survey on the renaming of Josef-Reiter-Straße

Open data API in a single place

Provided by Stadtgemeinde Gallneukirchen

Get early access to Final report of the survey on the renaming of Josef-Reiter-Straße API!

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

Dataset information

Catalog

Stadtgemeinde Gallneukirchen catalog

Country of origin

Austria

Updated

2025.11.18 00:00

Created

2025.11.18

Available languages

English

Keywords

Neubennennung, Online-Befragung, Josef-Reiter-Straße, Abschlussbericht

Datasource

Official portal for European data link

Quality scoring

Dataset description

At its meeting on 3 July 2025, the municipal council adopted the decision in principle to rename Josef-Reiter-Straße due to the dubious biography of the namesake - Josef Reiter is heavily burdened due to his support of the National Socialist idea and his openly displayed anti-Semitism. A number of naming proposals have been submitted by the affected residents, the population and politicians for the renaming in the city office. In order to make these name suggestions known to the citizens and to provide the municipal council with a picture of the mood for the proposed names, an online survey was created and made available for voting in the period from 12 August to 4 September 2025.

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