You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2018. It is now read-only.
Is it possible to make OSM format is the wrapper extension of this tools?
So that we can create a wrapper for another type of JSON object coming from another source.
One of the interesting types is wiki data. I also have sets of data need to be properly linted using this tools, but converting Wikidata objects into a compatible osm object will be a bit of pain.
In my opinion,
Hanum should have a Generalized simple object schema. And then incompatible format with Hannum can easily be converted to Hannum's schema.
Not sure is a good thing though, let me know your thought.
The text was updated successfully, but these errors were encountered:
There is exists a package for OSM like this. But, it's an old one and I think that package wouldn't maintained anymore. I think the best way indeed to creates a generalization of the object data structure as a schema. Let me take a look on Wikidata object first. Any sample?
Is it possible to make OSM format is the wrapper extension of this tools?
So that we can create a wrapper for another type of JSON object coming from another source.
One of the interesting types is wiki data. I also have sets of data need to be properly linted using this tools, but converting Wikidata objects into a compatible osm object will be a bit of pain.
In my opinion,
Hanum should have a Generalized simple object schema. And then incompatible format with Hannum can easily be converted to Hannum's schema.
Not sure is a good thing though, let me know your thought.
The text was updated successfully, but these errors were encountered: