I'm more looking for a "custom parser" than I am for "do this based on X tag". Basically, I'd like to see an interface (or an abstract class) that we can implement to precisely [and performantly] parse data as we wish. That said, the code in this case is relatively simple & we've "reverse-engineered" it enough to see how it works and can write our own code/parsing. It would be much nicer if it was an abstract or interface implementation for parsing though -- and definitely, include the default [concrete] implementations (ie the ones that are there as standard now). Basically, instead of using compiler defines for "EasyRoads 3D" etc -- make a single "parser" abstract class [or interface], and then implement that twice (once for LineRenderer & once for EasyRoads3D) for the product you ship. That then allows more advanced customers, like us, to write our own parser without having to get into your code and cause issues when attempting to upgrade / merge with the "upstream". For instance, we're writing our road parsing to take in JSON [data from OSM's Overpass-Turbo API, with output format = JSON], and then to use a high-performance rendering method to display [tens of thousands of] roads -- just as one example. Another question -- and, like before, I admit that I haven't investigated too far yet, so apologies in advance! Is there a way for us to use your library to ingest arbitrary spatial GeoTiff data and then use your tool to query against that GeoTiff for the values at a Lat/Lon coordinate? Context / Example We have a server-side system that lets us make an HTTP request with geo-bounds & then our server spits back either 1 GeoTiff with ~10 different bands of data [ideal], or it can optionally spit back multiple GeoTiffs [one for each data-set -- less ideal]. Our data-sets are essentially totally "arbitrary" -- along the lines of "risk of lightning-strike [at position]", they're just encoded as GeoTiff, including the appropriate meta-data for projection, bounds, etc... Server side is just using GDAL under the hood, it's a small server that queries against a bigger data-set and then uses GDAL to 'crop' the requested data and passes it back. Again, the data is 'arbitrary' / application-specific; the bounds are generally the same [or close] to the terrain that we import via your tool, the key thing is we'd like to be able to query like so: var tif = data.Import(local_path_to_geotif); // already in StreamingAssets dir float valueAtPosition = tif.Query(int GeotiffBandID, Vector2Double LatLon); Summarized Question: Is there a utility method/way to use your asset that would allow us to ingest 'arbitrary' data, similar to what's in the example pseudo-code above -- so that we can sample a Geotif's band at a given geo-coordinate (Lat/Lon)? If so, can you guide me towards what API method(s) I should be looking at, please? =D Ty!!