1864:
the text of an article, they should be the coordinates of something meaningful to a human, and should not overpower the rest of the article. So, for example, a table in an article on a motorway giving the coordinates of every junction would certainly be overkill for the purposes of readability. I'm not saying that information isn't meaningful or useful, just that having it in the body of the article would detract from the readability of the article. If the user (and any computer application) is then provided with a means to burrow down into the article and unearth the coordinates than that's fine too. Some data
1788:, rather than a single co-ordinate, you need a set of co-ordinates defining a boundary, anything within that boundary should return the article in you search results, as well as anywhere up to x metres from the boundary. Again this would need to be added in an "invisible" form for the most part,a s it would be entirely meaningless and obstructive for most human readers. Otherwise, artilces which take the "London" lcoation wouldn't appear on your geo-spatial search until you approached the "centre" given in the article - making
546:... Can you please spell out your concern in detal? I don't follow, so hopefully more detail would help me understand. I haven't intentionally suggested anything that would cause difficulty for editors and, in fact, I think having fewer geocoding templates should make life easier on all of us. Google was invoked because I've spoken to them directly on this exact issue and people here seem to care about them.... But our internal data extracts are in the same boat, things like
1272:, which is still being updated by Quarl as I type. It may also be more appropriate to use its talk page, for further discussion, and especially for extra feature requests. Of your first set, there should be no significant changes, but I thought Google Earth parsed wikicode, not HTML? I still find some of your suggested pitfalls ("functionality might be different in subtle ways", for example) too vague to address.
877:
WP, if you could put me in touch - in confidence of course)? #5 - there are a number of browser tools which use uFs, such as
Operator, Tails and WebCards for Firefox. For more, see the "implementations" sections for each uF on the uF wiki. As for #7, like I said, that's beyond me, but I'm happy to learn; and to assist n any way I can, and to do the subsequent work, updating documentation, informing editors, etc.
1502:
coordinates actually in
Knowledge (XXG) for? I'm not an enduser of the data, and I'm not sure what endusers like you actually do. If your aim is, say, to use your GPS receiver to help you go and look at a painting, then I'd imagine that the coordinates of the front door of the gallery would be more useful than the coordinates of the painting, especially if it is actually on the third floor. In the case of
1699:, and it's fairly obvious there that coordinates (and a map scale) have been chosen to give a reasonable overview of London. On the specific example of pictures in the National Gallery, it occurs to me that to fully represent their location, you would also need some representation of height, since the gallery has more than one floor... (edit-conflicted with Philip, hence some overlap in content)
810:
elsewhere. I suppose that's a result of an organically-grown, rather than fully-spec'd, system. Still I'm glad that we;re finding at least some common ground. I don't know enough about the way templates are made to understand you last sentence (my understanding is of HTML and microformats); I hope Quarl will be here soon; or perhaps you can make the changes?
690:
part-way change to our wikitext format will just make our readability problems worse. I think the changes are a good step but we should make sure they address all the important issues and then mass push them across the project rather than making a part-way transisition which will leave yet another syntax that people have to support. --
774:
microformats help me write a bot that goes removes locations which are known to be incorrect or which adjusts the scale for georefs inside a given bounding box? .. We tell people who want to work with our data (including our own users) to use the dumps, but microformats transcluded via n-deep indirection are not helpful there.
1531:
From the top of my head I'd say if you cannot answer the questions above the articles should not be geocoded. If we added a time stamp or time interval to the coordinates it might make sense (ever loaded a GPS trail into GoogleEarth? You get a timeline widget to select what data to display!). But for
1863:
Um, hang on. I regard anything that detracts from the readability of an article, by a human, as harmful. Knowledge (XXG) is (IMHO) first and foremost an encyclopedia intended to be consulted and read by humans, not a database to be queried by computer applications. If coordinates are to appear in
1694:
so in the article on X we'll just stick in the coordinates for London, it is not clear to a future reader of the article that those coordinates were chosen merely to represent London, and not something more specific to X, whereas if you don't put any coordinates for X, if the user doesn't know where
242:
I'm not suggesting that the coordinates are as trivial as ISBN numbers, but they certainly don't make or break an article, and citing other obtrusive templates that appear on the article page as a precedent for this one doesn't seem a particularly strong argument. Who benefits from the inclusion on
876:
Thank you. I've numbered and sub-divided your points, for convenience. I agree them all in principle. I think "coord" satisfies #1. Where and how do you suggest we achieve #3? Do you have a list, for #4 (I have some separate issues I'd like to raise with Google, about microformats (uFs) rather than
777:
Please note, I do strongly support us having microformats. My objections are that (1) we shouldn't change the project wide syntax without also addressing the other machine readability issues, and (2) we shouldn't break existing features (i.e. adjustable scale). Adding some simple modes to the coord
638:
Speaking from experience, *nothing* which comes in via transclusion is useful for machine readability of the
Wikitext. If someone is working from the dumps they need a complete copy of the templates as well as a full Wikitext parser (um which means our horribly slow PHP one, since there is no other
482:
We have millions of pages, it is not reasonable for someone to have to make millions of http requests just to extract the locations of all our pages. We provide dumps for this purpose but the vast number of possible geocoding templates makes extraction from the page data unreliable. The addition of
435:
If google spidered our webpages any faster we'd probably have to block them. ;) The microformats don't help people working off dumps, which is the preferred way to work with all of the data. I raised this issue months ago when we first setup google earth's import, and I really don't appreciate your
400:
Greetings. Please be aware that when you make changes like this you break machine readability for other tools (like google earth). I'm not opposed to making changes, but our changes should be in the direction of consolidation, and I'm not sure that this change is going far enough in that direction.
1501:
I almost agree, but I have two questions. One is: What is the object size of a series of concerts (or a collection of jewellery, or a police force, or an annual military parade)? If there isn't a meaningful answer to the question, then it isn't a meaningful question. The other is: What are the
1479:
they can be given with a precission comparable to the object size (that would be sub-meter). It makes no sense to clutter the map with gazillions of markers all at the exact same coordinates as the
National Gallery marker (in this example). For a geospatial search application (show me all articles
689:
How am I supposted to know about discussion on a page whos existance I could not have known about? The changes were not discussed here as far as I know. Please don't make us look like idiots. I've spend a lot of time wearing the
Wikimedia hat coordinating with reusers and researchers and making a
809:
When I said that they resolved problems, I was referring to machine readability of HTML pages; which they do assist. They won't help the machine readability unless they're added as discrete components in each page's wikicode - which is certainly do-able, but would require a lot of re-engineering
577:
The new template is intended to be easier for editors to use; and provides more standardised output for the benefit of end users. It also provides a Geo microformat, again for the benefit of end users (I trust that we agree that these are all good things?). It replaces three other templates (and
195:
It seems like you requested that bot tag the talk pages, which would be fine, but I don't see the point of tagging the article pages with an banner asking for a trivial piece of information to be added. In all probability the tags will stay there for a very long time, detracting from the article
1762:
One more, it seems to me that to a large extent the coordinates are meta-data, and a number of people seem to see them as simply being an unnecessary level of detail for an encyclopaedia article. It occurs to me that you may find less resistance to the introduction of this data if an approach
773:
Sure enough, I missed it. :) Um, except they don't at all solve it for us. I realize that microformats are the current ultimate in buzzword compliance, but if implemented via templates they don't do anything to make our actual pages more machine readable. For example, how does coord's use of
1724:
One further thought, for a geo-spatial search, it seems to me that really we should be tieing-in with
Knowledge (XXG)'s categorisation scheme. To stick to the examples we've been using here, if the search "knows" that the National Gallery is within 500m, there should also be some way of using
512:
Other issues aside, it seems that the way you want things to work prioritises the convenience of data manipulators like Google over and above the convenience of editors and the convenience of individual end users. It strikes me that that's a bad thing, so I hope I've misunderstood you. I'd be
988:
parameter is completely ignored, and maps are always requested at 1:300000. Theother parameters are not currently used by the geo-hack interface, but they probably will be used in the near future. Now users have no way of tagging what type of item is listed, what country it is in, or, most
1825:
While I appreciate your taking the time to comment, I have no interest in hiding such data; I view that as harmful (and there are similar issues with
Persondata, which are not on-topic here). There is already a facility for users who wish to hide coordinates to do so, with CSS.
78:. Should it go on their talk pages (as in the few examples currently tagged) or on the articles themselves (like other clean-up tags, such as clean-up itself, or "uncited" and so on? For now, please start using it (and advocating its use) if appropriate - just type
418:, regardless of what current or future template generates it; no need for it to try to parse numerous templates - and that's a great step towards "consolidation". This has been discussed for sometime; there have been plenty of chances for such issues to be raised.
1125:
So far I cannot see any benefits but there are a lot of potential pitfalls. I don't think that the potential inclusion of geo-microformats are worth us accepting any loss of features of the existing templates, especially since the geo-hack page already has the
113:
A: For a building, the main entrance; for a city, the nominated centre point (e.g from which road distances are measured), if there is one, or the location of the main administration building (Town or City Hall, etc.); for a park or open space, the approximate
1506:, perhaps the most useful coordinates for a first-time visitor would those of the back end of the Arena Day Ticket queue - something that doesn't exist for most of the year but can change every few seconds at 90 minutes before the start of a popular concert.
1773:
is used, meaning the data is (are?) hidden from human readers by default, those with an interest can add something to their css to make it visible, or use some sort of template which hides most of the data by default (eg something like the parameter used in
663:
It *is * solving problems; and it is not "uncoordinated" - you have had plenty of opportunity to comment, while this was being discussed, on numerous talk and project pages. I've restored the changes. Please discuss as resolution before reverting again.
1445:
So what? I count over 20 mainspace articles each about a painting in the
National Gallery, London. Which do you think is better: to have a rule that says that each article should have coordinates, or to have a rule that each article should refer to
1385:
I am concerned at the recent indiscriminate tagging, by a bot, for the addition of coordinates, of articles that do not need them. This project's project page makes it clear that the project is about adding coordinates to articles that are about
1648:
The CP Dinosaurs could either be tagged with the generic coordinates for the park, or section of the park, where they reside, or with individual, in-line coordinates (perhaps by making the existing list into a table) for each one - see
582:" comment, with which I wholeheartedly agree. Doesn't that also make things easier for wikicode parsers? Don't Google scan our HTML anyway? I'm not clear why the new template is less satisfactory for the internal uses you mention.
1187:
Since the template is significantly different to the coor series in operation, the impact on the wikipedia servers should possibly be investigated, to make sure the new template does not create more lookups or other server
2054:
is a good example. It was disproportionate, and detracted from the readability of the article. I wouldn't though, have a problem if tables of junction data, coordinates and all, were hived off into subsidiary articles.
1142:
I believe that most, of not all, of your concerns have been addressed in the preceding discussion. If you can see "potential pitfalls" which have not been addressed, then please identify them specifically. Thank you.
1327:) external usability of the data would be greatly enhanced. My ideal solution, forget about the display= argument, request a title= for every inline coordinate and put the one coordinate without it in the title. --
596:
capture the coord title functionality into this template? For example {{coord|latitude|longitude|display=title}}. The proliferation of geotemplates is making machine reading of wikitext very very hard to do
352:
835:
I'm not aware of any existing browser features that use microformats ... but we have wikiminiatlast *today*. Doesn't mean we shouldn't provide microformats, but it does mean we shouldn't break the tools.
642:
I am reverting your changes to the instruction pages, we don't need yet another widespread uncoordinated breakage of machine readability unless it's going to actually solve some problems. --
1480:
with 500ft) on the other hand it would make sense to code as many articles as possible. But again let me emphasize, that there must be a sane relation of precission and object size. --
1217:
Ability for article authors to control how the coordinates are displayed, either by displaying the same format as entered in the template or by specifically choosing a display format.
841:
We can resolve these issues by some simple additions to the proposed new template, but these additions might break the proposed syntax, so we shouldn't roll until they are ironed out.
483:
this template as yet another way to code coordinates in articles just makes the problem worse, when with a few minor additions to the templates we could solve the issue completely. --
384:}} will follow shortly. Please advise fellow editors, and update documentation, accordingly. Please also notify this project of any coordinate-listing templates which do not include
17:
376:}} has just been made available. It replaces the existing "coor" family of templates (which now redirect to it); simplifies data entry; standardises display; and deploys a
96:
As a newcomer to this project, might I suggest that the following questions go on the project page (or in a FAQ linked from it), with better answers than these "starters":
103:
A: Only as precise as needed for the size of place or structure; for a city, for instance, two or three decimal places or the nearest whole minutes - no need for seconds.
1407:
I have no affinity with the project, but I bring this matter to the attention of those who do. Such lack of discrimination risks bringing the project into disrepute.
1112:
1097:
32:
513:
grateful for clarification, please. (Also, is there a better place of all of these issues to be discussed, which will involve more of the people involved?)
59:
would return the geographical coordinates of London and mark it on the map. This can really unleash the power of location maps. Also posted on bugzilla
849:
243:
the article page rather than the talk page? I'd be interested to know what the reasoning was from whomever suggested you put them on the article page.
1450:
and that that article should have coordinates and the painting articles shouldn't? What do you think the consensus would be on which rule is better?
278:
53:. But the process of marking each point using coordinates is tiring and cumbersome especially if something like a clickable road map is to be made.
49:
With some wonderful code, wikipedia now churns out clickable location maps of countries which add a new degree of interactability to the wiki ex:
1591:, or anyone else. Admittedly the matter is much less urgent now that we don't have tags defacing those articles. But, well, do we really need a
778:
template (one to adjust the title, one to output the lat, long in dec. deg. for use in other templates) would get us a lot of the way there. --
457:
I didn't say anything about working faster - it's just working "smarter". Surely WP is primarily for people working off pages, not data dumps?
290:
I'm absolutely against this being placed on the article page. It's not something the average editor will respond to. It is a specialist task.
120:
Though the points are currently covered, they're not immediately apparent; and a "FAQ" format is more easily absorbed by first-time visitors.
921:
619:
1048:, who edited the templates (at my request). Hopefuly, we can find a speedy remedy that will satisfy everybody, and meet everybody's needs.
1726:
1160:
Ok - the pitfalls I can see are mostly compatiblity and functionality concerns due to the enormous number of pages that use the template.
1993:
a table in an article on a motorway giving the coordinates of every junction would certainly be overkill for the purposes of readability
229:
and other "cleanup" type tags. Your reference to "trivial" information is unwarranted, and your final question, I presume, rhetorical.
1584:
1201:
There is a good chance that functionality might be different in subtle ways that some people will perceive as a loss of functionality.
261:
1730:
639:
parser with complete template support) in order to use anything that comes out of templates. This is an unreasonable requirement.
256:
I add my voice against tagging articles. Tagging the talk page is sufficient to build a category list of articles to be tackled.
209:
I first suggested the talk pages, but was told that using the article pages would be more appropriate. It's also in keeping with
152:
2146:
2117:
2096:
2059:
2007:
1999:
1872:
1830:
1796:
1737:
1703:
1661:
1619:
1536:
1510:
1484:
1454:
1436:
1418:
1344:
1331:
1313:
1276:
1251:
1147:
1133:
1081:
1052:
1027:
1006:
993:
961:
928:
881:
865:
814:
782:
740:
707:
694:
668:
646:
625:
601:
586:
554:
517:
487:
461:
440:
422:
405:
394:
359:
341:
294:
251:
237:
204:
189:
170:
156:
128:
86:
64:
39:
1778:
196:
without having any benefit. If every wikiproject started pushing their project this way wouldn't all the articles look lovely?
50:
861:
1002:
Sure enough it doesn't pass scale. Blah! I was hoping we could get away without reverting the rest of the changes. *sigh* --
846:
Now that you have my attention, I'd be glad to work with you and everyone else to get a solution which fixes everything. :)
1654:
838:
We shouldn't make any wide scale geocoding template changes unless they resolve the outstanding issues of machine access.
265:
1373:
550:
also need a straightforward way to extract our geodata. Scanning every article via HTTP is completely unreasonable. --
1359:
957:
Where was it discussed here, I can't find it. I only look at VP once a week or so, the SNR is terrible. ::shrugs:: --
1468:
1600:
1404:, which is a concert series, not a place. The bot's author has so far not accepted that this was inappropriate.
1366:
1309:
and comment there. We'll now need to look at how this works for wikicode parsers. I think he's done a great job.
984:
should be reverted ASAP until the parameters can be included. The lack of the parameters variable means that the
1733:) to pick up those articles in the search too, rather than having to individually geo-tag each picture article.
182:
1596:
1447:
1604:
578:
eventually six, or nine; I'd proposed bot-replacing all the coor family with "coord"), which satisfies your "
311:
1561:
I agree completely. But what I'm looking for is a policy consensus that will provide me with grounds for
917:
381:
1767:
1650:
820:
Gah, it looks like we've just been having a misunderstanding. From the start I was only insisting that:
285:
272:
1569:
1394:
75:
2114:
1793:
1734:
1700:
148:
268:. I do not think there is consensus for this action and would ask you to desist & reconsider. --
2056:
1869:
1784:. Further, on the idea of geo-spatial search, it seems to me taht particularly for something like
1616:
1507:
1451:
1415:
1337:
1306:
1166:
Compatibility with all browsers, when template is in a variety of containers, positions and styles.
249:
202:
1532:
now I'd say concentrate on the clear-cut cases, that should be enough work for quite some time. --
902:
How am I supposted to know about discussion on a page whos existance I could not have known about?
2093:
2004:
1996:
1827:
1658:
1588:
1433:
1341:
1310:
1273:
1269:
1144:
1119:
1074:
1049:
925:
878:
857:
811:
737:
665:
622:
583:
514:
458:
419:
391:
356:
234:
230:
186:
167:
125:
83:
832:
It might also be wise to contact the authors of some of the existing tools that use our geodata.
2050:
Umm, yes it can be. I suggest that the six entry full-page-width table that used to appear in
415:
377:
328:
318:
1612:
135:
1580:
1238:
Name tag for coordinates, allowing articles which have multiple coordinates on the page (eg
282:
269:
2139:
1911:
I regard anything that detracts from the readability of an article, by a human, as harmful.
2051:
338:
213:
143:
1214:
Functionality that is still missing that needs be implemented and tested before release:
1913:" - as do I. I also regard the hiding of useful data as detracting from its readability.
829:
We can also only do this if we have an active consensus, not simply a failure to object.
826:
We can only do this if the new template covers the old features, which this doesn't yet.
1687:
1299:
1108:
1078:
1020:
981:
373:
244:
197:
55:
It would be very useful if one could reference the coordinates from an article, like
1789:
1608:
1101:
1024:
1003:
958:
853:
779:
704:
691:
643:
598:
551:
484:
437:
402:
291:
257:
223:
36:
547:
2143:
1533:
1481:
1328:
1248:
1239:
1130:
990:
141:
If we were to implement coordinates into the roads articles, how would we do it? --
1324:
615:
163:
314:, this template should appear on the talk page (if anywhere). It is more like
1045:
611:
335:
2113:
Really? Why then so many policies, guidelines, manuals of style etc., etc..
1410:
Please can the project team reach a policy consensus on what articles should
1576:
1503:
1425:
1401:
1113:
Knowledge (XXG):Manual of Style (dates and numbers)#Geographical coordinates
1098:
Knowledge (XXG):Manual of Style (dates and numbers)#Geographical coordinates
1575:
tags) from articles (and talk pages thereof) that don't need them, such as
1118:
I am getting the impression that this new template is being pushed only by
56:
1305:
and adding additional backwards compatibility. Please see his summary at
1163:
If the final HTML produced is different to the previous template, then:
1268:
Thank you. Some of your issues are already resolved; I suggest you see
1172:
Compatibility with external tools, such as the indexer for google earth
1169:
Compatibility with all templates that currrently use the coor templates
980:
What happened to the
Parameters variable? - I think that the change to
60:
1785:
1696:
1603:
actually passes muster, at least as the article currently stands) or
1104:
as the primary coordinate system until it is successfully phased out.
1122:(Andy Mabbett). Is there anyone else in favor of making this change?
1995:" - not if added to the existing tables of junctions, for example.
1220:
Parameters (eg scale, region etc) with ability for future expansion
1242:) to tag each set of coordinates with a name for external parsers.
353:
suggestion to add
Coordinate Display Format into User Preferences
618:
will greatly increase the machine-readability of articles; see
347:
Suggestion: Add Coordinate Display Format into User Preferences
580:
fewer geocoding templates should make life easier on all of us
82:(or whatever month we're in after this one)) on talk pages.
1319:
May I take the chance to ask for another little feature: a
110:
Q: The place is very big - what coordinates should I give?
610:
I suggest you raise the specific changes you request with
1100:
is currently incorrect - it needs to be reverted to show
18:
Knowledge (XXG) talk:WikiProject Geographical coordinates
279:
Knowledge (XXG):Administrators' noticeboard#LocateMe bot
700:
1353:
Templates with coordinates, but not using {{tl:coord}}
1727:
Category:Collections of the National Gallery, London
1599:(it's the paintings argument again, though I think
1073:The parameter issue seems to have been fixed. See
185:to articles about places, in need of coordinates.
1792:seem even more interesting than it actually is.
1690:, I see an issue with context. If you simply say
1323:arguments. With lots of inline coordinates (i.e.
414:Google Earth - or anyone else - can now read the
33:Knowledge (XXG):Peer review/Ridge Route/archive1
823:We should replace tags rather that adding more.
260:has also spoken against tagging articles, at
8:
1952:should not overpower the rest of the article
701:see my prior post on our interface problems
100:Q: How precise should the coordinates be?
1657:for examples, albeit on linear features.
45:Reference geo coordinates from an article
2088:Knowledge (XXG) doesn't work by having "
1023:until we can fix the parameter issue. -
922:Knowledge (XXG):Village pump (proposals)
1390:(emphasis added). Yet the bot added a
351:Did anything ever come of the May 2005
1467:As an enduser of the coordinate data (
1381:Articles that do not need coordinates
183:request for a bot to apply "LocateMe"
177:request for a bot to apply "LocateMe"
7:
1686:As I've said in more detail over on
1235:New Features which would be useful:
27:How should coordinates be formatted?
2138:Agreed. You probably misunderstood
1688:Talk:The Proms#Location coordinates
365:New template replaces "coor" family
31:Please help with the discussion at
1587:. I do not want an edit war with
1585:Crown Jewels of the United Kingdom
262:User talk:SatyrBot/Current project
24:
1731:Category:National Gallery, London
1019:I have reverted the redirects to
989:importantly, what scale it is. --
1374:Template:Geolinks-naturalfeature
904:" - The issue was flagged up on
264:. So far 525 articles have been
124:Comments? Additions? Brickbats?
1471:) I'd like for those paintings
1430:held annually in Central London
1360:Template:Geolinks-buildingscale
51:Indian_Institutes_of_Management
1579:(I think that's been done) or
1:
1655:Crossings of the River Severn
355:? I'd be strongly in favour.
1107:Also, the documentation for
1044:I've referred the matter to
1367:Template:Geolinks-cityscale
1338:Template_talk:Coord#Updates
1307:Template_talk:Coord#Updates
2171:
2147:18:24, 12 April 2007 (UTC)
2118:16:51, 12 April 2007 (UTC)
2097:16:45, 12 April 2007 (UTC)
2060:16:52, 17 April 2007 (UTC)
2008:16:39, 17 April 2007 (UTC)
2000:16:39, 17 April 2007 (UTC)
1873:16:13, 17 April 2007 (UTC)
1868:be hidden to first sight.
1831:15:23, 17 April 2007 (UTC)
1797:15:15, 17 April 2007 (UTC)
1738:16:51, 12 April 2007 (UTC)
1704:16:37, 12 April 2007 (UTC)
1695:London is, they can go to
1662:19:05, 15 April 2007 (UTC)
1620:19:29, 12 April 2007 (UTC)
1537:18:24, 12 April 2007 (UTC)
1511:16:33, 12 April 2007 (UTC)
1485:13:18, 12 April 2007 (UTC)
1469:user:Dschwen/WikiMiniAtlas
1455:12:27, 12 April 2007 (UTC)
1082:22:06, 11 April 2007 (UTC)
233:20:14, 4 April 2007 (UTC)
129:23:45, 31 March 2007 (UTC)
87:23:33, 31 March 2007 (UTC)
70:Template to request coords
65:16:40, 31 March 2007 (UTC)
40:01:04, 20 March 2007 (UTC)
1601:Nordic churches in London
1437:21:30, 4 April 2007 (UTC)
1419:19:59, 4 April 2007 (UTC)
1345:21:50, 4 April 2007 (UTC)
1332:21:45, 4 April 2007 (UTC)
1314:11:49, 4 April 2007 (UTC)
1277:10:59, 4 April 2007 (UTC)
1252:10:43, 4 April 2007 (UTC)
1148:07:49, 4 April 2007 (UTC)
1134:00:37, 4 April 2007 (UTC)
1053:21:29, 2 April 2007 (UTC)
1028:18:46, 2 April 2007 (UTC)
1007:18:09, 2 April 2007 (UTC)
994:18:07, 2 April 2007 (UTC)
962:22:06, 2 April 2007 (UTC)
929:21:33, 2 April 2007 (UTC)
882:10:08, 3 April 2007 (UTC)
866:23:53, 2 April 2007 (UTC)
815:23:16, 2 April 2007 (UTC)
783:22:06, 2 April 2007 (UTC)
741:21:37, 2 April 2007 (UTC)
708:18:02, 2 April 2007 (UTC)
695:17:53, 2 April 2007 (UTC)
669:17:12, 2 April 2007 (UTC)
647:17:04, 2 April 2007 (UTC)
626:14:37, 2 April 2007 (UTC)
602:14:28, 2 April 2007 (UTC)
587:23:04, 2 April 2007 (UTC)
555:22:47, 2 April 2007 (UTC)
518:22:07, 2 April 2007 (UTC)
488:18:02, 2 April 2007 (UTC)
462:17:12, 2 April 2007 (UTC)
441:17:04, 2 April 2007 (UTC)
423:14:37, 2 April 2007 (UTC)
406:14:06, 2 April 2007 (UTC)
395:13:48, 2 April 2007 (UTC)
360:12:47, 2 April 2007 (UTC)
342:12:33, 5 April 2007 (UTC)
295:04:44, 5 April 2007 (UTC)
252:22:48, 4 April 2007 (UTC)
238:20:14, 4 April 2007 (UTC)
205:15:40, 4 April 2007 (UTC)
190:09:54, 2 April 2007 (UTC)
171:14:24, 2 April 2007 (UTC)
157:01:15, 1 April 2007 (UTC)
1597:Crystal Palace Dinosaurs
1595:tag on the talk page of
1448:National Gallery, London
1075:Template:Coord/doc#Usage
1605:Art in Perpetuity Trust
1295:Quarl is done updating
436:dismissive response. --
80:{{LocateMe|April 2007}}
1779:Province of Canterbury
918:Template talk:Coor dms
312:Template talk:LocateMe
1651:Manchester Ship Canal
1607:? I think I'll take
852:comment was added by
310:Indeed: as I said at
1475:to have coordinates
1115:. I think it should.
620:Project Microformats
382:template:coord title
1414:have coordinates?
372:Please note that {{
1615:while I'm at it.
1270:Template:Coord/doc
1120:User:Pigsonthewing
1111:does not mention
869:
76:Template:LocateMe
2162:
1783:
1777:
1772:
1766:
1581:Kew Constabulary
1574:
1568:
1565:coordinates (or
1399:
1393:
1304:
1298:
1291:
1126:geo-microformat.
847:
699:You may wish to
333:
327:
323:
317:
247:
228:
222:
218:
212:
200:
2170:
2169:
2165:
2164:
2163:
2161:
2160:
2159:
2115:David Underdown
2052:Tinsley Viaduct
1794:David Underdown
1781:
1775:
1770:
1764:
1735:David Underdown
1701:David Underdown
1572:
1566:
1397:
1391:
1383:
1355:
1302:
1296:
1293:
1289:
848:—The preceding
807:
575:
416:Geo microformat
378:Geo microformat
371:
367:
349:
331:
325:
321:
315:
245:
226:
220:
216:
210:
198:
181:Please note my
179:
139:
94:
72:
47:
35:; thank you. --
29:
22:
21:
20:
12:
11:
5:
2168:
2166:
2158:
2157:
2156:
2155:
2154:
2153:
2152:
2151:
2150:
2149:
2127:
2126:
2125:
2124:
2123:
2122:
2121:
2120:
2104:
2103:
2102:
2101:
2100:
2099:
2081:
2080:
2079:
2078:
2077:
2076:
2075:
2074:
2073:
2072:
2071:
2070:
2069:
2068:
2067:
2066:
2065:
2064:
2063:
2062:
2057:Philip Trueman
2029:
2028:
2027:
2026:
2025:
2024:
2023:
2022:
2021:
2020:
2019:
2018:
2017:
2016:
2015:
2014:
2013:
2012:
2011:
2010:
1972:
1971:
1970:
1969:
1968:
1967:
1966:
1965:
1964:
1963:
1962:
1961:
1960:
1959:
1958:
1957:
1956:
1955:
1931:
1930:
1929:
1928:
1927:
1926:
1925:
1924:
1923:
1922:
1921:
1920:
1919:
1918:
1917:
1916:
1915:
1914:
1890:
1889:
1888:
1887:
1886:
1885:
1884:
1883:
1882:
1881:
1880:
1879:
1878:
1877:
1876:
1875:
1870:Philip Trueman
1846:
1845:
1844:
1843:
1842:
1841:
1840:
1839:
1838:
1837:
1836:
1835:
1834:
1833:
1810:
1809:
1808:
1807:
1806:
1805:
1804:
1803:
1802:
1801:
1800:
1799:
1749:
1748:
1747:
1746:
1745:
1744:
1743:
1742:
1741:
1740:
1729:(a sub-cat of
1713:
1712:
1711:
1710:
1709:
1708:
1707:
1706:
1692:x is in London
1677:
1676:
1675:
1674:
1673:
1672:
1671:
1670:
1669:
1668:
1667:
1666:
1665:
1664:
1633:
1632:
1631:
1630:
1629:
1628:
1627:
1626:
1625:
1624:
1623:
1622:
1617:Philip Trueman
1548:
1547:
1546:
1545:
1544:
1543:
1542:
1541:
1540:
1539:
1520:
1519:
1518:
1517:
1516:
1515:
1514:
1513:
1508:Philip Trueman
1492:
1491:
1490:
1489:
1488:
1487:
1460:
1459:
1458:
1457:
1452:Philip Trueman
1440:
1439:
1416:Philip Trueman
1382:
1379:
1378:
1377:
1370:
1363:
1354:
1351:
1350:
1349:
1348:
1347:
1336:Please ask on
1292:
1287:
1286:
1285:
1284:
1283:
1282:
1281:
1280:
1279:
1259:
1258:
1257:
1256:
1255:
1254:
1245:
1244:
1243:
1228:
1227:
1226:
1225:
1224:
1223:
1222:
1221:
1218:
1207:
1206:
1205:
1204:
1203:
1202:
1194:
1193:
1192:
1191:
1190:
1189:
1180:
1179:
1178:
1177:
1176:
1175:
1174:
1173:
1170:
1167:
1161:
1153:
1152:
1151:
1150:
1137:
1136:
1127:
1123:
1116:
1109:Template:Coord
1105:
1093:
1092:
1091:
1090:
1089:
1088:
1087:
1086:
1085:
1084:
1062:
1061:
1060:
1059:
1058:
1057:
1056:
1055:
1035:
1034:
1033:
1032:
1031:
1030:
1021:Template:Coord
1012:
1011:
1010:
1009:
997:
996:
982:Template:coord
977:
976:
975:
974:
973:
972:
971:
970:
969:
968:
967:
966:
965:
964:
942:
941:
940:
939:
938:
937:
936:
935:
934:
933:
932:
931:
916:main page, on
913:this project's
907:this talk page
887:
886:
885:
884:
871:
870:
844:
843:
842:
839:
836:
833:
830:
827:
824:
806:
803:
802:
801:
800:
799:
798:
797:
796:
795:
794:
793:
792:
791:
790:
789:
788:
787:
786:
785:
756:
755:
754:
753:
752:
751:
750:
749:
748:
747:
746:
745:
744:
743:
721:
720:
719:
718:
717:
716:
715:
714:
713:
712:
711:
710:
678:
677:
676:
675:
674:
673:
672:
671:
654:
653:
652:
651:
650:
649:
640:
631:
630:
629:
628:
605:
604:
574:
571:
570:
569:
568:
567:
566:
565:
564:
563:
562:
561:
560:
559:
558:
557:
531:
530:
529:
528:
527:
526:
525:
524:
523:
522:
521:
520:
499:
498:
497:
496:
495:
494:
493:
492:
491:
490:
471:
470:
469:
468:
467:
466:
465:
464:
448:
447:
446:
445:
444:
443:
428:
427:
426:
425:
409:
408:
374:template:coord
369:
366:
363:
348:
345:
308:
307:
306:
305:
304:
303:
302:
301:
300:
299:
298:
297:
178:
175:
174:
173:
138:
133:
132:
131:
118:
117:
116:
115:
107:
106:
105:
104:
93:
90:
71:
68:
54:
46:
43:
28:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
2167:
2148:
2145:
2141:
2137:
2136:
2135:
2134:
2133:
2132:
2131:
2130:
2129:
2128:
2119:
2116:
2112:
2111:
2110:
2109:
2108:
2107:
2106:
2105:
2098:
2095:
2091:
2087:
2086:
2085:
2084:
2083:
2082:
2061:
2058:
2053:
2049:
2048:
2047:
2046:
2045:
2044:
2043:
2042:
2041:
2040:
2039:
2038:
2037:
2036:
2035:
2034:
2033:
2032:
2031:
2030:
2009:
2006:
2003:
2002:
2001:
1998:
1994:
1990:
1989:
1988:
1987:
1986:
1985:
1984:
1983:
1982:
1981:
1980:
1979:
1978:
1977:
1976:
1975:
1974:
1973:
1953:
1949:
1948:
1947:
1946:
1945:
1944:
1943:
1942:
1941:
1940:
1939:
1938:
1937:
1936:
1935:
1934:
1933:
1932:
1912:
1908:
1907:
1906:
1905:
1904:
1903:
1902:
1901:
1900:
1899:
1898:
1897:
1896:
1895:
1894:
1893:
1892:
1891:
1874:
1871:
1867:
1862:
1861:
1860:
1859:
1858:
1857:
1856:
1855:
1854:
1853:
1852:
1851:
1850:
1849:
1848:
1847:
1832:
1829:
1824:
1823:
1822:
1821:
1820:
1819:
1818:
1817:
1816:
1815:
1814:
1813:
1812:
1811:
1798:
1795:
1791:
1790:Charing Cross
1787:
1780:
1769:
1761:
1760:
1759:
1758:
1757:
1756:
1755:
1754:
1753:
1752:
1751:
1750:
1739:
1736:
1732:
1728:
1723:
1722:
1721:
1720:
1719:
1718:
1717:
1716:
1715:
1714:
1705:
1702:
1698:
1693:
1689:
1685:
1684:
1683:
1682:
1681:
1680:
1679:
1678:
1663:
1660:
1656:
1652:
1647:
1646:
1645:
1644:
1643:
1642:
1641:
1640:
1639:
1638:
1637:
1636:
1635:
1634:
1621:
1618:
1614:
1610:
1609:Maureen Paley
1606:
1602:
1598:
1594:
1590:
1586:
1582:
1578:
1571:
1564:
1560:
1559:
1558:
1557:
1556:
1555:
1554:
1553:
1552:
1551:
1550:
1549:
1538:
1535:
1530:
1529:
1528:
1527:
1526:
1525:
1524:
1523:
1522:
1521:
1512:
1509:
1505:
1500:
1499:
1498:
1497:
1496:
1495:
1494:
1493:
1486:
1483:
1478:
1474:
1470:
1466:
1465:
1464:
1463:
1462:
1461:
1456:
1453:
1449:
1444:
1443:
1442:
1441:
1438:
1435:
1431:
1427:
1423:
1422:
1421:
1420:
1417:
1413:
1408:
1405:
1403:
1396:
1389:
1380:
1375:
1371:
1368:
1364:
1361:
1357:
1356:
1352:
1346:
1343:
1339:
1335:
1334:
1333:
1330:
1326:
1322:
1318:
1317:
1316:
1315:
1312:
1308:
1301:
1288:
1278:
1275:
1271:
1267:
1266:
1265:
1264:
1263:
1262:
1261:
1260:
1253:
1250:
1246:
1241:
1237:
1236:
1234:
1233:
1232:
1231:
1230:
1229:
1219:
1216:
1215:
1213:
1212:
1211:
1210:
1209:
1208:
1200:
1199:
1198:
1197:
1196:
1195:
1186:
1185:
1184:
1183:
1182:
1181:
1171:
1168:
1165:
1164:
1162:
1159:
1158:
1157:
1156:
1155:
1154:
1149:
1146:
1141:
1140:
1139:
1138:
1135:
1132:
1128:
1124:
1121:
1117:
1114:
1110:
1106:
1103:
1102:Template:Coor
1099:
1095:
1094:
1083:
1080:
1076:
1072:
1071:
1070:
1069:
1068:
1067:
1066:
1065:
1064:
1063:
1054:
1051:
1047:
1043:
1042:
1041:
1040:
1039:
1038:
1037:
1036:
1029:
1026:
1022:
1018:
1017:
1016:
1015:
1014:
1013:
1008:
1005:
1001:
1000:
999:
998:
995:
992:
987:
983:
979:
978:
963:
960:
956:
955:
954:
953:
952:
951:
950:
949:
948:
947:
946:
945:
944:
943:
930:
927:
923:
919:
915:
914:
909:
908:
903:
899:
898:
897:
896:
895:
894:
893:
892:
891:
890:
889:
888:
883:
880:
875:
874:
873:
872:
867:
863:
859:
855:
851:
845:
840:
837:
834:
831:
828:
825:
822:
821:
819:
818:
817:
816:
813:
804:
784:
781:
776:
775:
772:
771:
770:
769:
768:
767:
766:
765:
764:
763:
762:
761:
760:
759:
758:
757:
742:
739:
735:
734:
733:
732:
731:
730:
729:
728:
727:
726:
725:
724:
723:
722:
709:
706:
702:
698:
697:
696:
693:
688:
687:
686:
685:
684:
683:
682:
681:
680:
679:
670:
667:
662:
661:
660:
659:
658:
657:
656:
655:
648:
645:
641:
637:
636:
635:
634:
633:
632:
627:
624:
621:
617:
613:
609:
608:
607:
606:
603:
600:
595:
591:
590:
589:
588:
585:
581:
572:
556:
553:
549:
548:Wikiminiatlas
545:
544:
543:
542:
541:
540:
539:
538:
537:
536:
535:
534:
533:
532:
519:
516:
511:
510:
509:
508:
507:
506:
505:
504:
503:
502:
501:
500:
489:
486:
481:
480:
479:
478:
477:
476:
475:
474:
473:
472:
463:
460:
456:
455:
454:
453:
452:
451:
450:
449:
442:
439:
434:
433:
432:
431:
430:
429:
424:
421:
417:
413:
412:
411:
410:
407:
404:
399:
398:
397:
396:
393:
390:. Thank you.
389:
388:
383:
379:
375:
364:
362:
361:
358:
354:
346:
344:
343:
340:
337:
330:
320:
313:
296:
293:
289:
288:
287:
284:
280:
276:
275:
274:
271:
267:
263:
259:
255:
254:
253:
250:
248:
241:
240:
239:
236:
232:
225:
215:
208:
207:
206:
203:
201:
194:
193:
192:
191:
188:
184:
176:
172:
169:
165:
161:
160:
159:
158:
154:
150:
146:
145:
137:
134:
130:
127:
123:
122:
121:
112:
111:
109:
108:
102:
101:
99:
98:
97:
91:
89:
88:
85:
81:
77:
74:I've created
69:
67:
66:
62:
58:
52:
44:
42:
41:
38:
34:
26:
19:
2094:Andy Mabbett
2089:
2005:Andy Mabbett
1997:Andy Mabbett
1992:
1954:" - I agree.
1951:
1910:
1865:
1828:Andy Mabbett
1691:
1659:Andy Mabbett
1592:
1589:Andy Mabbett
1562:
1476:
1472:
1434:Andy Mabbett
1429:
1411:
1409:
1406:
1387:
1384:
1342:Andy Mabbett
1320:
1311:Andy Mabbett
1294:
1274:Andy Mabbett
1240:Arthur Range
1145:Andy Mabbett
1050:Andy Mabbett
985:
926:Andy Mabbett
912:
911:
906:
905:
901:
879:Andy Mabbett
812:Andy Mabbett
808:
738:Andy Mabbett
666:Andy Mabbett
623:Andy Mabbett
616:microformats
593:
584:Andy Mabbett
579:
576:
515:Andy Mabbett
459:Andy Mabbett
420:Andy Mabbett
392:Andy Mabbett
386:
385:
368:
357:Andy Mabbett
350:
309:
235:Andy Mabbett
231:Andy Mabbett
187:Andy Mabbett
180:
168:Andy Mabbett
142:
140:
126:Andy Mabbett
119:
95:
84:Andy Mabbett
79:
73:
48:
30:
1763:similar to
1325:Ridge Route
736:To which .
283:Tagishsimon
270:Tagishsimon
164:Ridge Route
2142:here... --
1768:persondata
1046:User:Quarl
612:User:Quarl
370:Important!
144:Rschen7754
136:U.S. Roads
57:geo:London
1577:The Proms
1504:The Proms
1426:The Proms
1402:The Proms
805:Outdent 2
614:. Again,
573:Outdent 1
277:See also
246:Yomangani
199:Yomangani
1593:LocateMe
1570:LocateMe
1563:removing
1395:LocateMe
1025:jredmond
1004:Gmaxwell
959:Gmaxwell
862:contribs
854:Gmaxwell
850:unsigned
780:Gmaxwell
705:Gmaxwell
692:Gmaxwell
644:Gmaxwell
599:Gmaxwell
552:Gmaxwell
485:Gmaxwell
438:Gmaxwell
403:Gmaxwell
329:copyedit
319:reqphoto
292:Tyrenius
258:Tyrenius
153:contribs
2144:Dschwen
1613:WP:COIN
1534:Dschwen
1482:Dschwen
1329:Dschwen
1249:Ozhiker
1131:Ozhiker
991:Ozhiker
920:and on
597:well.--
592:Can we
114:centre.
2140:WP:IAR
1866:should
1786:London
1697:London
1477:unless
1388:places
1290:Update
594:please
339:(Talk)
286:(talk)
273:(talk)
266:tagged
214:expand
2090:rules
1424:From
1321:title
1300:coord
1188:load.
986:scale
910:, on
703:]. --
387:coord
336:ALoan
334:. --
324:than
92:FAQs?
16:<
1096:The
1079:Para
1077:. --
858:talk
380:. {{
224:ISBN
162:See
149:talk
61:here
2092:".
1653:or
1611:to
1583:or
1473:not
1432:".
1428:: "
1412:not
1400:to
63:--
37:NE2
1782:}}
1776:{{
1771:}}
1765:{{
1573:}}
1567:{{
1398:}}
1392:{{
1376:}}
1372:{{
1369:}}
1365:{{
1362:}}
1358:{{
1340:.
1303:}}
1297:{{
1247:--
1129:--
924:.
864:)
860:•
401:--
332:}}
326:{{
322:}}
316:{{
281:--
227:}}
221:{{
219:,
217:}}
211:{{
166:.
155:)
151:-
1991:"
1950:"
1909:"
900:"
868:.
856:(
147:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.