I'm working on an engineering router for my site and I used your blueprint JSON to map between engineers and blueprints. One issue I've discovered is that at least some of the Coriolis GUID don't match up.
That blueprint is for Wake Scanner (Fast Scanner) and the guids don't match up. Matching on blueprint names is also not helpful due to different names being used across different products (SLEF, Coriolis, ED Engineer, EDSY etc).
I was wondering how difficult it would be to add the Frontier name to blueprints.json (in the case above that would be Sensor_FastScan). That should be common (since it comes from frontier) and would allow greater interoperability between the various softwares interested in engineers.
I'm working on an engineering router for my site and I used your blueprint JSON to map between engineers and blueprints. One issue I've discovered is that at least some of the Coriolis GUID don't match up.
https://github.com/EDCD/coriolis-data/blob/a4f5d3fb8176b808618962aceda27efda8947df2/modifications/blueprints.json#L5967 https://github.com/msarilar/EDEngineer/blob/master/EDEngineer/Resources/Data/blueprints.json#L33650
That blueprint is for Wake Scanner (Fast Scanner) and the guids don't match up. Matching on blueprint names is also not helpful due to different names being used across different products (SLEF, Coriolis, ED Engineer, EDSY etc).
I was wondering how difficult it would be to add the Frontier name to blueprints.json (in the case above that would be Sensor_FastScan). That should be common (since it comes from frontier) and would allow greater interoperability between the various softwares interested in engineers.