![]() The entity waysegments is able to store tags as key-value-pairs. The base model is easy to expand if storage of additional data is needed. Both entities store an array of access types (in case of waysegments for each direction) representing the allowed usage for different vehicle types. The entity waysegment_connections stores directed data for each connection between two joined segments. In PostgreSQL the entity waysegments stores data of graph segments (the linestring between two crossings) in a directed way, the segment entries itself are not directed. The base network model represents a directed graph consisting of waysegments and their connections. By default, Graphium uses PostgreSQL, but because of the interchangable database tier other DBMS could be used, too. The publishing of graph versions will be done on central Graphium server's side and guarantees a consistent state over all subscribers of one view.įor data management transport graph data has to be persisted. On worker machines clients - so called satellite Graphium servers - can deployed and subscribe on the central Graphium server for one or more specific views on graph versions. ![]() With Graphium it is possible to define one central Graphium server for administration of used graph versions. If data processing based on graph data has to be parallalized using a number of machines, graph data has to be distributed and persisted on them. Graphium is designed for use in distributed systems. Publish transport graphs to other servers Hence it is possible to import the whole data of a graph and extract only way segment used by car or by bike using views. This approach is similar to database views. One major design decision was to keep one (or more) graph version(s) including all kind of data needed and set up various views for data only needed for special use cases. This feature makes it possible to process data for real-time tasks as well as historic data processing. Graphium can import and manage several time restricted versions of one graph. Transport networks and their abstract mapping into digital transport graphs evolve over time. You can also enhance transport graphs and handle additional information. Uniform and expandable data model to fulfill specific use casesĪfter you have imported the transport graphs, you can access and process the data through its uniform data model. ![]() The Extended Information data model allows to import additional information to the basic transport graph. The transport graph data is imported into the Graphium server using the JSON file. Currently there are converters for OpenStreetMap and GIP (Graph Integration Platform - a joint, nationwide transport graph of Austria) available. Either use an existing converter or implement an custom one to convert transport graph data into a JSON file. Using those transport graph data is easy with Graphium. There are several providers of transport graph data. Features Import transport graphs from different sources Graphium is designed for deployment in distributed systems for centralized management and publishing to several servers. With the REST-API imports and management is easy. Graph data can be stored from several data providers. Io.Graphium is an Open Source project to store, manage and version transport graphs. ![]() :eclipse-collectionsĮclipse Public License 1.0 ( ) NOASSERTIONĬom.typesafe.akka:akka-distributed-data_2.12 GNU Lesser General Public License v3.0 only ( ) Jakarta.activation:jakarta.activation-apiĬom.:jackson-module-jaxb-annotations :jakarta.injectĬom.:jqassistant-commandline-distribution GNU General Public License v2.0 w/Classpath exception ( ) Eclipse Public License 2.0 ( ) Io.prometheus:simpleclient_tracer_otel_agent :scala-parser-combinators_2.12Ĭommon Development and Distribution License 1.1 ( ) GNU General Public License v2.0 w/Classpath exception ( )Įclipse Public License 1.0 ( ) Apache License 2.0 ( ) GNU Lesser General Public License v2.1 only () ( ) Apache License 2.0 ( )Įclipse Public License 2.0 ( ) GNU General Public License v2.0 w/Classpath exception ( ) :scala-java8-compat_2.12īSD 3-Clause "New" or "Revised" License ( )Ĭom.:jackson-jaxrs-json-providerīSD 3-Clause "New" or "Revised" License ( ) Apache License 2.0 ( ) Eclipse Public License 1.0 ( )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |