There is discussion in a thread on using geographical objects as properties with PostGIS on GitHub. This issue might be helpful.

Graph data is usually entered around edges on nodes like you mentioned. Now a more detailed look into the data is required but typically geographical data is not easily expressed by just edges and nodes.

Since geographical data has elements that are numerical, and verbose you might be better off using a NoSQL database instead.

Apache-age is primarily designed to save graph data in the form of edges and nodes. While it is possible to store some basic geographical information as properties of nodes and edges, it may not be the most efficient or flexible option for storing complex geographical data. it may be worth considering another extension like PostGIS or consider using MongoDB. These databases provide specialized data structures and indexing techniques that can make it easier to store and query geographical data.

However, if you only need to store simple geographical data alongside your graph data, Apache AGE may be sufficient for your needs.

References:

• http://postgis.net/
• https://www.mongodb.com/docs/manual/geospatial-queries/
• https://www.sqlshack.com/getting-started-with-spatial-data-in-postgresql/

The main function of Apache-age is to store edges and nodes in graphs. However, to save certain fundamental geographic data, it can be used. It might be preferable to think about an alternate extension, such as PostGIS, MongoDB, etc., which offer specialized strategies that can make it simpler to store and access geographic data. There is a discussion on GitHub issues that might prove to be useful to you in order to find the answer to the specific problem you are looking for, refer to this issue.

At the moment, Apache AGE is not efficient to store Geographical Information because of the complex structure of the data involved.

PostGIS would do this conveniently.

As per this issue, POSTGIS is not supported by AGE