You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The feature_update_warnings channel (added in #53) currently only carries the NetworkLink message. The importer silently drops several other non-fatal things:
invalid individual placemarks (currently collected into @errors, which raises unless skip_invalid)
blank / zero-geometry features (blank_feature?, geom blank)
GDAL field-width truncations (e.g. Value … of field Shape_Area … not successfully written)
Proposal: route these non-fatal skips through the same warnings channel so a partial import reports what didn't import and why — not just NetworkLinks. This turns the warning surface into a general "here's what was skipped" report, which is what an uploader actually wants.
Related: consider storing warnings as typed/structured data ({type:, file:, payload:}) instead of pre-formatted strings. That would:
The
feature_update_warningschannel (added in #53) currently only carries the NetworkLink message. The importer silently drops several other non-fatal things:@errors, which raises unlessskip_invalid)blank_feature?, geom blank)Value … of field Shape_Area … not successfully written)Proposal: route these non-fatal skips through the same
warningschannel so a partial import reports what didn't import and why — not just NetworkLinks. This turns the warning surface into a general "here's what was skipped" report, which is what an uploader actually wants.Related: consider storing warnings as typed/structured data (
{type:, file:, payload:}) instead of pre-formatted strings. That would:Larger change than #54; prioritize independently.
🤖 Generated with Claude Code