Feeds integration: add a mapping target for geofield

Created on 14 March 2018, almost 7 years ago
Updated 21 June 2024, 6 months ago

Need feeds support for D8.5
Could anyone familiar with these two module make a patch/ or patches?Or would MegaChriz you please make this possible?
I am constructing a site with info of a big bulk of locations and need to import those lat/lon data to their nodes and terms.
Sincerely wish you guys will offer support to solve this since I am not coder but only a builder.
Many thanks.

✨ Feature request
Status

Closed: outdated

Version

1.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom robcarr Perthshire, Scotland

    I'm seeing exactly the same problem as reported by @Problue Solutions in #22, and do not understand the proposal in #23, specifically:

    if you are importing Geometries use just the geometry property in the mapping (and leave unset the Lat and Lon selects).

    I have source values in JSON for latitude and longitude, which can be Feeds mapped to location > Centroid latitude and location > Centroid longitude. I've set the default value (with Feeds Tamper) for location > Geometry to null as I'm only importing point locations.

    However, when running a feeds import (as reported in #22) the import fails stating that:

    ...failed to validate with the following errors:
    location (location): location: this field cannot hold more than 1 values.

    So the import will only work if the Geofield field storage is set to a multivalue.

    Feels related to the way this thread evolved, but should a fresh issue be raised? (I'm probably answering my own question here)

  • 🇬🇧United Kingdom problue solutions Northern Ireland

    @robcarr - in the end I just left the field as multivalue and wrote a custom Feeds pre-validate event susbscriber and removed the field items greater than 0 (removing the unwanted 3 instances of the field and leaving the single correct instance). It's a workaround but my import now works fine.

  • 🇬🇧United Kingdom robcarr Perthshire, Scotland

    @Problue Solutions - I think I've addressed point geometry imports at #3381048-4: Unable to Import via Feeds → .

    Documentation or UI could be a bit clearer, but it does work if you know how to use the mappings. Geofield import will work with Feeds for single points if the 'Geometry' value is left to 'Select a source' in the Feeds mappings, and the lat/long values are mapped correctly.

  • 🇮🇹Italy itamair

    In new release 8.x-1.55 specific Instructions added in the Geofield Feeds Target Summary on how to either use ONLY Centroid
    Latitude & Centroid Longitude in case of Lat/Lon coupled values OR ONLY Geometry in case of WKT or GeoJson format.
    Don't use both ...

  • 🇺🇸United States bogdog400

    I'm running into the same problem with feeds and getting an error claiming that the Geofield can't hold more than one value.

    The Latitude and Longitude are set to CSV columns correctly. And geometry is set to "Select a Source".

    I'm using Latitude and Longitude values of the form "39° 21' 21.5496" N" which is what comes out of Views Export in the old system. Is it possible that this text format isn't correct?

    Any suggestions?

    TIA

Production build 0.71.5 2024