Closed (fixed)
Project:
Openlayers
Version:
6.x-1.x-dev
Component:
OpenLayers Layers
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Nov 2009 at 20:56 UTC
Updated:
24 Feb 2010 at 02:00 UTC
I have not found any documentation on the setup or usage of OpenLayers 1.x so I'm at a loss for what may be causing my issue.
I have several nodes of type "Bus Stop" which require a map. I also have Geo and Postal installed. The "Bus Stop" content type has a CCK field for the geocoded location which gets it's input from a CCK address field using the Postal widget. I have created dozens of "Bus Stop" nodes and entered their addresses accordingly.
(Honestly, I would have liked to input the data using a map rather than Postal (since bus stops don't have addresses), but I couldn't figure out that setup either.)
After installing OpenLayers, I went to the Presets tab to add a new one that would work according to my needs. I left everything at defaults, but in the "Layers" fieldgroup under "Overlay Layers" I checked the box next to "Geo Table (content_type_busstop)". When I click "Save" I get the following error message:
user warning: Table 'mydrupaldb.mysitename_mysitename_content_type_busstop' doesn't exist query: SELECT asText(field_busstop_codedlocation_geo) as field_busstop_codedlocation_geo, vid,nid,field_stopnumber_value,field_schedule_nid,field_busstop_address_type,field_busstop_address_name,field_busstop_address_street1,field_busstop_address_street2,field_busstop_address_zip,field_busstop_address_city,field_busstop_address_state,field_busstop_address_country from mysitename_mysitename_content_type_busstop in /var/www/html/sites/all/modules/openlayers/modules/openlayers_layers/includes/openlayers_layers.layers.inc on line 359.
Any idea what is happening here?
Comments
Comment #1
phayes commentedIt sounds to me that geo has changed it's API, and that we need to update openlayers to reflect this. That aside, I think you are going about this the wrong way.
I would recommend the following configuration and modules:
1. For collecting and storing data use the Location CCK module(http://drupal.org/project/location), since it sounds like you will only be storing points in latitude and longitude. You can set-up locations cck so that it is collecting lat/lon, not an address.
2. To generate a map create a preset how you want it, then use views with the openlayers_views module to create a map of your points.
Comment #2
zzolo commentedChanging name and type of message. It's not something worth putting so much time into, but since it's already there.
Comment #3
zzolo commentedIs this a feature we want to keep in? I am just feeling lazy about trying to figure out the Geo API, especially when it is still in alpha.
Comment #4
phayes commentedI'd be happy to remove this from openlayers and release it as a standalone module.
Comment #5
zzolo commentedSo, the next question might be: do we want to remove Geo integration out of this module all together and move towards an openlayers_geo module?
I lean towards yes, but I am just throwing out the question. I think the only real technical challenge would be to abstract our Views data inputs so that they are pluggable.
This also might be a better discussion for the Development 2.x thread.
Comment #6
tmcw commentedI'm happy to remove Geo integration entirely from 2.x, and possibly move it to another module. Until the geo module provides a stable API, it's a timesink for other modules to keep changing with it.
Comment #7
zzolo commentedMoving Geo integration discussion to #569178: Development 6-2.x
Putting on hold until that is resolved.
Comment #8
phayes commentedOkay. I've rolled layers-from-tables into a new modules that also handles geo tables. http://drupal.org/project/spatial
So no need for this functionality inside openlayers anymore. Marking as needs work as someone needs to actually remove it. :-)
Comment #9
phayes commentedChanging name to reflect job.
Comment #10
phayes commentedhttp://drupal.org/cvs?commit=326612