Maybe some quite specific parsers within src/Parser could be moved as plugins. I'm thinking about GDFParser, GTXParser and ISGParser. These parsers were added to support some format for geoid grid data.
Similarly, TIFFParser which is already within examples/js/plugins could be included in src/Parser.
Motivation
Geoid data parsers offer the support for some very niche formats. Moreover, I did not find a standard for geoid grid data. I don't have any clue about how users use the GeoidLayer but it is likely they use a different format from those we developed a parser for.
However, I think TIFF is a more broadly used format and its place within src/Parser is more justified than geoid formats parsers.
Discussion
I might miss some info about usage of geoid within iTowns, and this post relates to my humble opinion, so the subject is highly opened to discussion.
Context
Maybe some quite specific parsers within
src/Parsercould be moved as plugins. I'm thinking aboutGDFParser,GTXParserandISGParser. These parsers were added to support some format for geoid grid data.Similarly,
TIFFParserwhich is already withinexamples/js/pluginscould be included insrc/Parser.Motivation
Geoid data parsers offer the support for some very niche formats. Moreover, I did not find a standard for geoid grid data. I don't have any clue about how users use the
GeoidLayerbut it is likely they use a different format from those we developed a parser for.However, I think
TIFFis a more broadly used format and its place withinsrc/Parseris more justified than geoid formats parsers.Discussion
I might miss some info about usage of geoid within iTowns, and this post relates to my humble opinion, so the subject is highly opened to discussion.