Mapping choices betw "standalone form" & "content type" differ
Shapefile (Geodata) feeds import to content/node failed with selection of a content type instead of "Use standalone form" in the importer's basic settings
Important configuration settings of the Feeds Importer:
"Attach to content type ": POI (not "Use standalone form")
Fetcher: File upload
Allowed file extensions: zip
Parser: Vector geodata parser (from PostGIS Module); Name for the geometry field: _geometry_; Name for the FeatureID field: _fid_
Processor: Node processor; Settings: Bundle: POI
Hello Drupal Community,
I would like to attach my importer to a content type by selecting "Attach to content type" in the importer's basic settings instead of using a standalone form. I tested my geodata (shapefile) importer with a standalone form and it works fine. With this configuration I'm able to choose lots of source fields and target fields as well to define which elements of a single item of a feed (= Sources) map to which content pieces in Drupal (= Targets).
But if I attach my importer to a content type by selecting "Attach to content type" in the importer's basic settings there are only two sources for selecting ("Feed node: Node ID and User ID"). I have no longer the possibility to define elements of a single item of a feed (= Sources).
After uploading a shapefile with an added node there is no map and the geospatial field is empty.
Can you explain the problem, please?
Best wishes,
Toni
Comment | File | Size | Author |
---|---|---|---|
missingmappingoptions.png | 96.15 KB | toni.mueller | |
mapping_opions_withUsestandaloneform.png | 102.8 KB | toni.mueller |
Comments
Comment #1
toni.mueller CreditAttribution: toni.mueller commentedThis feature or bug is associated with the Vector geodata parser (GDAL Module) because this problem occurs not with the CSV parser.