Documentation across OpenLayers and geo modules in general are recommending using CCK fields of type float for long/lat input. However OLG (openlayers_geocoder) only support CCK textfield in autocomplete.

By using float field
- we get float validation for free
- more conformance to other recommendation in cases when user decided to start/stop using OLG, they don't need to create/remove new fields, risk losing their existing geo data.

This is more like an additional new feature, if enabled
- we can further extend OLG to reverse mapping using those fields, i.e. set marker on map using values input into CCK long/lat float fields

Come across this when I was testing alternative geo implementations. When start/stop using OLG, long/lat fields type have to be changed (for autocomplete) which will have deep impact on existing user geo data. With other geo combination float fields just work across the system.

Marked critical as unaware user might lose their data accidentally.

Comments

steinmb’s picture

steinmb commented
Priority: Critical » Normal

Hi
No feature req. are critical, back to normal. You have a valid point in supporting float fields. Bumping this issue and will revisit it when I start looking into revers geo-lookup and why it never happened.