This is a documentation subpage for Template:OverpassTurboStolpersteine.|
It contains usage information, categories and other content that is not part of the original template page.
With this template you can generate a link to an Overpass turbo query, which shows all Stolpersteine in a specific area. This is mainly used on DE:Städte mit Stolpersteinen. In most cases you just need to set the name of your city. If this doesn't work as espected (because there are several cities with the same name), you can set the admin_level of the administrative boundary to be more precise. Alternativly you can exactly define the area by entering the OSM-ID of the administrative boundary. You can also define your own area by entering the corner coordinates. There are also several optional parameters for customizing the result.
Please write to User:Klumbumbus, if you have any suggestions or questions to this template.
|Required parameter (to define the area)|
|name||The name of the administrative boundary in which you want to search for Stolpersteine e.g. the name of your town or city.|| Note : you no longer need to replace spaces by a plus sign, as in "name=Frankfurt+am+Main"; |
and you no longer need to URL-encoded other non-ASCII characters, as in "name=Baden-W%C3%BCrttemberg"
In presence of any "+" or "%", the name given is assumed to be already URL-encoded for HTTP query strings.
|relation||The OSM-ID of a relation which defines an area, e.g. the OSM-ID of the administrative boundary relation of your town or city.|
|way||The OSM-ID of a way which defines an area.||This works only for closed ways which also have a name. For further information see here.|
|coordinates||You can specify a custom area with three or more points.||Type for each point lat and lon separated by a plus sign (+) or space ( ). Use a dot (.) as decimal separator. Example: coordinates=50.0+7.0+51.0+7.0+51.0+8.0|
|admin_level||This defines the number of the admin_level of the administrative boundary. Use this only together with name.||You can use this if you don't get the correct result by just adding the name, e.g because of several towns with the same name. Alternatively you can use relation, way or coordinates.|
|lg||The language of the mouseover text of the link.|| Currently beside english only german (de) is supported. Please let me know if you want to add your language to the template, or add it yourself if you are familiar with template editing.
|icon||If set to "yes" Overpass turbo will display a Stolperstein icon for each Stolperstein. You can also enter the URL of any other icon.||If you don't want to display an icon do not set icon=no but ommit the icon parameter completely. The default blue circle with yellow fill is used then.|
|text||This will add a text label to each Stolperstein. The text is the value of the osm-key you define in this parameter.||Examples: If you set text=name then the text label shows the name of the Stolperstein. If you set text=memorial:ref, then the text label shows the value of memorial:ref of the Stolperstein.|
|display area||If set to yes, the map will also show the area in which the Stolpersteine were searched.||If you use this and export the data to an external editor (e.g. JOSM), you will not just export the Stolperstein nodes, but also the complete area relation with all its ways with all their nodes! Also note that if you use this the number of POIs shown down right in the corner of the Overpass turbo map is no longer the number of Stolpersteine! There are also counted nodes of the area relation which have at least one tag (these nodes are hidden on the map for better view). With this parameter you can check if the area in which Overpass api searches for Stolpersteine is correct. For example if you use name=Berlin|display area=yes , you will see, that beside the capital of germany there are also some cities in the USA, with the name Berlin (you may check Don't display small features as POIs in the settings of Overpass turbo to see these areas on low zoom). In this case Overpass api searches also in these areas. To avoid this you can either add admin_level=4 or use relation=62422 instead of name. This parameter does not work if you use coordinates.|
|run on load||If set to "no" the query will not run automatically, when you click on the link.||If the query runs automatically on load and it finds data, then also the map automatically jumps to the position of the data. Otherwise you need to set lat/lon/zoom or the user needs to use the zoom to data button after manually running the query. This parameter is ignored if fullscreen=yes is set.|
|lat||The latitude.||If you do not automatically run on load, you can specify the latitude of the center of the shown map. If you use this you also need to use lon and zoom. This parameter is ignored if fullscreen=yes is set.|
|lon||The longitude.||If you do not automatically run on load, you can specify the longitude of the center of the shown map. If you use this you also need to use lat and zoom. This parameter is ignored if fullscreen=yes is set.|
|zoom||The zoom level.||If you do not automatically run on load, you can specify the zoom level of the shown map. If you use this you also need to use lat and lon. This parameter is ignored if fullscreen=yes is set.|
|fullscreen||If set to "yes" the query will load on a fullscreen map.||This means all the overpass turbo buttons and the side panel with the query code are hidden. The query always runs automatically on load because there is no run button.|
|json||If set to "yes" the output data will be in json format instead of xml.||If you want to export the data to JOSM you need the xml format. This parameter is not useful in combination with fullscreen since there is no export button on fullscreen map.|
|meta||If set to "no" the tool tip which appears when you click on a Stolperstein in Overpass turbo will not display the meta data of the node.||Meta data is: timestamp, version, changeset, user name and user id.|
|date||Instead searching for Stolpersteine in the current state of the database, you can specify a date in the past.||Example: 2012-09-14T15:00:00Z This processes the query as if it were posed on 14th September 2012 at 15:00.|
|diff1||This parameter lets the database determine the difference of two queries at different points in the past.||Example: 2013-12-12T15:00:00Z This processes the query as if it were posed on 12th December 2013 at 15:00, then processes the same query with current data and finally outputs the difference between the two results. If you want to use a second date in the past instead of the comparison with the current state, then use the parameter diff2 for the second date. Note that you will not be able to export the received data to JOSM.|
|diff2||The Second date in the past.||If unset, then diff1 will use the current state as second date. Example: 2013-12-15T15:00:00Z Together with diff1=2013-12-12T15:00:00Z this processes the query as if it were posed on 12th December 2013 at 15:00, then processes the same query as if it were posed on 14th December 2013 at 15:00 and finally outputs the difference between the two results. Note that you will not be able to export the received data to JOSM. You can use this for example if you just want to display the Stolpersteine of the last laying.|
|adiff1||Similar to diff2.||The adiff does basically the same like diff, but for all elements that aren't contained in the newer result, it is indicated what happened to them. This is printed if you switch from map tab do data tab top right in Overpass turbo. If an element has been deleted, then its last deletion date is printed and the indication "visible=false". If an element has changed such that it no longer matches the query then its last change date is printed and the indication "visible=true". This does not work for json as output format.|
|adiff2||Similar to diff2.|