When using Geolocation Field module on one site, it's very confusing that it uses rare longitude abbreviation lng instead of lon in field values.

I researched most of other Drupal modules related to GPS coordinates (geofield, google_map_field, baidu_map, leaflet, etc), and all of them use lon abbreviation for store longitude value. Same abbreviation use most of other projects, not related to Drupal, too, you can simply compare count of results for "lat lon" and "lat lng" in any search engine.

So will be good to use most popular abbreviation in Geolocation Field module too, for, at least, make values looks same together with Geofield Drupal module, for not frustrate developers to remember that they must use another abbreviation only for geolocation fields.

If you want to keep using "lng" as main abbreviation, can you, please, describe your reasons? Thanks!

Comments

Murz created an issue. See original summary.

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented

Without changing database field name, that will require upgrade function with large migration procedures for each field, containing data, possible workaround for this problem can be adding wrappers, that accept "lon" data as value for "lng" field, and add "lon" value to field, so will work like aliases.

Other solution is make real Drupal computed field "lon", that will contain copy of "lng" value.

And make "Format of longitude field name: lng / lon" option in module settings, to configure the main storage name for field, without building upgrade functions.

What do you think about those solutions?

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented
Title: Make lontitude abbreviation as "lon" instead of "lng" like in Geofield module » Change longitude abbreviation from "lon" to "lng"
Issue summary: View changes
christianadamski’s picture

christianadamski commented
Status: Active » Closed (works as designed)

Historical reasons.