Export: geoJSON format: allow user to specify field to use as the building footprint coordinate data rather than defaulting to UBID bounding box coordinates

[RDmitchell]

Instance: staging
SHA: b264666

The main issue is that when a property has a UBID associated with it, SEED automatically generates polygon coordinates that define the bounding box of the UBID.

When this property is then exported as a geoJSON file, that bounding box is what is defined in the geoJSON file as the building footprint coordinates.

In this case (see the doc below) and probably in others, the user has the actual building footprint data, showing the real geometry of the building, that they want to be exported in the geoJSON file INSTEAD of the UBID bounding box.

So it seems, if I am understanding correctly how the geoJSON export is working, that SEED should have a place, probably in Organization / Settings, where the user can specify the field that defines the polygon geometry when a property is exported as a geoJSON file.

See this doc for the specific details from this user. I don't know the code but have interpreted what SEEED is doing based on testing and experimentation. There may be other things going on that I don't understand.

https://docs.google.com/document/d/1mInNbkebl78xQ5Zno-2IsucT6S8zr09aiTLpPaSWoDs/edit?usp=sharing

[kflemin]

@RDmitchell With the new geojson fixes that Ross made, GeoJSON exports will now contain both UBID bouding box information AND property footprint if they both exist in the data. (We are exporting everything, but not allowing user to select what will be in the coordinates geometry).

All of these fields show up in the geometry section:
polygon_fields = ["bounding_box", "centroid", "property_footprint", "taxlot_footprint", "long_lat"]

[RDmitchell]

@kflemin -- thanks. I will pass this info along to Maryland.

[RDmitchell]

@kflemin -- is this on staging for testing?

[RDmitchell]

see #5099