Please help.
I enabled the mappingkit location fields on a custom nodetype. When I create the node I can see the longitude latitude fields and I enter values. My problems are:
1. When I view the node (view mode) the location fields are not there.
2. When I create a view I can't see the fields to include them in the view columns.
3. When I add a feed display and read the feed I can't see the fields
4. When I try to import data of my node type from a cvs file I can't see the location fields on the field mapping screen of Node_import
Note: Surprisingly I'm able to see the location fields on a user/feed.
How do i enable mappingkit location fields for my custom nodetype?
Does mapping kit require location module?
I appreciate the help.
Comments
Comment #1
jpulles CreditAttribution: jpulles commentedHi chalee,
So far the location of a node wasn't visible when viewing; it was only used to add a position to that node in a rss feed. You would see that position when looking 'inside' the RSS feed as a <georss:point> element.
The dev release now does the following:
- it shows location in the node view (and thus also in the rss view)
- it shows the x/y/srid fields when making a view
- it should work with node_import
Note that the integrating with views is still limited. Adding the x/y/srid fields to a feed view does not give you a georss:point element which is needed for a location.
Comment #2
chalee CreditAttribution: chalee commentedThanks for your reply jpulles. I installed the dev release of Mapping Kit and it solved the first 3 issues except for the 4th one which is importing using node_import.
1. I still can't see the mapping fields (Lat/lon) in the node_import wizzard. Is there something I have to do to see the fileds. I have thousands of node records I have to import from a CVS file.
2. On a separate note what does it take to have a mappingkit style that one can select in a view like we have for nicemap module. That feature is cool. It makes showing node markers on a map quick and easy, especially when you want to show makers for nodes returned by a Faceted Search module.
Thanks.
Comment #3
VeeLin CreditAttribution: VeeLin commentedsubscribing - equivalent feature request in Node Import: http://drupal.org/node/483210
I have a few thousand nodes I'd like to import as well. I have the same issue where I can not map the csv file to the mapping kit lat/long fields from the node import wizard. Any advice greatly appreciated.
V
Comment #4
chalee CreditAttribution: chalee commentedHi Veelin,
While we wait for this feature here is a work around that worked for me. I installed and enabled both the mappingkit and location modules. In the 'content type' Edit page you will see sections for both mappingkit and location. Disable the MappingKit there and leave/configure the coordinate fields for the location section. The effect of this is you will be able to see these lat/lon fields in your node import and Mappingkit will also be able to use them. My website is working well with this setup andhope this will work for you
--
Chalee
Comment #5
VeeLin CreditAttribution: VeeLin commentedSo what you are saying is that mapping kit will use the lat/long brought in by location? Or do you somehow have to translate after import? In other words how does mapping kit use the fields? Automatically or manually?
Thanks,
V
Comment #6
chalee CreditAttribution: chalee commentedVeeLin
Yes the mapping kit will use the lat/long brought in by location. And this will be automatic.
Chalee
Comment #7
chalee CreditAttribution: chalee commented