641:
to something more powerful. Here is my reasoning: As far as I can tell template processing occurs on the "display-side" (meaning rendering side) of the media wiki. In other words when you edit a page with a template, the original unexpanded template text is added to the text in the database. The template is not expanded until the page is rendered to html. This means if you would like to do anything useful on the edit-side, like cataloging geographical coordinates as they are entered into the database, you have to first expand the template text. So in musing on this subject I realized that templates add an additional barrier. Using a
142:
resolution's a bit worse). I don't think there are any public servers running the software itself. It would require a server with 3D graphics abilities doing the equivalent of generating screenshots with the program. The code is open source, so perhaps it's doable, but I think it would be a major undertaking. (And not one for the
Wikimedia developers really.) Should we ask a dev/committee member about enabling worldwind:// links? --
695:
at least for the next realease of
Mediawiki. There is a new hook in 1.4 called the 'ArticleSave' hook that would allow an extension to be called when a page is saved. (Unfortunately templates complicate its use.) it makes it possible to parse for coordinates and put them into a database, on-save. Unfortunately if you use templates its complicated because they are only expanded on render. --
536:(like measuring great cicle distances), and it complicated support of a georef database. It is bad enough to support the various formats for output. Converting input data to WGS84 should be quite easy, and it needs to be done only once for each point. I do believe there are various Swiss online maps that support online conversion to WGS84. --
694:
Perhaps the solution is to move a bunch of articles about a specific area, like a city, to your server. Then implement the extensions however you want and show it to other developers. They are often very resistent as their priorities are not on new functionality but on bugs, performance and security,
169:
Yup works fine. Thanks, my two internet addictions are now united! To give an indication of whether scale's working, the
Heathrow link leads to Heathrow's main runway being about one screen across. The top Oslo link goes south east as far as Arjangs Commun and north west as far as Buskerud Fylke. The
767:
I have now implemented the
ArticleSave hook, and it most certainly seems to be exactly what is needed. I have not implemented the actual SQL storage yet, but all required information is certainly available. I will also soon rewrite the special page into an extension page, so that all of this is via
676:
One very real advantage of using templates at this stage is that it is easy having a robot go through and modify current usage if a change is necessary. Plus, it allows is to get experience and learn now. Waiting for a change in the official
Wikimedia software before getting a change to build enough
640:
Yes in addition I'm not sure that MediaWiki supports "edit-side" extensions which make things things difficult. I'm going to go out on a limb and suggest that templates might not be the best way to implement geographic coordinates, if you want to eventually move from just a standardization of format
535:
I did at one point implement input in a few coordinate systems other than WGS84, but I then decided against it. For a number of reasons: one being lack of time (which is really sufficient), one other being that it would complicate systems extracting georef meta-data from the
Knowledge (XXG) articles
751:
I've played with your extension idea, and I think I've got some quite promising results. It seems like there is a concept there that will also work very well together with infobox templates and such - it will in fact work significantly better than the current approach due to the current limitations
738:
and got some fairly condescending responses. Its sort of a chicken in the egg thing, you cannot pass template parameters to an extension but you can't make effective templates without using extensions. I've started a proposal on my meta userpage about how to use extensions to manage geocoordinates.
662:
You are raising very important issues. The subject of geographical coordinates has become more inclusive then first anticipated, and building and maintaining the reverse database is the remaining one big issue that must be solved first. (Currently I am just doing a simple scan with a Perl script to
854:
PHP includes a image manipulation library called GD. I'm pretty sure that PHP includes this library by default and the code is very straightforward, I'm guessing wikipedia servers already have the capability and maybe already use it for math rendering(does anyone know how math is rendered to PNG?)
757:
I will see what I can do about the storage bit. If you have more info on the
ArticleSave hook, that would be appreciated. For the database solution (including sorting out the neighbourhoods) I do believe I have a concept, but I just din't have the time to write more now (non-Knowledge (XXG) things
894:
My assumption is that by defining three or more points on the map surface to define the map space, I can approximate the projection well enough for most maps, and this is an easy way for an editor to define a map image. Options for more detailed information about the projection will eventually be
726:
Switching to extensions would imply converting existing coor templates (quite managable via a robot), but also converting existing coordinates in the US articles to this template. This conversion needs to happen after the extension has been installed in the
English Knowledge (XXG), of course. --
545:
I see that it takes quite some time to implement such functions and makes db-queries more complicated. Converting coordinates is not easy at all especially for non mathematicians. At the moment there is an error of about 150m in northing and 80m in easting in your conversion, and we don't know
141:
Worldwind itself connects to public servers to get its data, i.e. Landstat7, USGS, MODIS, SVS, WMS, Blue Marble. Its unique feature is combining all of them in a pretty (3D) format. You can zoom from seeing an entire globe, to seeing individual houses (at least in the US, everywhere else the
890:
Ideally there will also need to be some kind of caching routines so that the image only needs to be rendered the first time it is accessed after the map tag has been altered otherwise we can default to the last rendered image and save cycles. (I don't know how to do this yet.)
707:
Does
ArticleSave give you the article in the before and after forms? ( I believe that is needed, because you should also be allowed to remove coordinates from articles). Wrt storage in a database and orgainization in a database, I don't think that should be a problem.
153:
No need. I have now enabled worldwind: on the demo Wiki, so that the above thing should work. I've placed it at the end of the page, so you can try it out, now. I will include the support for worldwind: in the patch that I will provide for the Wiki software. --
202:
I am working on incorporating a World Wind layer that provides clickable reverse links into
Knowledge (XXG). It seems to work real nice so far, but I need to spend more time on the automation process that extracts the coordinates from Knowledge (XXG). --
711:
Templates needs to be considered whataver the solution, because one of the major applications of coordinates in articles will be via infoboxes. This must be supported. I will investigate the extension mechanism also. Some of the requirements are:
567:
for help. Wrt. the error in CH1903, yes I am aware of it, but I simply haven't had time to investigate. Every country seems to have had their own coordinate system, and they are different in many subtle respects. The source code is available, see
61:
300:
for this location is Northing 5200824 Easting 379514 Zone 32T. For the map.search.ch one I couldn't find any. If you can please find more information, ideally also on how to navigate directly, I would be happy to implement.--
318:
which seems to be what is being used (centered around an observatory in Bern, no less!). I have to investigate what Oblique Mercator is, but if you can find how to make direct links, I'll supply the coordinates. :-)
777:
Using templates shouldn't be a problem unless the template needs to send individual parameters to the extension so if you are sending an extension to a template it should work but doesn't. See {{catmore <math:
752:
wrt. templates as arguments for templates. The only real disadvantage I can see right now is that one cannot control the resulting appearance from within Wiki - although some would claim that is an advantage ;-).
546:
whether this is systematic or just a trunctation error. There are NO exact maps with WGS84 in Switzerland. How sould the average user be able to do a correct and accurate conversion? Slightly disappointed --
880:
The script calculates the pixel equivalents of the projected geo-points and stores a list of pixel to text relations (clipped to the map, error text should be generated if a point is not on the map.)
722:
It must also be possible to hide the actual markup of the coordinates, and have either nothing appear, of a link to the map sources with a different text. This may perhaps be handled via a template.
463:
http://gis.swissinfo.org/swissinfo-geo/neapoljs_ENGLISH.htm?Resolution=small&KOORDX= {ch1903northing}&KOORDY={ch1903easting}&markx={ch1903northing}&marky={ch1903easting}&ZOOM=5
839:
525:. For OSGB36 I saw conversion is implemented. Is this also the case for CH1903? We would be very glad not having to convert the coordinates to WGS84 manually anymore. Thanks in advance --
17:
522:
647:
would simplify things later on, though implementing it now would mean convincing mediawiki developers to add an extension to the existing site. I hope this makes sense. --
404:
Looks excellent if you ask me (not that I am an expert). I tried to look at the possibility of direct linking the Swiss maps, but it seems they use some sort of 5 minute
39:
521:
I'm referring on user Docu's first comment. Because all small scale maps of Switzerland are in CH1903 datum, we'd like to use them as input for the geo tag, see
268:
60:
I tried to add to the kvaleberg.com wiki, but didn't have a great deal of success. Knowledge (XXG) only seems to recognise links which start "http://". e.g.
133:
thing, for those who have Worldwind installed locally. For those who have not, do you know if there are any public servers where this can be accessed? --
663:
generate points. This certainly has to happen internally, and kept in the SQL database.) I am working with Magnus Manske so see what we can come up with.
739:
I'm still trying to decide how I feel about templates, the mediawiki is not really designed to use them for anything beyond standard messages. Read
129:
Seems like a really brilliant idea if you ask me, just needs some thought and consideration when implementing. I'm sure there are ways around the
104:
Could be rewritten to automatically parse several possible input formats: N/S E/W notation vs signed coordinates, decimal vs deg-min-sec, etc.
503:
86:
What about using a redirector PHP script? I just tested that HTTP redirect to worldwind:// URI works in Firefox. The code itself is simple:
608:
619:
Good point. Not expanding the template arguments within the extensions seems to me like a mis-feature that should be attended to. --
107:
Similar code that produces a snippet of XML instead, and serves it as "Content-type: application/keyhole", can be used for output of
170:
bottom Oslo link leads to Sandvika being about 25% in from the right, and Ekeberg being about the same amount in from the left. --
101:
The disadvantage is that it stays open. But it could be opened in a new window and contain javascript to close itself immediately.
576:
550:
540:
529:
115:
111:
files for Google Earth. What output will be produced could even be configurable by the user, or both links could be provided.--
607:
instead of just formating the coordinate and making it a link to a special page? It seems like this might be problematic (see
95:
header("302 Redirect"); header("Location: worldwind://goto/world=Earth&lat=$ LAT&lon=$ LON&view=0.008"); ?: -->
740:
435:
630:
Apparently this is not a misfeature, I found out it has to work this way, since wikimarkup stops inside of <tags: -->
642:
604:
245:. It would be nice if there was a way to use them as output or possibly as input. On the other hand, sites such as
352:
783:
563:
It would seems that the Swiss map services are lacking the feature of providing WGS84 coordinates. But look at
338:
734:
I agree we need to use both, but this seems extremely problematic. I talked to a few developers about this on
719:
It must produce standard markup when used stand-alone, including link-through to the special map sources page.
502:
Thanks, even a special page! Now I only need to find a way to import the coordinates (and possibly more) from
898:
Later a special search page will essentially generate a map tag and perhaps find an appropriate map image. --
445:. To search by coordinates, I suppose one would need to simulate a GPS input for local software. -- User:Docu
386:
108:
855:
I'm guessing that projecting points onto a image of a map could be done in a couple hundred lines of code.
899:
842:
744:
696:
648:
612:
735:
52:
Plus it seems reasonable to support it, since its landmark links currently link to Knowledge (XXG). --
64:
doesn't work. Below is what I added. If you can tell me a better way of doing it, I'd appreciate it:
258:
468:
The optional "marky" part creates a green marker. Thank you for making this possible. -- User:Docu
349:
311:
646:
coor|48_46_36.48_N_121_48_51.84_W|Special:Mapsources/48_46_36.48_N_121_48_51.84_W </geo: -->
367:
did include coordinates in the displayed source, but they appear to be available only offline (
242:
883:
The script generates an image where numbers are overlayed at the correct points on the map.
190:
886:
The script generates a text key, showing the text corresponding to each numbered point.
483:
which lists this entry first. (You mixed nothing and easting, otherwise it was ok). --
875:
A set of projected geo-points to text relations (the text can include any wikimarkup).
677:
data to get the experience on how it ought to have been sounds like a non-starter. --
187:
600:
547:
526:
112:
431:
Thanks. For now, a possible way I came up with to link to a local map is to add to
631:. If it didn't then template syntax would for example be confused with TeX, syntax.
96:
NASA WorldWind redirect. Requires <a href="http://worldwind.arc.nasa.gov/": -->
257:
Do you have further information about these coordinates? Seems like some sort of
335:
40:
worldwind://goto/world=Earth&lat=52.61664&lon=-1.39980&view=0.00739
184:
716:
It must be possible to supply it as an argument to an infobox style template.
283:
270:
223:
46:
869:
A references to a Knowledge (XXG) image (the image of course depicts a map.)
769:
759:
728:
678:
620:
596:
573:
537:
484:
409:
346:
331:
320:
302:
227:
204:
155:
134:
368:
212:
171:
143:
78:
53:
222:
There is a demo Knowledge (XXG) layer for NASA World Wind available via
389:, it could probably use a re-write by a specialist editor. -- User:Docu
315:
253:
don't appear to support direct links with coordinates. -- User:Docu
569:
261:; swissinfo gives coordinates Easting 600500 Northing 199500 for
32:
872:
A set of geo-point to pixel relations that define the map space.
342:
262:
226:
if anyone are interested. Any feedback would be appreciated! --
246:
312:
http://www.geocities.com/CapeCanaveral/1224/prj/ch/ch1903.html
297:
442:
564:
371:
18:
Knowledge (XXG) talk:WikiProject Geographical coordinates
364:
250:
592:
Search Mechanisms, Finding Articles based on Geography
786:
572:, so I would appreciate if you could investigate. --
341:. The old observatory's coordinates can be found at
850:
Map Markup/Projecting Geographic Points onto Images
479:This is now in the map sources. I also made a page
833:
408:for the URLs designed to make it impossible. --
363:At first glance I thought TeleAtlas/Endoxon at
45:It's now open source (they have their own wiki
645:for geographic coordinates (i.e. <geo: -->
31:Any chance of having automatic generation of
8:
354:, though you already implemented it. Great!
337:in German and French (see PDF), and one in
834:{\displaystyle \sum _{x=2}^{6}x^{2}=2^{2}}
779:\sum_{x=2}^{6} x^{2} = 2^{2}</math: -->
441:, which can give unspectacular links like
224:http://wiki.worldwindcentral.com/Wikipedia
825:
812:
802:
791:
785:
609:m:Talk:Write your own MediaWiki extension
460:(Finally) The following URL should work:
370:). Linking doesn't apppear possible at
599:, is it possible that eventually, the
7:
241:Swiss maps generally use the Swiss
77:Perhaps this is just a bad idea. --
862:The rendering script encounters a
841:}} that is the real barrier no? --
198:From World Wind to Knowledge (XXG)
186:on how to add new URL types, like
68:=== Requiring special software ===
24:
603:could be modified to access an a
504:de:Template:Places in Switzerland
1:
858:The process works like this:
247:http://www.swissinfo-geo.org
758:needs to be done also). --
577:06:19, 24 August 2005 (UTC)
551:19:04, 23 August 2005 (UTC)
541:16:23, 22 August 2005 (UTC)
530:12:00, 18 August 2005 (UTC)
211:Good idea. Best of luck. --
916:
902:03:36, 11 Mar 2005 (UTC)
747:12:07, 14 Mar 2005 (UTC)
731:09:03, 14 Mar 2005 (UTC)
615:05:41, 11 Mar 2005 (UTC)
330:There is an article from
310:PS: I found some info on
116:23:51, 17 July 2005 (UTC)
56:21:41, 28 Feb 2005 (UTC)
845:20:15, 14 Mar 2005 (UTC)
772:18:19, 14 Mar 2005 (UTC)
762:13:42, 14 Mar 2005 (UTC)
699:21:01, 13 Mar 2005 (UTC)
681:18:42, 13 Mar 2005 (UTC)
651:05:49, 12 Mar 2005 (UTC)
623:06:47, 11 Mar 2005 (UTC)
587:Plowboylifestyle's Stuff
565:http://www.tandt.be/wis/
487:17:34, 23 Mar 2005 (UTC)
412:19:03, 13 Mar 2005 (UTC)
385:There is now a draft at
207:10:37, 4 Mar 2005 (UTC)
137:08:16, 1 Mar 2005 (UTC)
81:22:24, 28 Feb 2005 (UTC)
387:Swiss coordinate system
323:08:54, 1 Mar 2005 (UTC)
305:08:25, 1 Mar 2005 (UTC)
230:09:46, 5 Mar 2005 (UTC)
215:20:15, 4 Mar 2005 (UTC)
193:03:12, 7 Jun 2005 (UTC)
174:18:42, 1 Mar 2005 (UTC)
158:18:29, 1 Mar 2005 (UTC)
146:17:33, 1 Mar 2005 (UTC)
38:(They are of the form:
895:added to the map tag.
835:
807:
372:http://www.swissgeo.ch
339:German Knowledge (XXG)
836:
787:
586:
866:, the tag includes:
784:
436:switzerland-geo-stub
374:either. -- User:Docu
365:http://map.search.ch
345:. Converters are at
251:http://map.search.ch
97:WorldWind</a: -->
643:mediawiki extension
605:mediawiki extension
517:Swiss grid as input
259:transverse Mercator
831:
62:Find this location
780:}} == {{catmore
243:coordinate system
907:
900:Plowboylifestyle
843:Plowboylifestyle
840:
838:
837:
832:
830:
829:
817:
816:
806:
801:
745:Plowboylifestyle
697:Plowboylifestyle
649:Plowboylifestyle
613:Plowboylifestyle
440:
434:
295:
294:
292:
291:
290:
285:
284:46.950°N 7.417°E
281:
278:
277:
276:
273:
915:
914:
910:
909:
908:
906:
905:
904:
852:
821:
808:
782:
781:
768:extensions. --
594:
589:
523:german proposal
519:
506:). -- User:Docu
438:
432:
288:
286:
282:
279:
274:
271:
269:
267:
266:
239:
200:
127:
91:
69:
29:
22:
21:
20:
12:
11:
5:
913:
911:
888:
887:
884:
881:
878:
877:
876:
873:
870:
851:
848:
847:
846:
828:
824:
820:
815:
811:
805:
800:
797:
794:
790:
774:
773:
764:
763:
754:
753:
724:
723:
720:
717:
705:
704:
703:
702:
701:
700:
687:
686:
685:
684:
683:
682:
669:
668:
667:
666:
665:
664:
655:
654:
653:
652:
635:
634:
633:
632:
625:
624:
593:
590:
588:
585:
584:
583:
582:
581:
580:
579:
556:
555:
554:
553:
518:
515:
514:
513:
512:
511:
510:
509:
508:
507:
493:
492:
491:
490:
489:
488:
472:
471:
470:
469:
466:
465:
464:
455:
454:
453:
452:
451:
450:
449:
448:
447:
446:
420:
419:
418:
417:
416:
415:
414:
413:
395:
394:
393:
392:
391:
390:
378:
377:
376:
375:
358:
357:
356:
355:
343:Bern#Geography
325:
324:
307:
306:
238:
235:
234:
233:
232:
231:
217:
216:
199:
196:
195:
194:
180:
179:
178:
177:
176:
175:
162:
161:
160:
159:
148:
147:
126:
123:
121:
119:
118:
105:
102:
93:
92:
89:
87:
83:
82:
71:
70:
67:
65:
33:NASA Worldwind
28:
27:NASA Worldwind
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
912:
903:
901:
896:
892:
885:
882:
879:
874:
871:
868:
867:
865:
861:
860:
859:
856:
849:
844:
826:
822:
818:
813:
809:
803:
798:
795:
792:
788:
776:
775:
771:
766:
765:
761:
756:
755:
750:
749:
748:
746:
742:
737:
732:
730:
721:
718:
715:
714:
713:
709:
698:
693:
692:
691:
690:
689:
688:
680:
675:
674:
673:
672:
671:
670:
661:
660:
659:
658:
657:
656:
650:
644:
639:
638:
637:
636:
629:
628:
627:
626:
622:
618:
617:
616:
614:
610:
606:
602:
601:template:coor
598:
591:
578:
575:
571:
566:
562:
561:
560:
559:
558:
557:
552:
549:
544:
543:
542:
539:
534:
533:
532:
531:
528:
524:
516:
505:
501:
500:
499:
498:
497:
496:
495:
494:
486:
482:
478:
477:
476:
475:
474:
473:
467:
462:
461:
459:
458:
457:
456:
444:
437:
430:
429:
428:
427:
426:
425:
424:
423:
422:
421:
411:
407:
403:
402:
401:
400:
399:
398:
397:
396:
388:
384:
383:
382:
381:
380:
379:
373:
369:
366:
362:
361:
360:
359:
353:
350:
347:
344:
340:
336:
333:
329:
328:
327:
326:
322:
317:
313:
309:
308:
304:
299:
293:
289:46.950; 7.417
265:, located at
264:
260:
256:
255:
254:
252:
248:
244:
236:
229:
225:
221:
220:
219:
218:
214:
210:
209:
208:
206:
197:
192:
188:
185:
182:
181:
173:
168:
167:
166:
165:
164:
163:
157:
152:
151:
150:
149:
145:
140:
139:
138:
136:
132:
124:
122:
117:
114:
110:
106:
103:
100:
99:
98:
88:
85:
84:
80:
76:
75:
74:
66:
63:
59:
58:
57:
55:
50:
48:
43:
41:
36:
34:
26:
19:
897:
893:
889:
863:
857:
853:
733:
725:
710:
706:
595:
520:
480:
405:
240:
201:
130:
128:
125:Brilliant...
120:
94:
72:
51:
44:
37:
30:
237:Swiss grid?
736:#mediawiki
191:NevilleDNZ
183:check out
481:region:CH
332:Swisstopo
73:* with .
570:meta:Gis
548:Ikiwaner
527:Ikiwaner
406:sessions
113:Shaddack
864:map tag
272:46°57′N
35:links?
316:CH1903
314:about
296:. The
275:7°25′E
131:http:
90:<?
16:<
770:Egil
760:Egil
743:. --
741:here
729:Egil
679:Egil
621:Egil
611:) --
597:Egil
574:Egil
538:Egil
485:Egil
443:Bern
410:Egil
321:Egil
303:Egil
263:Bern
249:and
228:Egil
205:Egil
156:Egil
135:Egil
47:here
778:-->
334:at
298:UTM
280:/
213:cfp
172:cfp
144:cfp
109:KML
79:cfp
54:cfp
49:).
789:∑
439:}}
433:{{
351:,
348:,
287:/
189:.
42:)
827:2
823:2
819:=
814:2
810:x
804:6
799:2
796:=
793:x
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.