Using in-memory XML OSM Java object instead of OSM from file path

[MrAndre]

Currently I am trying to see if graphhopper has a way to read a XML OSM in-memory (Java String or something like that) instead of using a file path. Want to host the OSM file in a AWS S3 bucket in which case I can’t provide a path but only a Java object

[karussell]

This is currently not possible. There was a community member who shared some code some years ago:

Readonly DataAccess for InputStreams instead of Files

For our routing runtime we wanted to load the graph data from an URL / Inputstream rather than file. (Graph data was on external server and boot time already long enough). I want to share the implementation with you, maybe it is of interest for others. It also uses off-heap storage via lxarray but you can combine it with other storage techniques, of course: https://gist.github.com/jtheuer/a709ef97aad4eb63bc87c57744cccc19 It is a bit reverse-engineered to remove the random access logic but work…

https://gist.github.com/jtheuer/a709ef97aad4eb63bc87c57744cccc19

[easbar]

This is not supported currently but should be possible with only a few changes. Basically you just need to replace this code:

graphhopper/graphhopper/blob/47d3d3482346be50326999c6604d7c2c717f885f/core/src/main/java/com/graphhopper/reader/osm/WaySegmentParser.java#L392-L403

where the file is read and the different ReaderElement objects are passed to ReaderElementHandler with some code that reads your in-memory XML, creates these objects and passes them to the handler.