WFS Straßen- und Wegenetz Hamburg
Dieser Wep Feature Service (WFS) stellt die Straßen und Wege Hamburgs mit verschiedenen Merkmalen zum Download bereit. Das Straßen- und Wegenetz wird in der Hamburger Straßeninformationsbank (HH-SIB) in einem Knoten-Kanten-Modell gehalten.
Zur genaueren Beschreibung der Daten und Datenverantwortung nutzen Sie bitte den Verweis zur Datensatzbeschreibung.
|
Citation proposal
. WFS Straßen- und Wegenetz Hamburg. Behörde für Verkehr und Mobilitätswende (BVM) https://gdk.gdi-de.org/geonetwork/srv/api/records/6D0C9998-D7A7-43A8-910E-1C61D7079A3D |
INSPIRE
Identification
- File identifier
- 6D0C9998-D7A7-43A8-910E-1C61D7079A3D XML
- Hierarchy level
- service Service
Online resource
Resource identifier
Encoding
Projection
Classification of data and services
Classification of data and services
- Service Type
- download
- Coupling Type
- Tight
Coupled resource
Coupled resource
Classification of data and services
- Service Type
- download
- Coupling Type
- Tight
Coupled resource
Coupled resource
Keywords
- UMTHES Thesaurus ( Theme )
-
- Geoinformation
- Raumbezogene Information
- Service Classification, version 1.0 ( Theme )
-
- infoFeatureAccessService
- Further legal basis
-
- Hamburgisches Geodateninfrastrukturgesetz (HmbGDIG)
Other keywords
- Keywords
-
- DTV
- HH-SIB
- HHSIB
- Straße
- Straßendaten
- Straßeninformationsbank
- Straßennetz
- Straßenzustand
- Tt-sib
- TTSIB
- Verkehr
- Verkehrsstärken
- Weg
- Wegedaten
- Wegenetz
- Zählstellen
- Zählstellenbereiche
- Zustandsdaten
Geographic coverage
N
S
E
W
Temporal reference
Temporal extent
Temporal extent
- Date ( Creation )
- 2017-01-13T13:33:16.597+01:00
- Date ( Revision )
- 2019-12-17T00:00:00.000+01:00
Quality and validity
Conformity
Conformity
Conformity
Conformity
Conformity
Conformity
- Explanation
- see the referenced specification
Restrictions on access and use
Restrictions on access and use
- Access constraints
- Datenlizenz Deutschland Namensnennung 2.0
- Access constraints
- Quellenvermerk: Freie und Hansestadt Hamburg, Behörde für Wirtschaft, Verkehr und Innovation
- Access constraints
- {"id":"dl-by-de/2.0","name":"Datenlizenz Deutschland Namensnennung 2.0","url":"https://www.govdata.de/dl-de/by-2-0","quelle":"Freie und Hansestadt Hamburg, Behörde für Wirtschaft, Verkehr und Innovation"}
Responsible organization (s)
Contact for the resource
- Organisation name
- Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg
- udp-hilfe@gv.hamburg.de
- Organisation name
- Behörde für Verkehr und Mobilitätswende (BVM)
- hmdk-bvm@bvm.hamburg.de
Responsible organization (s)
Contact for the resource
- Organisation name
- Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg
- udp-hilfe@gv.hamburg.de
- Organisation name
- Behörde für Verkehr und Mobilitätswende (BVM)
- hmdk-bvm@bvm.hamburg.de
Metadata information
Contact for the metadata
- Organisation name
- Landesbetrieb Geoinformation und Vermessung (LGV) Hamburg
- udp-hilfe@gv.hamburg.de
- Date stamp
- 2023-08-10
- Metadata language
- German
SDS
Conformance class 1: invocable
- Pass
- false
Access Point URL
Endpoint URL
Technical specification
- Date
- Explanation
- see the referenced specification
Conformance class 2: interoperable
Coordinate reference system
Quality of Service
Access constraints
- Access constraints
- otherRestrictions Other restrictions
Limitation
Use constraints
Limitation
- string
- Datenlizenz Deutschland Namensnennung 2.0
- string
- Quellenvermerk: Freie und Hansestadt Hamburg, Behörde für Wirtschaft, Verkehr und Innovation
- string
- {"id":"dl-by-de/2.0","name":"Datenlizenz Deutschland Namensnennung 2.0","url":"https://www.govdata.de/dl-de/by-2-0","quelle":"Freie und Hansestadt Hamburg, Behörde für Wirtschaft, Verkehr und Innovation"}
Responsible custodian
Contact for the resource
Conformance class 3: harmonized
Contains Operations
- Operation Name
- DescribeFeatureType
- Distributed Computing Platforms
- HTTPGet
- Invocation Name
- DescribeFeatureType
Parameter
- Name
- OUTPUTFORMAT
- Description
- The output format to use to describe feature types. text/xml; subtype=gml/3.1.1 must be supported. Other output formats, such as DTD are possible
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- REQUEST=DescribeFeatureType
- Description
- Name of request
- Optionality
- 0
- Repeatability
- false
- Name
Parameter
- Name
- TYPENAME
- Description
- A comma separated list of feature types to describe. If no value is specified that is to be interpreted as all feature types
- Optionality
- 1
- Repeatability
- false
- Name
Contains Operations
- Operation Name
- GetFeature
- Distributed Computing Platforms
- HTTPGet
- Distributed Computing Platforms
- HTTPPost
- Invocation Name
- GetFeature
Parameter
- Name
- resultType=Results
- Description
- The default value results indicates that a web feature service should generate a complete response that contains all the features that satisfy the request. The exact structure of the response is defined in clause 9.3
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- outputFormat=GML2
- Description
- This value is kept for backward compatability and indicates that an XML instance document must be generated that validates against a GML2 application schema
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- outputFormat=text/xml; subtype=gml/2.1.2
- Description
- Same as GML2
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- outputFormat=text/xml; subtype=gml/3.1.1; subtype=gml/2.1.2
- Description
- This value indicates that an XML instance document must be generated that validates against a GML3 application schema. This is the default values of the outputFormat attribute if the attribute is not specified in the GetFeature request
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- resultType=Hits
- Description
- The value hits indicates that a web feature service should process the GetFeature request and rather than return the entire result set, it should simply indicate the number of feature instance of the requested feature type(s) that satisfy the request. That is that the count should only include instances of feature types specified in the typeName attribute (i.e. GetFeature/Query/@typeName ). The exact way in which the feature count is conveyed to a client application is described in clause 9.3
- Optionality
- 1
- Repeatability
- false
- Name
Contains Operations
- Operation Name
- GetCapabilities
- Distributed Computing Platforms
- HTTPGet
- Invocation Name
- GetCapabilities
Parameter
- Name
- SERVICE=WFS
- Description
- Service type
- Optionality
- 0
- Repeatability
- false
- Name
Parameter
- Name
- UPDATESEQUENCE=string
- Description
- Sequence number or string for cache control
- Optionality
- 1
- Repeatability
- false
- Name
Parameter
- Name
- REQUEST=GetCapabilities
- Description
- Name of request
- Optionality
- 0
- Repeatability
- false
- Name
Parameter
- Name
- VERSION=version
- Description
- Request version
- Optionality
- 1
- Repeatability
- false
- Name
Overviews
Provided by
Views
6D0C9998-D7A7-43A8-910E-1C61D7079A3D
Access to the portal
Read here the full details and access to the data.
Associated resources
Not available