Remove map url field from venues

Bug #524013 reported by Thomas Bechtold on 2010-02-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LoCo Team Portal

Bug Description

i think longitude and latitude are enough. we don't need the map url field.

Related branches

tags: added: schema-change
Michael Hall (mhall119) on 2010-02-27
tags: added: venues
Michael Hall (mhall119) on 2010-03-12
tags: added: needs-decision
Michael Hall (mhall119) on 2010-03-12
Changed in loco-directory:
status: New → Confirmed
Michael Hall (mhall119) on 2010-03-13
tags: added: maps
Nathan Handler (nhandler) wrote :

I personally find the maps much more useful than longitude and latitude. Longitude and Latitude mean absolutely nothing to me. I would simply copy them to Google Maps to figure out where the coordinates point to. However, I do agree that there is no point in specifying both longitude, latitude, and a map url. Instead, the map url should be generated automatically using the coordinates (or the other way around, generate the coordinates from the map url).

Changed in loco-directory:
importance: Undecided → Low
status: Confirmed → Triaged
Laura Czajkowski (czajkowski) wrote :

Yup I think maps are what everyone is used to, longitude and latitude are handy if you are used to them or have an iphone!
So can we please just use a map instead

Daniel Holbach (dholbach) wrote :

From a UI and usability perspective it would probably be the easiest to either paste in a Google Maps URL (and we get our data from it?) or you choose a position on Google map and we get lat. and long. from it.

Not sure how straight-forward that is to implement.

Laura Czajkowski (czajkowski) wrote :

how about a field where you can copy and paste in the map so it's displayed. that way if folks want to use a google map they can, or if their area is mapped enough you can use an open street map, but both display easily once it's just a field to add and display the image?

How about using a service like Geohack (which wikipedia uses).

e.g. has a link at the top
"Coordinates: 51°29′32.0″N 0°07′33.5″W" which links to:-

Which lets the user choose which mapping service to use.

If people can discover the Lat/Long of the location of their event (this is trival to do) then we could hold that in the database and generate the above geohack url to present a decent page to them?

Laura Czajkowski (czajkowski) wrote :

oh I like that idea. +1

Changed in loco-directory:
importance: Low → High
Thomas Bechtold (toabctl) wrote :

When we have longitude/latitude in the database, we can show a map with all venues for a given event (for example). i think long/lat are much more flexible than a map-url. I like the idea that a user can pick long/lat on a map.

tags: removed: needs-decision
David Rubin (drubin) wrote :

Storing a map url is pointless my vote is for the longitude/latitude in the DB and choose to display it in what ever means you want.

You can even hack a single google map API to allow for easier entering of the co-ordinates :) similar to the way LP does it for peoples locations.

my 2cents

Efrain Valles (effie-jayx) wrote :

I have hacked a bit on this and I have used google maps to get long and latitude. I do not feel this is code we should merge for LD yet. Consider this proof of concept. . I am willing to elaborate more, like having the pick set city and country acording to long and lat but first we should further discuss:

 * is google maps what we are using for our maps? learning the apis and doing this would mean duplication of efforts if someine else isworking with other maps.

 * Apart from the schema change, should this be picked up, forms for new venues would have to be more flexible than modelforms to be able to better place the map.

 * general cleanup of the map imports, currently there are imports for maps in many places. can we discuss where the maps apis of google are needed?

Efrain Valles (effie-jayx) wrote :

After hacking some more at suggestion of dholbach and toabctl, I have merged the openlayers branch with trunk, it is available at, works like a charm. Questions 2 and 3 above still apply.

Changed in loco-directory:
milestone: none → 0.2.11
status: Triaged → Fix Committed
Changed in loco-directory:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers