Open nicklally opened 7 years ago
Ok, here's the beginnings of a proposal:
Have project data files be specified in a type of GraphML. You should be able to load/import/save files of the following format.
The nodes in the GraphML file are anchor points for the mesh within particular images. Node data:
id
: arbitraryimage
: this is a string, likely a URI of some sort, that specifies the location of the image file x
: x
coordinate in the non-transformed coordinate system associated with the file (if the file is a GeoTIFF, then, perhaps, longitude)y
: similar but different to x
Edges in the GraphML file are known distances between nodes.
id
: arbitrarysource_image
: URI of image corresponding to the source node.target_image
: URI of image corresponding to the target node. When source_image
is equal to target_image
, you're looking at an intra-image connection.source
: id
of a particular node in the source_image
where the distance
of the edge is measured from.target
: id
of a particular node in the target_image
where the distance
of the edge is measured to. distance
: distance between nodes. likely a number.distance_type
: can be defined to indicate more than one possible type of distance/units stored within a given file. Note that upon encountering such a file, the loader would need to import the images specified in the various nodes.
Here's a parser that we might be able to use to do the file IO: https://www.npmjs.com/package/graphml-js
So some of this is in process in the dos-exploring branch, although not the embedding of images in the node and edge information, or the potential for multiple images to be thereby linked.
Ie: Geocoded csv files or other formats.