Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Activities are being run regarding the implementation of File, GPX, KML and Geojson providers, already implemented in the last weeks in the 2.x branch ...
Comment | File | Size | Author |
---|---|---|---|
#3 | geocoder_file_gpx_kml_geojson_into_3_x_branch_3024207-3.patch | 55.04 KB | itamair |
Comments
Comment #2
itamair CreditAttribution: itamair as a volunteer commentedComment #3
itamair CreditAttribution: itamair as a volunteer commentedThe attached patch accomplishes this issue task, both on the widgets and formatters sides, for file, gpx, kml and geojson plugin types providers.
Gpx, kml and geojson plugin geocode operations rely upon the geofield.geophp service, and will return a \Geometry (not just POINT but also Linestring, Multilinestring, Polygon, Multipolygon), instead of a \Geocoder\Model\AddressCollection.
That's why some object interfaces and geocode\doGeocode methods definitions have been adapted and un-restricted accordingly (to both return \Geocoder\Model\AddressCollection or \Geometry, or NULL).
All these amends don't interfere with, and don't introduce regressions to, lastly added enhancements to 8.x-3.x-dev branch (such as Convert providers from simple config to a config entity ...),
and have been widely and succesfully tested with real Geocoding use cases of incremental complexity.
Exceptions handlings have been setup and implemented in the code.
This is being set to "Needs review" ... and will be committed into dev if any downside arises from some contributor review.
Comment #4
itamair CreditAttribution: itamair as a volunteer commentedComment #6
itamair CreditAttribution: itamair as a volunteer commented