- Issue created by @kthull
- 🇺🇸United States apmsooner
I've looked into replicating what the Geofield module https://www.drupal.org/project/geofield → is doing and it would just be way too heavy of a lift to handle this in custom_field. This particular need makes much better sense to just split out as its own field. If these fields should go together as a multi-valued component or you just want them structured together for API reasons, I would still use a paragraph here as an entity wrapper that contains both fields, otherwise just split them out as separate single values on the node or whatever parent entity type the fields are attached to.
- 🇺🇸United States kthull Fort Wayne, Indiana
Yeah, I'm doing a post-import event as well as an entity presave hook to gather all the individual NSEW coordinates from the custom field into a single WKT formatted geofield on the node, but that a) felt hacky, and b) has some minor drawbacks to having a geofield per multi-value custom field delta.
I thought it might be a big ask, so thanks for the feedback.