I discovered this through using out center, which produces object without coordinates but also produces separate Feature items from the center point; I think this is a red herring and this is only caused by the missing coordinates but I mention it for completeness. (Difficult to make a nice reproduction.)
(As a workaround, I can, of course, remember to instead use out center tags; in my overpass queries.)
1: A way that has references to nodes which lack coordinates: way(387635995);out;node(w);out ids;
I believe in both of these cases the geometry should either be tainted (if some geometry is present) or null (if no geometry is present), in which case I believe the library will simply discard the feature; it's valid GeoJSON to have a null geometry but I don't think this library does that.
I discovered this through using
out center
, which produces object without coordinates but also produces separate Feature items from the center point; I think this is a red herring and this is only caused by the missing coordinates but I mention it for completeness. (Difficult to make a nice reproduction.)(As a workaround, I can, of course, remember to instead use
out center tags;
in my overpass queries.)1: A way that has references to nodes which lack coordinates:
way(387635995);out;node(w);out ids;
Input:
Output:
2: A relation that has references to ways which lack coordinates:
rel(544634);out;way(r);out;
Input:
Output:
I believe in both of these cases the geometry should either be tainted (if some geometry is present) or null (if no geometry is present), in which case I believe the library will simply discard the feature; it's valid GeoJSON to have a null geometry but I don't think this library does that.