seed icon indicating copy to clipboard operation
seed copied to clipboard

Property footprint does not import from GeoJSON

Open nllong opened this issue 2 years ago • 10 comments

Describe the bug

The polygon isn't importing as 'property_footprint' when there is a polygon in a geojson file.

Expected Behavior

There should be an entry in the mapping page for one to map the footprint. If mapped to the canonical field of property_footprint then it should show up in the inventory.

Actual Behavior

Doesn't show any mapping options

Steps to Reproduce

Attached to this ticket is a GeoJSON file

  • import as GeoJSON (unzip the attached file)
  • Verify that there is no "property_footprint" in the mapping page
  • This results in no footpring

Instance Information

local

Additional Context

ubid_subselection.geojson.zip

nllong avatar Feb 12 '23 23:02 nllong

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Apr 14 '23 01:04 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jul 12 '23 02:07 github-actions[bot]

still an issue and a complete mystery :)

nllong avatar Jul 12 '23 20:07 nllong

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Sep 11 '23 01:09 github-actions[bot]

Still an issue

nllong avatar Sep 11 '23 03:09 nllong

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Nov 11 '23 01:11 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jan 17 '24 01:01 github-actions[bot]

@nllong -- is this issue fixed?

RDmitchell avatar Jan 17 '24 03:01 RDmitchell

no, still not fixed.

nllong avatar Jan 27 '24 17:01 nllong

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Mar 28 '24 01:03 github-actions[bot]