-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a sample configuartion for import .osm files to OrientDB via ETL . #7107
Comments
Hey @saeedtabrizi do you have a example of a XML snippet for OSM and how you want to import it in OrientDB? |
Hi @lvca . I tried multiple ways to handle my xml OSM data to OrientDB by using ETL but it so complicated and hard in my case . I think the ETL feature has lack of documentation and current documentation does not have true guides or best practices . (TD;LR ETL must be add some facilities and documentation and best practice for ETL at the future) . Anyway i put my ETL json files here that i have success transform data from .osm to OrientDB but it is not my favor ETL process . ETL Process for OSM Data .
For each This issue can be closed . |
@saeedtabrizi thanks for the JSON files, it could be useful to some users. If you can create something generic, we would more than happy to include it in the GeoSpatial module and maybe also in Studio! |
@lvca with the pleasure . i handle it asap . (may be in this week) |
Hi
I need a sample for ETL configuration to importing OSM data to OrientDB .
In my case , i'm using spatial module in orientdb and i need to store the node , ways , tags as Vertex and relationship as the Edge or something like this . i want to define the data version field and using data version in the runtime query too . after all i want to use routing functions like the astar function to find cheapest way (i don't like to use postgis routing) so i want to calculate the distance between node when ETL transfortms data .
i read ETL XML but i confused exactly .
i need help or more documentation to solve my problem .
Thanks
The text was updated successfully, but these errors were encountered: