Active
Project:
Layar
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Apr 2011 at 20:34 UTC
Updated:
18 Jul 2011 at 08:15 UTC
Jump to comment: Most recent file
Comments
Comment #1
c-c-m commentedAfter using this module for a while I think it wouldn't be that hard for a developer to do what I was asking. After all GMAP is not used at all to generate any content to Layar but to provide a user friendly way to obtain coordinates and location is only used to store them and then send them to layar. In fact, if I'm not wrong, it could be possible to use this module with no map at all on the website.
This can be achieved in many different ways, starting from typing longitude and latitude on two separate cck decimal fields or using a combination of Geo module and WKT field , so that's why I think the dependencies should be removed and compatibility with other ways of storing and displaying data should be considered (such as the already mentioned ones).
Hope you can reconsider this issue (I want to get rid of big and somewhat outdated modules like this two -as well as getting rid of Google's, Yahoo's... and other non opensource solutions ;) ). I would like to help you but unfortunately my programming skills are almost zero.
On the other hand I'd like you to thank you for this great and useful module. Good job!
Regards
Comment #2
juliusvaart commentedHi C-c-m,
I made a patch to provide for 3D objects and haven't had the time to make a release out of it. But i'm willing to check this out and include it.
In the meantime you can use this altered .info file where the location dependencies are removed.
Julius
Comment #3
c-c-m commentedThank you very much, StreamDesing.
Unfortunately it was not as easy as expected, since OpenLayers Geocoder stores data in WKT format, which means that both latitude and longitude are set in a singla field, and thus it's nos possible to use layar module with it (All nodes are placed at 0,0 in layar)
:(
EDIT:
I realized that WKT fields can populate other cck with several tokens, so I created two text fields, one for longitude and another one for latitude and it worked fine!
Comment #4
juliusvaart commentedYou should consider to post a request at the Open Layers module.
Comment #5
c-c-m commentedStreamDesign it seems that you wrote while I was editing my previous post ;)
I have some good news:
As I was saying when you were editing, I realized that WKT fields can populate other cck with several tokens, so I created two text fields, one for longitude and another one for latitude and it worked fine! (I can write a tutorial if you want)
Here the bad news.
After seeing that I had everything I needed I uninstalled all location and gmap modules and submodules, just to discover that layar didn't find any result. After some trial-error I discovered that layar can't get any POI if drupal's layar view doesn't have any location field, even though they are not used for obtaining coordinates. I guess it may have something to do with filter "Layar: Location latitude/longitude is within Layars requested Proximity "
Regards
Comment #6
juliusvaart commentedI checked the Proximity filter and it uses the Location Search module. Maybe this module can be an alternative: Open Layers Proximity?
Comment #7
c-c-m commentedIndeed, it works
Comment #8
juliusvaart commentedSo did you create Open Layars functionality? If so, we could make an upgrade for the module.
Comment #9
uniquename commentedDid you just replace the views filter from layar "Location latitude/longitude is within Layars requested Proximity" with the "Proximity: Great-circle" filter from openlayers_proximity?
I have no setup to test it, but this should be the idea, or?
Comment #10
juliusvaart commentedYou use the "Location latitude/longitude is within Layars requested Proximity", but you alter the plugin file that it uses the hooks from the Open Layer Proximity.
I'm a bit busy, so i won't be able to check it out.
Topic starter is using the location module for the proximity and open layers for the lat/lon.
Comment #11
c-c-m commentedI haven't read all the comments, but this conversation in the Location and Mapping Group might be helpful: http://groups.drupal.org/node/159584