In the wrf-fire datasets I've worked with, the FXLONG and FXLAT coordinate variables contain 0's at the spatial domain's boundary. Since they also have no _FillValue attribute, some post-processing software package like Vapor have trouble reading the contained 2D variables.
Is there a good place that I can make a feature request to change this? I don't know if there may be a good reason to keep it.
Example `ncdump -v FXLAT` on wrf-fire output:
...
40.19511, 40.19512, 40.19511, 40.19511, 40.19511, 40.19511, 40.19511,
40.19511, 40.19511, 40.19511, 40.19511, 40.19511, 40.19511, 40.1951,
40.1951, 40.1951, 40.1951, 40.1951, 40.19509, 40.19509, 40.19509,
40.19508, 0, _, _, _, _,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...
Is there a good place that I can make a feature request to change this? I don't know if there may be a good reason to keep it.
Example `ncdump -v FXLAT` on wrf-fire output:
...
40.19511, 40.19512, 40.19511, 40.19511, 40.19511, 40.19511, 40.19511,
40.19511, 40.19511, 40.19511, 40.19511, 40.19511, 40.19511, 40.1951,
40.1951, 40.1951, 40.1951, 40.1951, 40.19509, 40.19509, 40.19509,
40.19508, 0, _, _, _, _,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
...