Sunday, 10 February 2013

Big Brother edit You!

Nice text about "1984" and Wikipedia`s editing wars. Translation for not speak Russian:


Dear diary, I thought that the main character of the immortal George Orwell's "1984" has a prototype in our world - the moderator Wikipedia. Judge for yourself, it is forced by using the "updated" data edit the information in the old articles. That's how it is described in the book:
"For example, messages from" The Times "of March 17, it was clear that
In his speech on the eve of Senior Brag predicted a lull in the south Indian
front and speedy offensive Eurasia North Africa. In fact,
Eurasians actually launched an offensive in South India and North Africa
no action is taken. We had to rewrite this paragraph speech
Big Brother so that he predicted the actual course of events. Or
Again, December 19, "The Times" published an official forecast production
variety of consumer products in the fourth quarter of 1983, ie
sixth quarter ninth three-year plan. In today's issue of the printed data
actual production, and it turned out that the forecast was totally wrong.
Winston was to clarify the original figures, so that they coincide with
today. On the third sheet it was a very simple error which
can be corrected in one minute. As recently as February, the Ministry of plenty
promised (to state categorically the official terms), which in 1984
, the rate of delivery of chocolate will not diminish. In fact, as it was known, and
Winston himself, at the end of the week is going to reduce the rate from 30 to
20 grams. He had to just replace old promise advance notice,
that in April, the rate may be reduced. "
Sound familiar? Well, of course, the classic war edits, even Wikipedia describes a similar process.
Under the war meant not a single action, and the general mood of confrontation participant in regard to the content of articles. War update - is the aggressive use of update mechanism in order to win the argument about the content of the article.
When conflict management administrators often have to make decisions on the qualifications of certain actions as war edits. There are several criteria that can be used to determine the involvement of a party to war edits.
The most common criterion for the presence of the war is a violation of the participant edits the rule of three setbacks. Under this rule, the excess participant absolute limit on the number of "kickbacks" that can do in one particular article within 24 hours (three "rollback") qualifies as a war edits. This limitation, however, should not be interpreted too formal, and the fact that the party has reached (but not beyond) the limit, indicates the presence of a serious breach of conduct. Rule three setbacks should not be seen as a license to carry out "kickbacks" that are not formally covered by its action: the war of edits can be stretched for a few days or even for a longer period, they may cover several pages, although the actions of the participant thus can be within the "normal" and, finally, the problem may be that the party just used to say "roll back" to any editing, calling his displeasure.
Wars edits - it behaviors, characterized by a tendency to confrontation. This behavior is contrary to the spirit of seeking consensus, based on the discussion of the situation.
Not a war of edits "kickbacks" or vandalism edits Blocked members - at the same time, no changes are vandalism committed during the conflict over the content of the article (even if they clearly violate NPOV), and other actions, if made in good faith .
Talking about war update, we mainly have in mind the style of behavior a participant, not the number of "kickbacks", which he made on various pages for a given period of time.

By the way, a surprising number: Yandex does not want to suggest the phrase "war update" in the search query, but produces results. Google suggests search.

Saturday, 9 February 2013

Thread:Extension talk:Babel/Where is Babel.css?/reply (3)

Reply to Where is Babel.css?


New page


Very thanks!

Communication/el

Created page with "el"


New page


<languages/>

{{MediaWiki Introduction/el}}



There are several ways to get in contact with other MediaWiki users, or to get instant help. The recommended options are listed below.



{{anchor|com-landing}}

== Landing ==



This is what most MediaWiki contributors do in their first day:



* [[Special:UserLogin|Register]] and add some info about yourself in your user page.

* Follow the [[Special:MyLanguage/News|News]] and our [[Special:MyLanguage/social media|social media]] channels.

* Subscribe to [[mail:mediawiki-l|mediawiki-l]] mailing list and perhaps [[Special:MyLanguage/Mailing lists|more]].

* Join {{irc|mediawiki}} IRC channel and perhaps [[Special:MyLanguage/MediaWiki on IRC|more]].



* Make sure you have an email confirmed and email notifications enabled in your [[Special:Preferences|mediawiki.org preferences]].

* "[[Special:MyLanguage/Help:Watchlist|Watch]]" (click the star icon of) the pages you want to follow and perhaps contribute to.

* All the better if you find a [[Special:MyLanguage/Groups|MediaWiki Group]] that matches your location or interests!

{{anchor|com-chat}}

== Chat ==



[irc://irc.freenode.net/mediawiki '''#mediawiki'''] on [http://freenode.net/ irc.freenode.net] is the around-the-clock [[Special:MyLanguage/MediaWiki on IRC|IRC channel]] for realtime communication. If you don't have an IRC client, use [http://webchat.freenode.net/?channels=mediawiki web chat].



* Please read the [[Special:MyLanguage/Help:FAQ|FAQ]] before asking.

* State your problem immediately and wait for a response. Don't ask "is there anyone here" or "can someone help me". This is normal IRC etiquette and allows participants to multitask effectively.

* Expect to wait for some time for an initial response, especially in off-peak times. Despite this, out of courtesy for the volunteer who is helping you, try to answer their questions promptly.



If you don't get an answer, this could mean one of a number of things:



* Nobody was around at the time of day you chose. If the channel is generally quiet, come back later.

* You're asking a question which nobody knows the answer to, or which requires a lot of work to answer.

* You're asking a question which is in the [[Special:MyLanguage/Help:FAQ|FAQ]], the [[Special:MyLanguage/Help:Contents|help]], the [[Special:MyLanguage/Manual:Contents|manual]], or other [[Special:MyLanguage/documentation|documentation]], and the volunteers in the channel feel it would be best if you found it yourself.



Questions relating to problems with your particular installation of MediaWiki are generally best answered on IRC, since they often require a back-and-forth exchange to isolate the problem, which is tedious when performed on the mailing lists.

{{anchor|com-lists}}

== Mailing lists ==

[[Image:Wikipedians often work at night.jpg|thumb|right|Get in contact!]]

There are several [[Special:MyLanguage/mailing lists|mailing lists]] available. The recommended ones are:



* '''[[mail:mediawiki-l|mediawiki-l]]''' (or [http://dir.gmane.org/gmane.org.wikimedia.mediawiki via Gmane]) (or [news://news.gmane.org/gmane.org.wikimedia.mediawiki via your newsreader]) is the high-traffic mailing list to ask for support.

* '''[[mail:wikitech-l|wikitech-l]]''' (or [http://dir.gmane.org/gmane.science.linguistics.wikipedia.technical via Gmane]) (or [news://news.gmane.org/gmane.science.linguistics.wikipedia.technical via your newsreader]) is the high-traffic mailing list for software development, especially when it relates to Wikimedia (not just MediaWiki) wikis.

* '''[[mail:mediawiki-announce|mediawiki-announce]]''' (or [http://dir.gmane.org/gmane.org.wikimedia.mediawiki.announce via Gmane]) (or [news://news.gmane.org/gmane.org.wikimedia.mediawiki.announce via your newsreader]) is a low-traffic list for announcements of new MediaWiki releases and security updates (all messages also go to mediawiki-l).



'''Please check the archives first!'''

All three lists are also available through [http://www.gmane.org/ Gmane] which provides access as newsgroups or in various web-based formats, and includes its own archives and archive search.

<br style="clear:right;" />

{{anchor|com-twitter}}

== Twitter/Facebook/Identi.ca ==



Follow the MediaWiki accounts:

<!--T:20-->

* [https://twitter.com/#!/MediaWiki @MediaWiki] (Twitter)

* [https://identi.ca/mediawiki @MediaWiki] (Identi.ca)

* [https://www.facebook.com/MediaWikiProject MediaWiki] (Facebook)

More details at [[Special:MyLanguage/Social media|Social media]].

{{anchor|com-blog}}

== Blog ==



The '''[[m:Wikimedia Blog|Wikimedia Blog]]''' has a tech section specifically for news and information from the Wikimedia Foundation’s Technology department ([http://blog.wikimedia.org/c/technology/ link] - [http://blog.wikimedia.org/c/technology/feed RSS feed]).

{{anchor|com-news}}

== Newsletter ==



'''[[w:Wikipedia:Wikipedia Signpost|English Wikipedia's Signpost]]''' has a regular [[w:Wikipedia:Wikipedia Signpost/Single#Technology report|technology report]] with content related to activity within Wikimedia Foundation’s Technology department.

{{anchor|com-sites}}

== Websites ==



* '''[[Meta:Help:Contents|Wikimedia's Meta-Wiki]]''' was formerly where documents were managed and proposals were discussed before this site was started. There is still a lot of content there that has yet to be moved.

* '''[[Special:MyLanguage/Bugzilla|Bugzilla]]''' is where feature requests and bugs may be reported or browsed.

{{anchor|com-forums}}

== Forums ==



=== For help with the MediaWiki software ===



There is no "official" forum or discussion board, but there are some private ones, e.g. [http://www.mwusers.com/ mwusers.com] and the [http://www.facebook.com/#!/group.php?gid=2205099323 MediaWiki Developers] [[w:Facebook|Facebook]] group.



You can also post support questions at [[Project:Support desk]], though this is less frequented than the other sources of help listed on this page.



=== To discuss this site, MediaWiki.org ===



* [[Project:Current issues]]



[[Category:MediaWiki Introduction{{Langcat|Communication}}]]

[[Category:MediaWiki Communication{{Langcat|Communication}}| ]]



__NOTOC__

__NOEDITSECTION__

Επικοινωνία

Created page with "<languages/> {{MediaWiki Introduction/<translate> <!--T:1--> el</translate>}}"


New page


<languages/>

{{MediaWiki Introduction/<translate>

<!--T:1-->

el</translate>}}

User:Alinerodrigues/common.css

Created page with "'''''Texto em negrito'''''Aline Rodrigues"


New page


'''''Texto em negrito'''''Aline Rodrigues

DE:Is in

Nordrhein-Westfalen:













































← Older revisionRevision as of 22:30, 9 February 2013
Line 236:Line 236:

* Soest: is_in=


* Soest: is_in=


* Steinfurt: is_in=


* Steinfurt: is_in=

-
* Unna: is_in=

+
* Unna: is_in=Kreis Unna,Regierungsbezirk Münster,Nordrhein-Westfalen,Bundesrepublik Deutschland,Europe


* Viersen: is_in=


* Viersen: is_in=


* Warendorf: is_in=


* Warendorf: is_in=


User:Alux

Created page with "{{Userboxtop|About Me}} {{User username|Alux}} {{user United Kingdom}} {{User Hertfordshire}} {{User JOSM}} {{User Potlatch}} {{User OS|Arch}} {{User Firefox}} {{Userboxb..."


New page


{{Userboxtop|About Me}}



{{User username|Alux}}

{{user United Kingdom}}

{{User Hertfordshire}}



{{User JOSM}}

{{User Potlatch}}



{{User OS|Arch}}

{{User Firefox}}





{{Userboxbottom}}



{{babel|en|de-1}}

==Me==





==My mapping==





==My Hardware==

===Computers===

* Raspberry Pi

===Phone / GPS===

* HTC Sensation





==My software==

* Arch

* Awesome

* JOSM





[[Category:Users in Hertfordshire]]

User talk:Lutz/Historische Objekte

ext. vs. int. Link: new section


New page


== ext. vs. int. Link ==



Für Links zu Wikipedia gibt es im OSM-Wiki eine spezielle Syntax:



* ext. Link: <pre>[http://de.wikipedia.org/wiki/Weltkulturerbe Weltkulturerbe]</pre> [http://de.wikipedia.org/wiki/Weltkulturerbe Weltkulturerbe]



* int. Link: <pre>[[wikipedia:de:Weltkulturerbe|Weltkulturerbe]]</pre> [[wikipedia:de:Weltkulturerbe|Weltkulturerbe]]



letztere Schreibweise ist sogar kürzer ;) gruss --[[User:Reneman|Reneman]] ([[User talk:Reneman|talk]]) 22:20, 9 February 2013 (UTC)

User:Twermter

User account Twermter was created


Help:Extension:Translate/Page translation administration/da

Created page with "Billeder, der indeholder sprogspecifikt indhold som tekst, bør omfatte hele billedsyntaksen i en enhed. Andre billeder kan kun markere beskrivelsen med et valgfrit tip i side..."


Show changes

NL:How to map a

Translate hulp-venster from german to dutch language













































← Older revisionRevision as of 22:11, 9 February 2013
Line 5:Line 5:

Bei Widersprüchen gelten vorrangig die Bedeutungen der Attribute (s. englisch: [[Map Features]]; deutsch: [[NL:Map Features|Nederlands]]). Falls dir solche Widersprüche auffallen, gib doch bitte einen Hinweis auf der [[DE_talk:How_to_map_a|Diskussionsseite]], damit sie behoben werden können.


Bei Widersprüchen gelten vorrangig die Bedeutungen der Attribute (s. englisch: [[Map Features]]; deutsch: [[NL:Map Features|Nederlands]]). Falls dir solche Widersprüche auffallen, gib doch bitte einen Hinweis auf der [[DE_talk:How_to_map_a|Diskussionsseite]], damit sie behoben werden können.


|}


|}

- +

Im Gegensatz zu den [[De:Map_Features|Map Features]], wo nach Attributen (oder ''Eigenschaften'', englisch: tags) sortiert wird, ist diese '''Liste nach den Objekten sortiert''', die man in der realen Welt vorfindet. Die realen Objekte werden meist durch mehrere Attribute repräsentiert, beispielsweise ein Fluss durch seinen Namen und seine Breite und ob Schiffe darauf fahren. Manchmal gibt es auch mehrere Möglichkeiten, etwas zu beschreiben, beispielsweise einen Kreisverkehr als kreisförmigen Weg oder als Minikreisverkehr, oder einen Point-of-Interest als Punkt oder als Fläche. Hier sind immer alle Möglichkeiten aufgeführt, und es wird erklärt, wann genau welche Möglichkeit zu wählen ist. Im Zweifelsfall ist die jeweils erste Angabe zu verwenden.


Im Gegensatz zu den [[De:Map_Features|Map Features]], wo nach Attributen (oder ''Eigenschaften'', englisch: tags) sortiert wird, ist diese '''Liste nach den Objekten sortiert''', die man in der realen Welt vorfindet. Die realen Objekte werden meist durch mehrere Attribute repräsentiert, beispielsweise ein Fluss durch seinen Namen und seine Breite und ob Schiffe darauf fahren. Manchmal gibt es auch mehrere Möglichkeiten, etwas zu beschreiben, beispielsweise einen Kreisverkehr als kreisförmigen Weg oder als Minikreisverkehr, oder einen Point-of-Interest als Punkt oder als Fläche. Hier sind immer alle Möglichkeiten aufgeführt, und es wird erklärt, wann genau welche Möglichkeit zu wählen ist. Im Zweifelsfall ist die jeweils erste Angabe zu verwenden.


Template:NL:Hulp-venster















































← Older revisionRevision as of 22:10, 9 February 2013
(One intermediate revision by one user not shown)
Line 7:Line 7:

* [[de:Potlatch|Editor Potlatch]]


* [[de:Potlatch|Editor Potlatch]]


* [[de:JOSM|Editor JOSM]]


* [[de:JOSM|Editor JOSM]]

-
* [[nl:Howto Map A|ABC van objecten]]

+
* [[nl:How to map a|ABC van objecten]]


* [[de:Map Features|Object-eigenschappen]]


* [[de:Map Features|Object-eigenschappen]]


----


----


Template:NL:Hulp-venster

Initial help box for dutch language


New page


{| border="2" cellspacing="0" cellpadding="4" style="float:right; background:#dfd; clear:right; width:180px; margin:1em 0 1em 1em; border-style:solid; border-width:1px; border-collapse:collapse; font-size:90%; empty-cells:show; margin-top:0;"

! [[Hulp]]

|-

|

* [[de:Browsing|Hulp voor kaartgebruikers]]

----

* [[de:Potlatch|Editor Potlatch]]

* [[de:JOSM|Editor JOSM]]

* [[nl:Howto Map A|ABC van objecten]]

* [[de:Map Features|Object-eigenschappen]]

----

* [http://forum.openstreetmap.org/viewforum.php?id=14 OSM-Forum]

* [http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-de Mailing-Liste]

|}

Tendring(Essex District)

Civil Parishes in the Tendring District:

















































































































← Older revisionRevision as of 22:06, 9 February 2013
Line 149:Line 149:

| Great Oakley Civil Parish || '''{{BrowseRelation|76714}}''' ||


| Great Oakley Civil Parish || '''{{BrowseRelation|76714}}''' ||


|-


|-

-
| Harwich Civil Parish || '''{{BrowseRelation|76699}}''' || Started

+
| Harwich Civil Parish || '''{{BrowseRelation|76699}}''' || Complete


|-


|-


| Lawford Civil Parish || '''{{BrowseRelation|76800}}''' || Complete


| Lawford Civil Parish || '''{{BrowseRelation|76800}}''' || Complete

Line 159:Line 159:

| Little Clacton Civil Parish || '''{{BrowseRelation|76866}}''' || Started


| Little Clacton Civil Parish || '''{{BrowseRelation|76866}}''' || Started


|-


|-

-
| Little Oakley Civil Parish || '''{{BrowseRelation|76709}}''' ||

+
| Little Oakley Civil Parish || '''{{BrowseRelation|76709}}''' || Complete


|-


|-


| Manningtree Civil Parish || '''{{BrowseRelation|76799}}''' || Complete


| Manningtree Civil Parish || '''{{BrowseRelation|76799}}''' || Complete

Line 165:Line 165:

| Mistley Civil Parish || '''{{BrowseRelation|76797}}''' || Complete


| Mistley Civil Parish || '''{{BrowseRelation|76797}}''' || Complete


|-


|-

-
| Ramsey and Parkeston Civil Parish || '''{{BrowseRelation|76703}}''' ||

+
| Ramsey and Parkeston Civil Parish || '''{{BrowseRelation|76703}}''' || Started (bit off Oakley Road)


|-


|-


| St Osyth Civil Parish || '''{{BrowseRelation|76858}}''' || Started


| St Osyth Civil Parish || '''{{BrowseRelation|76858}}''' || Started


FR:Servers/Hardware

orth












































































































































































← Older revisionRevision as of 21:59, 9 February 2013
(One intermediate revision by one user not shown)
Line 1:Line 1:
-
Liste matériel des différents serveur de l'association OSM-FR et remerciement à leur donnateurs

+
Liste matérielle des différents serveurs de l'association OSM-FR et remerciements à leur donateurs


= Dons de la Fondation d'Entreprise Free =


= Dons de la Fondation d'Entreprise Free =

Line 7:Line 7:

!| Source


!| Source


!| Logo


!| Logo

-
!| Configuration Matériel

+
!| Configuration Matérielle


!| Description


!| Description


|-


|-

Line 17:Line 17:

* [[#Dell R610|Dell R610]]


* [[#Dell R610|Dell R610]]


||


||

-
La [http://fondation.free.org/ Free Foundation] a donnée initialement 20 serveurs pour Open Street Map France. Les serveurs sont la propriété de [http://login.univ-nantes.fr login] jusqu'a ce que l'association soit créée.

+
La [http://fondation.free.org/ Free Foundation] a donné initialement 20 serveurs pour OpenStreetMap France. Les serveurs sont la propriété de [http://login.univ-nantes.fr login] jusqu'à ce que l'association soit créée.


En Mars 2012, 3 nouveaux serveurs (Dell R610) ont été donnés par la [http://fondation.free.org/ Fondation d'Entreprise Free] à l'association OpenStreetMap France.


En Mars 2012, 3 nouveaux serveurs (Dell R610) ont été donnés par la [http://fondation.free.org/ Fondation d'Entreprise Free] à l'association OpenStreetMap France.

Line 67:Line 67:

!| Source


!| Source


!| Logo


!| Logo

-
!| Configuration Matériel

+
!| Configuration Matérielle


!| Description


!| Description


|-


|-

Line 73:Line 73:

= Don du Pôle Aquinetic =


= Don du Pôle Aquinetic =

-
Les serveurs sont la propriété de [http://login.univ-nantes.fr login] jusqu'a ce que l'association soit créée.

+
Les serveurs sont la propriété de [http://login.univ-nantes.fr login] jusqu'à ce que l'association soit créée.


|-


|-


|| [http://pole-aquinetic.fr/ Pôle Aquinetic]


|| [http://pole-aquinetic.fr/ Pôle Aquinetic]


NL:How to map a

Add link to "overlegpagina" and completed translation from german to dutch of this section

























































← Older revisionRevision as of 21:52, 9 February 2013
Line 18:Line 18:

== Zoeken met <CTRL-F> ==


== Zoeken met <CTRL-F> ==

-
Wenn du einen Begriff gezielt suchen willst, drück die <Strg>-Taste und gleichzeitig die Taste <F>. Die <Strg>-Taste heißt auf nicht-deutschen Tastaturen auch <Ctrl>. Auf deinem Browser erscheint dann ein Suchfeld. Dort gibst du den Suchbegriff ein, beispielsweise „Fahrradweg“ oder allgemeiner „Fahrrad“. Mit „Abwärts“ und „Aufwärts“ findest du hier jeden Eintrag zum Thema.

+
Wanneer je op zoek bent naar een specifiek onderwerp, kan je met <CTRL>-F een zoek venster openen. In dit venster kan je het onderwerp waarnaar je op zoek bent ingeven, bijvoorbeeld "Afvalcontainer" of meer algemeen "Afval". Met de "Previous" of "Next" knoppen kan je de zoekopdracht opnieuw starten waarbij naar de vorige of volgende locatie wordt gegaan van het gevraagde onderwerp.

-
Deze pagina is nog in opbouw. Wanneer je iets zoekt dat nog niet beschikbaar kan je een aanvraag doen op [[DE_talk:How_to_map_a|Diskussionsseite]], mogelijk wordt deze dan zo snel mogelijk toegevoegd;-)

+
Deze pagina is nog in opbouw. Wanneer je iets zoekt dat nog niet beschikbaar is kan je een aanvraag doen op [[NL_talk:How_to_map_a|Overlegpagina]], mogelijk wordt deze dan zo snel mogelijk toegevoegd;-)


== Alfabetisch zoeken ==


== Alfabetisch zoeken ==


Участник:Lsdsubrosa

новый участник


Участник:Nikita0506

новый участник


Thread:Project:Support desk/Wiki page Log in brings up 500 error

New thread: Wiki page Log in brings up 500 error


New page


I am at a loss here. I have a wiki page (www.wikazine.com). It loads fine but for some reason when I click on "Log on" the system comes back with a 500 Internal Server Error.



Since I didn't do any upgrades to this site I thought I might have been hacked. I checked access logs and found no problem.



I was on an older load so I updated the system to 1.20.2. The install went fine but I still cannot log in.



Tried on another computer, tried on another browser.



I am also getting weird Database errors but I think that is because I haven't logged in to update the database.



Any help would be appreciated.

User:Geekazine

User account Geekazine was created


London/Winter 2012-2013 Pub Meetup

Next one Blue Posts Tue 19th: link lanyrd listing













































← Older revisionRevision as of 21:47, 9 February 2013
Line 6:Line 6:

The next pub meet-up will be '''Tuesday February 19th at the Blue Posts pub''' near Oxford Street / Tottenham court road area ([http://www.openstreetmap.org/?mlat=51.51698&mlon=-0.135471&zoom=18&layers=M map]) Warning: There is another "blue posts" pub not so far away. Go to right one!


The next pub meet-up will be '''Tuesday February 19th at the Blue Posts pub''' near Oxford Street / Tottenham court road area ([http://www.openstreetmap.org/?mlat=51.51698&mlon=-0.135471&zoom=18&layers=M map]) Warning: There is another "blue posts" pub not so far away. Go to right one!

-
<!--You can set yourself as 'attending' on [http://lanyrd.com/2012/osmlondon-nov1/ the lanyrd listing]-->

+
You can set yourself as 'attending' on [http://lanyrd.com/2013/openstreetmap-19feb-pub/ the lanyrd listing]


We'll '''meet at the pub at 7:00p.m.'''


We'll '''meet at the pub at 7:00p.m.'''


Talk:WikiProject Belgium/Activities

What was discussed:













































← Older revisionRevision as of 21:43, 9 February 2013
Line 51:Line 51:

* Developing apps on OSM.


* Developing apps on OSM.


* Create a HowToMap page similar to the german page: [http://wiki.openstreetmap.org/wiki/NL:How_to_map_a here] is the new NL translation but translation just started.


* Create a HowToMap page similar to the german page: [http://wiki.openstreetmap.org/wiki/NL:How_to_map_a here] is the new NL translation but translation just started.

-
* Mapping of GAS-stations.

+
* Mapping of fuel stations.


==2011-05-13: 5th Informal Talk, ASBL Barricade, Liege ==


==2011-05-13: 5th Informal Talk, ASBL Barricade, Liege ==


NL talk:How to map a

Initial version of this discussion page


New page


Ontbrekende objecten op de Nederlandse versie van de "How to map a" wiki pagini...start hier de discussie

AT/Kärnten/Landesstraßen

L76 ..L80

















































































































← Older revisionRevision as of 21:41, 9 February 2013
Line 892:Line 892:

| Von der Kärntner Straße (B83) in Töschling über Sekull zum Gemeindeamt in St. Martin am Techelsberg


| Von der Kärntner Straße (B83) in Töschling über Sekull zum Gemeindeamt in St. Martin am Techelsberg


|


|

- +

|


|


|


|

Line 901:Line 901:

| Von der Turracher Straße (B95) in Vorwald zum Ende der Liftparkplätze beim Falkertsee


| Von der Turracher Straße (B95) in Vorwald zum Ende der Liftparkplätze beim Falkertsee


|


|

- +

|


|


|


|

Line 910:Line 910:

| Von der Gurktal Straße (B93) nördlich Feldkirchen in Kärnten, entlang dem Goggausee und über den Zammelsberg zur Gurktal Straße (B93) in Weitensfeld


| Von der Gurktal Straße (B93) nördlich Feldkirchen in Kärnten, entlang dem Goggausee und über den Zammelsberg zur Gurktal Straße (B93) in Weitensfeld


|


|

- +

|


|


|


|


Thread:Extension talk:Maps/New install issues/reply (4)

Reply to New install issues


New page


[http://www.fortwiki.com/Map_Test_Page Test Page] Open layers seems to work great and google maps works in map editor and preview but not in regular page view.

Template:Platform Status

nominatim is back

































← Older revisionRevision as of 21:27, 9 February 2013
Line 1:Line 1:
-
<span style='background-color:yellow'>Nominatim updates disabled</span>

+
<span style='background-color:lime'>Up and running</span>


<noinclude>


<noinclude>


<!--


<!--


NL:How to map a

Ampel:









































































































← Older revisionRevision as of 21:26, 9 February 2013
Line 205:Line 205:

:''siehe [[#Rettungswache|Rettungswache]]''


:''siehe [[#Rettungswache|Rettungswache]]''

-
=== Ampel ===

+
=== Verkeerslichten ===


{| width=100%


{| width=100%


| width=160px valign=top | [[Image:Ampel.jpg|150px]]


| width=160px valign=top | [[Image:Ampel.jpg|150px]]

-
| width=300px valign=top | [[Image:Mf_node.png]] Punkt

+
| width=300px valign=top | [[Image:Mf_node.png]] Knoop

-
<br/>+ {{Tag|crossing||traffic_signals}} für Fußgänger- und Radfahrerübergänge mit Ampel

+
<br/>+ {{Tag|crossing||traffic_signals}} voor voetgangers en fietsenoversteekplaat met verkeerslichten

-
<br/>+ {{Tag|highway|traffic_signals}} für beampelte Autokreuzungen

+
<br/>+ {{Tag|highway|traffic_signals}} voor kruispunten met verkeerslichten

-
| valign=top | '''Anmerkungen:'''

+
| valign=top | '''Opmerkingen:'''

-
* Siehe auch: [[Key:crossing]]

+
* Zie ook: [[Key:crossing]]

-
* Blindenampeln siehe [[key:traffic_signals:sound]]

+
* Verkeerslichten voor blinden zie [[key:traffic_signals:sound]]


|}


|}


WikiProject Poland/Śląskie/Komunikacja miejska

Added route for line 51













































← Older revisionRevision as of 21:25, 9 February 2013
Line 177:Line 177:

| 50 || Katowice Plac Wolności - Siemianowice Powstańców Pętla || || {{Relation|tools=short|}} || {{KZK GOP|50}}


| 50 || Katowice Plac Wolności - Siemianowice Powstańców Pętla || || {{Relation|tools=short|}} || {{KZK GOP|50}}


|-


|-

-
| 51 || Katowice Ligota Akademiki - Katowice Osiedle Tysiąclecia Pętla || || {{Relation|tools=short|}} || {{KZK GOP|51}}

+
| 51 || Katowice Ligota Akademiki - Katowice Osiedle Tysiąclecia Pętla || {{progress|100}} || {{Relation|tools=short|2749436}} || {{KZK GOP|51}}


|-


|-


| 52 || Wojkowice Park - Bytom Dworzec PKP || {{progress|100}} || {{Relation|tools=short|1975567}} || {{KZK GOP|52}}


| 52 || Wojkowice Park - Bytom Dworzec PKP || {{progress|100}} || {{Relation|tools=short|1975567}} || {{KZK GOP|52}}


Platform Status

fixed poldi













































← Older revisionRevision as of 21:23, 9 February 2013
Line 62:Line 62:

|[[Nominatim]] || Search / Geo-coding


|[[Nominatim]] || Search / Geo-coding


|| [[Servers/poldi|poldi]]


|| [[Servers/poldi|poldi]]

-
{{yellow|no updates}} || updates stopped due to problems with 64-bit node IDs.

+
{{OK}} ||


|-


|-


|[[Mailing lists|mail]] || Mailing lists & SVN server


|[[Mailing lists|mail]] || Mailing lists & SVN server


NL:How to map a

Translation from german to dutch













































← Older revisionRevision as of 21:19, 9 February 2013
Line 22:Line 22:

Diese Seite ist noch im Entstehen. Wenn du hier etwas suchst, das noch nicht verzeichnet ist, kannst du es auf der [[DE_talk:How_to_map_a|Diskussionsseite]] eintragen, möglicherweise wird es dann in den nächsten Tagen ergänzt… ;-)


Diese Seite ist noch im Entstehen. Wenn du hier etwas suchst, das noch nicht verzeichnet ist, kannst du es auf der [[DE_talk:How_to_map_a|Diskussionsseite]] eintragen, möglicherweise wird es dann in den nächsten Tagen ergänzt… ;-)

-
== Alphabetische Suche ==

+
== Alfabetisch zoeken ==


__NOTOC__


__NOTOC__


Osm2pgsql/benchmarks

Best Results:













































← Older revisionRevision as of 21:18, 9 February 2013
Line 132:Line 132:

"current" (2011/2012) size full planet import


"current" (2011/2012) size full planet import

-
With Revodrive PCIe SSD on Dell R610: '''6.8h''' (with planet-130130)

+
With Revodrive PCIe SSD on Dell R610:[[Osm2pgsql/benchmarks/Dell_R610_import_revodrive | '''6.8h''']] (with planet-130130)


With SSD(s) [[Osm2pgsql/benchmarks#No_hstore | '''11.1h''']]


With SSD(s) [[Osm2pgsql/benchmarks#No_hstore | '''11.1h''']]


Key:wires


































































← Older revisionRevision as of 21:18, 9 February 2013
Line 14:Line 14:

}}


}}

-
To describe the number of wires (better: [http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-21 sub-conductors]) per power cable (better: [http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-20 bundle conductor]) of an [http://en.wikipedia.org/wiki/Overhead_power_line overhead power line].

+
To describe the number of wires (better: [http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-21 sub-conductors]) per power cable (better: [http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-20 conductor bundle]) of an [http://en.wikipedia.org/wiki/Overhead_power_line overhead power line].


== Background ==


== Background ==

Line 79:Line 79:

== A note on terminology ==


== A note on terminology ==

-
The names of the keys {{tag|wires}} and {{tag|cables}} may have been chosen a little bit unfortunate. The more common term for "wire" is ''sub-conductor'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-21 IEV ref 466-10-21]) of a ''conductor bundle'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-20 IEV ref 466-10-20]). A ''single conductor'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-19 IEV ref 466-10-19]) corresponds to {{tag|wires||single}}. Similarly {{tag|wires||double}}, {{tag|wires||triple}} and {{tag|wires||quad}} correspond to ''twin'', ''triple'' and ''quad bundle'', respectively. See also [http://en.wikipedia.org/wiki/Overhead_power_line#Conductors Wikipedia on conductors]

+
The names of the keys {{tag|wires}} and {{tag|cables}} may have been chosen a little bit unfortunate. The more common term for "wire" is ''sub-conductor'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-21 IEV ref 466-10-21]) of a ''conductor bundle'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-20 IEV ref 466-10-20]). A ''single conductor'' ([http://www.electropedia.org/iev/iev.nsf/display?openform&ievref=466-10-19 IEV ref 466-10-19]) corresponds to {{tag|wires||single}}. Similarly ''twin bundle'', ''triple bundle'' and ''quad bundle'' correspond to {{tag|wires||double}}, {{tag|wires||triple}} and {{tag|wires||quad}}, respectively. See also [http://en.wikipedia.org/wiki/Overhead_power_line#Conductors Wikipedia on conductors].


NL:How to map a

Hondenzakjes automaat:

























































← Older revisionRevision as of 21:16, 9 February 2013
Line 96:Line 96:

<br/>+&nbsp;{{Tag|operator}}


<br/>+&nbsp;{{Tag|operator}}


| valign=top | '''Opmerking:'''


| valign=top | '''Opmerking:'''

-
* {{Tag|fee}} te gebruiken wanneer de hondenzakjes gratis ter beschikking worden gesteld.

+
* {{Tag|fee}} te gebruiken om aan te geven of de hondenzakjes gratis ter beschikking worden gesteld.


* {{Tag|operator}} ''optionele'' tag die aangeeft wie het aanvullen van de hondenzakjes voor zijn rekening neemt.


* {{Tag|operator}} ''optionele'' tag die aangeeft wie het aanvullen van de hondenzakjes voor zijn rekening neemt.

-
* {{Tag|waste_basket:excrement_bags|yes}} - nog niet 100% bepaald, andere varianten:

+
* {{Tag|waste_basket:excrement_bags|yes}} - nog onder discussie, andere varianten:


** {{Tag|amenity|waste_basket}} + {{Tag|waste|dog_excrement}}, of nog


** {{Tag|amenity|waste_basket}} + {{Tag|waste|dog_excrement}}, of nog


** {{Tag|amenity|dog_bin}}, {{Tag|amenity|dog_waste_bin}}, {{Tag|amenity|dog_waste}}


** {{Tag|amenity|dog_bin}}, {{Tag|amenity|dog_waste_bin}}, {{Tag|amenity|dog_waste}}


Osm2pgsql/benchmarks/Dell R610 import revodrive

Created page with "<source lang="bash"> osm2pgsql SVN version 0.81.0 (64bit id space) Using projection SRS 900913 (Spherical Mercator) Setting up table: planet_osm_point NOTICE: table "planet_..."


New page


<source lang="bash">

osm2pgsql SVN version 0.81.0 (64bit id space)



Using projection SRS 900913 (Spherical Mercator)

Setting up table: planet_osm_point

NOTICE: table "planet_osm_point" does not exist, skipping

NOTICE: table "planet_osm_point_tmp" does not exist, skipping

Setting up table: planet_osm_line

NOTICE: table "planet_osm_line" does not exist, skipping

NOTICE: table "planet_osm_line_tmp" does not exist, skipping

Setting up table: planet_osm_polygon

NOTICE: table "planet_osm_polygon" does not exist, skipping

NOTICE: table "planet_osm_polygon_tmp" does not exist, skipping

Setting up table: planet_osm_roads

NOTICE: table "planet_osm_roads" does not exist, skipping

NOTICE: table "planet_osm_roads_tmp" does not exist, skipping

Allocating memory for dense node cache

Allocating dense node cache in one big chunk

Allocating memory for sparse node cache

Sharing dense sparse

Node-cache: cache=16000MB, maxblocks=2048001*8192, allocation method=11

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Allocated space for persistent node cache file

Maximum node in persistent node cache: 0

Mid: pgsql, scale=100 cache=16000

Setting up table: planet_osm_nodes

NOTICE: table "planet_osm_nodes" does not exist, skipping

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_nodes_pkey" for table "pla

net_osm_nodes"

Setting up table: planet_osm_ways

NOTICE: table "planet_osm_ways" does not exist, skipping

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_ways_pkey" for table "planet_osm_ways"

Setting up table: planet_osm_rels

NOTICE: table "planet_osm_rels" does not exist, skipping

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_rels_pkey" for table "planet_osm_rels"



Reading in file: /home/jocelyn/planet-130130.osm.pbf

Processing: Node(1755043k 1513.0k/s) Way(167918k 27.66k/s) Relation(1782000 334.71/s) parse time: 12554s



Node stats: total(1755043102), max(2134381692) in 1160s

Way stats: total(167918844), max(203427217) in 6070s

Relation stats: total(1782000), max(2730466) in 5324s

Committing transaction for planet_osm_point

Committing transaction for planet_osm_line

Committing transaction for planet_osm_polygon

Committing transaction for planet_osm_roads



Going over pending ways...

Maximum node in persistent node cache: 2134900735

99602563 ways are pending

Using 10 helper-processes

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Helper process 0 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 9 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 2 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 6 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 3 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 7 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 4 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 8 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 1 out of 10 initialised

processing way (0k) at 0.00k/s (done 0 of 10)Helper process 5 out of 10 initialised

Process 0 finished processing 9960257 ways in 3729 sec

Process 1 finished processing 9960257 ways in 3741 sec

processing way (99184k) at 26.52k/s (done 2 of 10)Maximum node in persistent node cache: 2134900735

Process 7 finished processing 9960256 ways in 3747 sec

Maximum node in persistent node cache: 2134900735

Process 3 finished processing 9960256 ways in 3747 sec

Maximum node in persistent node cache: 2134900735

Process 5 finished processing 9960256 ways in 3749 sec

Maximum node in persistent node cache: 2134900735

Process 9 finished processing 9960256 ways in 3754 sec

Maximum node in persistent node cache: 2134900735

Process 2 finished processing 9960257 ways in 3755 sec

Maximum node in persistent node cache: 2134900735

Process 8 finished processing 9960256 ways in 3755 sec

Maximum node in persistent node cache: 2134900735

Process 4 finished processing 9960256 ways in 3766 sec

Maximum node in persistent node cache: 2134900735

Process 6 finished processing 9960256 ways in 3788 sec

Maximum node in persistent node cache: 2134900735



All child processes exited



99602563 Pending ways took 3788s at a rate of 26294.24/s

Committing transaction for planet_osm_point

Committing transaction for planet_osm_line

Committing transaction for planet_osm_polygon

Committing transaction for planet_osm_roads



Going over pending relations...

Maximum node in persistent node cache: 2134900735

0 relations are pending



Using 10 helper-processes

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Mid: loading persistent node cache from /ssd/osm2pgsql/flat-nodes.raw

Maximum node in persistent node cache: 2134900735

Process 0 finished processing 0 relations in 3 sec

Process 9 finished processing 0 relations in 3 sec

Maximum node in persistent node cache: 2134900735

Process 5 finished processing 0 relations in 3 sec

Maximum node in persistent node cache: 2134900735

Process 1 finished processing 0 relations in 3 sec

Maximum node in persistent node cache: 2134900735

Process 6 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735

Process 2 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735

Process 7 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735

Process 3 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735

Process 8 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735

Process 4 finished processing 0 relations in 4 sec

Maximum node in persistent node cache: 2134900735



All child processes exited

0 Pending relations took 4s at a rate of 0.00/s



node cache: stored: 1755043102(100.00%), storage efficiency: 86.55% (dense blocks: 1857756, sparse nodes: 62738887), hit rate: 100.00%

Sorting data and creating indexes for planet_osm_line

Sorting data and creating indexes for planet_osm_roads

Sorting data and creating indexes for planet_osm_polygon

Sorting data and creating indexes for planet_osm_point

Maximum node in persistent node cache: 2134900735

Stopping table: planet_osm_nodes

Stopping table: planet_osm_ways

Stopping table: planet_osm_rels

Building index on table: planet_osm_ways (fastupdate=off)

Building index on table: planet_osm_rels (fastupdate=off)

Stopped table: planet_osm_nodes in 0s

Analyzing planet_osm_polygon finished

Analyzing planet_osm_point finished

Analyzing planet_osm_roads finished

Analyzing planet_osm_line finished

Stopped table: planet_osm_rels in 42s

Copying planet_osm_point to cluster by geometry finished

Copying planet_osm_roads to cluster by geometry finished

Creating indexes on planet_osm_roads finished

All indexes on planet_osm_roads created in 1190s

Completed planet_osm_roads

Creating indexes on planet_osm_point finished

All indexes on planet_osm_point created in 1629s

Completed planet_osm_point

Copying planet_osm_polygon to cluster by geometry finished

Copying planet_osm_line to cluster by geometry finished

Creating indexes on planet_osm_polygon finished

All indexes on planet_osm_polygon created in 6547s

Completed planet_osm_polygon

Creating indexes on planet_osm_line finished

All indexes on planet_osm_line created in 6986s

Completed planet_osm_line

Stopped table: planet_osm_ways in 8255s



Osm2pgsql took 24604s overall

</source>