[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:dc="" xmlns:geo="" xmlns:georss="">
  3.  <channel>
  4.    <title>OpenStreetMap diary entries</title>
  5.    <description>Recent diary entries from users of OpenStreetMap</description>
  6.    <link></link>
  7.    <image>
  8.      <url></url>
  9.      <title>OpenStreetMap diary entries</title>
  10.      <width>100</width>
  11.      <height>100</height>
  12.      <link></link>
  13.    </image>
  14.    <item>
  15.      <title>Verifica localização</title>
  16.      <link></link>
  17.      <guid></guid>
  18.      <description>&lt;p&gt;Teste do aparelho&lt;/p&gt;
  20. </description>
  21.      <dc:creator>Reginaldo Oliveira Pereira</dc:creator>
  22.      <pubDate>Fri, 03 Jul 2020 22:44:43 +0000</pubDate>
  23.      <comments></comments>
  24.    </item>
  25.    <item>
  26.      <title>Pedestrianisation of streets in Ireland</title>
  27.      <link></link>
  28.      <guid></guid>
  29.      <description>&lt;p&gt;As businesses start re-opening, local authorities in Ireland are supporting businesses to adhere to government health advice and specifically social distancing techniques which have been shown to slow the spread of the disease.&lt;/p&gt;
  31. &lt;p&gt;One of the most visual supports is the pedestrianisation of streets for specific hours of the day / week so cafés and restaurants can make use of the outdoor space (risk of infection is lower if people are eating outside). Unlike continental Europe and parts of the USA, pavilions and street dining is not common here.&lt;/p&gt;
  33. &lt;p&gt;OpenStreetMap contributors are keeping up with the local authority efforts by updating map data as changes are made.&lt;/p&gt;
  35. &lt;p&gt;Most of these updates make use of the conditional access key/values outlined in &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  37. &lt;p&gt;Here’s an example change in Cork, Ireland that I did earlier today: &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  39. &lt;p&gt;Note: the logic is that motor vehicles can’t access the street UNLESS it’s between 17:30 and 11:00 (i.e. the inverse of the pedestrianisation period).&lt;/p&gt;
  41. </description>
  42.      <dc:creator>dónal</dc:creator>
  43.      <pubDate>Fri, 03 Jul 2020 18:10:46 +0000</pubDate>
  44.      <comments></comments>
  45.      <geo:lat>51.8978319929996</geo:lat>
  46.      <geo:long>-8.47090593375569</geo:long>
  47.      <georss:point>51.8978319929996 -8.47090593375569</georss:point>
  48.    </item>
  49.    <item>
  50.      <title>A new version of indoor=</title>
  51.      <link></link>
  52.      <guid></guid>
  53.      <description>&lt;p&gt;Note: I also posted &lt;a href="" rel="nofollow noopener noreferrer"&gt;this on my blog&lt;/a&gt;.&lt;/p&gt;
  55. &lt;p&gt;&lt;em&gt;For those who have never heard of indoor=, you may want to read the &lt;a href="" rel="nofollow noopener noreferrer"&gt;introductory blog post&lt;/a&gt;. In short, it is a map that displays the indoor data of OpenStreetmap with a level selector.&lt;/em&gt;&lt;/p&gt;
  57. &lt;p&gt;I’ve released a new version of &lt;a href="" rel="nofollow noopener noreferrer"&gt;indoor=&lt;/a&gt; that brings visual, interaction and deployment enhancements.&lt;/p&gt;
  59. &lt;h2 id="visual-enhancements"&gt;Visual Enhancements&lt;/h2&gt;
  61. &lt;h3 id="display-of-contiguous-areas-without-walls"&gt;Display of contiguous areas without walls&lt;/h3&gt;
  63. &lt;p&gt;Previously, contiguous areas and corridors were rendered with a border, whereas the documentation states that they have no walls. They are now merged to avoid any rendering with a separation. The difference is noticeable in some areas.&lt;/p&gt;
  65. &lt;figure&gt;
  66.   &lt;img src=""&gt;
  67.   &lt;img src=""&gt;
  68.  &lt;figcaption&gt;&lt;a href=";amp;level=1" rel="nofollow noopener noreferrer"&gt;Gare Saint-Lazare, Paris France&lt;/a&gt;&lt;/figcaption&gt;
  69. &lt;/figure&gt;
  71. &lt;figure&gt;
  72.   &lt;img src=""&gt;
  73.   &lt;img src=""&gt;
  74.  &lt;figcaption&gt;&lt;a href="" rel="nofollow noopener noreferrer"&gt;Gare de l'est, Paris France&lt;/a&gt;&lt;/figcaption&gt;
  75. &lt;/figure&gt;
  77. &lt;h3 id="columns-management"&gt;Columns management&lt;/h3&gt;
  79. &lt;p&gt;The &lt;a href="" rel="nofollow noopener noreferrer"&gt;indoor=column&lt;/a&gt; tag is an undocumented but fairly widespread (&amp;gt; 2000 uses) tag that is used to render indoor poles.&lt;/p&gt;
  81. &lt;p&gt;&lt;img src="" alt=""&gt;&lt;/p&gt;
  83. &lt;h3 id="room-names"&gt;Room Names&lt;/h3&gt;
  85. &lt;p&gt;In most public buildings, rooms have names. It is displayed in the centre of the room.&lt;/p&gt;
  87. &lt;figure class="no-margin"&gt;
  88.  &lt;img src=""&gt;
  89.  &lt;figcaption&gt;&lt;a href=";amp;level=0" rel="nofollow noopener noreferrer"&gt;Musée du Louvre, Paris France&lt;/a&gt;&lt;/figcaption&gt;
  90. &lt;/figure&gt;
  92. &lt;h2 id="points-of-interest-details"&gt;Points of interest details&lt;/h2&gt;
  94. &lt;p&gt;It is possible to display details on a point of interest. To do so, click on the icon or the name of a point of interest.&lt;/p&gt;
  96. &lt;p&gt;&lt;img src="" alt=""&gt;&lt;/p&gt;
  98. &lt;p&gt;Different details are displayed such as the phone number, the website, the facebook page or the accessibility of the place.&lt;/p&gt;
  100. &lt;h2 id="openmaptiles-tools-update"&gt;Openmaptiles-tools update&lt;/h2&gt;
  102. &lt;p&gt;indoor= is built with the invaluable help of &lt;a href="" rel="nofollow noopener noreferrer"&gt;openmaptiles-tools&lt;/a&gt;. Version 5.2 is now in use which brings many improvements. For instance, it is much easier to render a planet sample and retrieve a mbtiles file.&lt;/p&gt;
  104. &lt;h2 id="other-new-features"&gt;Other new features&lt;/h2&gt;
  106. &lt;h3 id="translation"&gt;Translation&lt;/h3&gt;
  108. &lt;p&gt;It is possible to translate the interface of indoor= into your language. Please visit &lt;a href="" rel="nofollow noopener noreferrer"&gt;Transifex for this matter&lt;/a&gt;.&lt;/p&gt;
  110. &lt;h3 id="indoor-integration-in-your-map"&gt;Indoor= integration in your map&lt;/h3&gt;
  112. &lt;p&gt;If you missed it, it is possible to integrate the tiles and the indoor= style everywhere with the &lt;a href="" rel="nofollow noopener noreferrer"&gt;mapbox-gl-indoorequal&lt;/a&gt; plugin.&lt;/p&gt;
  114. &lt;h2 id="whats-next"&gt;What’s next?&lt;/h2&gt;
  116. &lt;p&gt;Do you have any improvement ideas? You can submit your requests on the &lt;a href="" rel="nofollow noopener noreferrer"&gt;github project page&lt;/a&gt;.&lt;/p&gt;
  118. </description>
  119.      <dc:creator>François2</dc:creator>
  120.      <pubDate>Fri, 03 Jul 2020 14:06:34 +0000</pubDate>
  121.      <comments></comments>
  122.    </item>
  123.    <item>
  124.      <title>Maroda</title>
  125.      <link></link>
  126.      <guid></guid>
  127.      <description>&lt;p&gt;Segnalazione di alberi da frutto abbandonati dai quali si può raccogliere frutta&lt;/p&gt;
  128. </description>
  129.      <dc:creator>Diego Mometti</dc:creator>
  130.      <pubDate>Fri, 03 Jul 2020 13:03:41 +0000</pubDate>
  131.      <comments></comments>
  132.      <geo:lat>44.9123519184228</geo:lat>
  133.      <geo:long>7.32622861862183</geo:long>
  134.      <georss:point>44.9123519184228 7.32622861862183</georss:point>
  135.    </item>
  136.    <item>
  137.      <title>Mapping Baltimore City's Storm Drains</title>
  138.      <link></link>
  139.      <guid></guid>
  140.      <description>&lt;p&gt;Baltimore City, like many cities of its era, was built long before environmental regulations required the preservation of wetlands and streams. Baltimore is built along the banks of a navigable waterway, in a valley that drains a large watershed that extends into the surrounding environs. However, when examining a map of the city, there is a notable lack of streams in the built up areas that usually give some definition to the topography shown on a map. That’s because the streams that used to dot the banks of the Patapsco River and Jones Falls have been placed underground by man in an attempt to tame nature and move surface water out of sight. Public Works engineers of the early 1900s tried to put streams into pipes wherever possible because they were seen as open sewers, rife with disease and industrial filth. These decisions have had dire consequences on the health of the water bodies downstream and have turned the built up city into an area devoid of natural water where there should be plenty.&lt;/p&gt;
  142. &lt;p&gt;Recently I’ve started finding and adding these buried streams to OpenStreetMap in an attempt to surface their existence to the world. Referencing public storm drain plans and old news articles I’ve found at the library, I’ve started adding some streams that are now completely underground. The process is interesting in part due to the massive scale of the underground pipes and tunnels that we rely on any time it rains, yet have little knowledge of their existence. There are several tunnels in excess of 4 meters in diameter.&lt;/p&gt;
  144. &lt;p&gt;&lt;img src="" alt=""&gt;&lt;/p&gt;
  146. &lt;p&gt;While you can see the culverts on the regular map, they are usually below the streets and thus not visible. I &lt;a href="" rel="nofollow noopener noreferrer"&gt;set up an overpass query&lt;/a&gt; to select all these culverts for viewing. I find it interesting to see how far these systems extend underground and how large some of the individual pipes and culverts are. I also enjoyed figuring out the names of these streams looking at the old plans and articles and then assigning those names on the map. Some of the streams that have been completely buried, like &lt;a href="" rel="nofollow noopener noreferrer"&gt;Sumwalt Run in Charles Village&lt;/a&gt; or &lt;a href="" rel="nofollow noopener noreferrer"&gt;Ogier’s Run in Highlandtown&lt;/a&gt;, have been completely erased from modern maps. By adding them to OSM, I hope to reintroduce them to the world.&lt;/p&gt;
  147. </description>
  148.      <dc:creator>ElliottPlack</dc:creator>
  149.      <pubDate>Thu, 02 Jul 2020 14:56:56 +0000</pubDate>
  150.      <comments></comments>
  151.      <geo:lat>39.2886084741994</geo:lat>
  152.      <geo:long>-76.5942764282227</geo:long>
  153.      <georss:point>39.2886084741994 -76.5942764282227</georss:point>
  154.    </item>
  155.    <item>
  156.      <title>Realising I don't need to date my entries</title>
  157.      <link></link>
  158.      <guid></guid>
  159.      <description>&lt;p&gt;There’s a timestamp on them, but I put 01/07/2020 on my last entry.
  160. Also, I don’t see any rules on diaries. Should they just be anything I want or do they have to be OSM-related in some way?&lt;/p&gt;
  161. </description>
  162.      <dc:creator>berrybine</dc:creator>
  163.      <pubDate>Thu, 02 Jul 2020 09:51:58 +0000</pubDate>
  164.      <comments></comments>
  165.    </item>
  166.    <item>
  167.      <title>Is there a way to keep history on all segment while "split 3 part of highway" in JOSM ??</title>
  168.      <link></link>
  169.      <guid></guid>
  170.      <description>&lt;p&gt;So in JOSM, if I wanna split a way into 3 part, it asks which one of the segment that I want to reuse the history. instead of one, i really need all segment to keep its history so the community still could track the previous mapper edits. I think it’s not fair if the rest of the segment become our data because we only split it not add the new one. Here the illustration which i refer to.
  171. &lt;a href="" rel="nofollow noopener noreferrer"&gt;&lt;img src="" alt="Untitled" border="0"&gt;&lt;/a&gt;&lt;/p&gt;
  172. </description>
  173.      <dc:creator>Akrimullah</dc:creator>
  174.      <pubDate>Thu, 02 Jul 2020 09:37:22 +0000</pubDate>
  175.      <comments></comments>
  176.    </item>
  177.    <item>
  178.      <title>西嶼島:外垵廟拍 </title>
  179.      <link></link>
  180.      <guid></guid>
  181.      <description>&lt;p&gt;溫王殿(外垵)石敢當、三仙塔、部分營頭
  182. 金王廟(外垵)
  183. 魯國大夫廟(外塹)
  184. 二興宮(內塹)&lt;/p&gt;
  186. &lt;p&gt;小池角關帝廟(五營頭全拍)&lt;/p&gt;
  187. </description>
  188.      <dc:creator>akiflorence0487</dc:creator>
  189.      <pubDate>Thu, 02 Jul 2020 02:32:50 +0000</pubDate>
  190.      <comments></comments>
  191.      <geo:lat>23.567761441644</geo:lat>
  192.      <geo:long>119.479513406623</geo:long>
  193.      <georss:point>23.567761441644 119.479513406623</georss:point>
  194.    </item>
  195.    <item>
  196.      <title>Ccd</title>
  197.      <link></link>
  198.      <guid></guid>
  199.      <description>&lt;p&gt;Sssss&lt;/p&gt;
  200. </description>
  201.      <dc:creator>Scar Dejong</dc:creator>
  202.      <pubDate>Thu, 02 Jul 2020 00:57:16 +0000</pubDate>
  203.      <comments></comments>
  204.      <geo:lat>43.6062506917464</geo:lat>
  205.      <geo:long>-87.8933715820313</geo:long>
  206.      <georss:point>43.6062506917464 -87.8933715820313</georss:point>
  207.    </item>
  208.    <item>
  209.      <title>Зручний фільтр у JOSM</title>
  210.      <link></link>
  211.      <guid></guid>
  212.      <description>&lt;p&gt;Однією з killer feature для мене у JOSM є фільтри, які дозволяють бачити лише ту інформацію, яка мені потрібна зараз. Найбільш “неприємним” для ока є бачити десятки маленьких жовтих квадратиків node, які не несуть великої інформації, особливо, коли редагуєш дороги. Чи можна їх сховати? Льогко!
  213. У фільтр задаємо:&lt;/p&gt;
  214. &lt;pre&gt;&lt;code&gt;type:node untagged&lt;/code&gt;&lt;/pre&gt;
  215. &lt;p&gt;після цього ставимо галочки E та H.&lt;/p&gt;
  217. &lt;p&gt;Насолоджуємося результатом!&lt;/p&gt;
  218. </description>
  219.      <dc:creator>AlexRiabtsev</dc:creator>
  220.      <pubDate>Wed, 01 Jul 2020 13:40:32 +0000</pubDate>
  221.      <comments></comments>
  222.    </item>
  223.    <item>
  224.      <title>First day</title>
  225.      <link></link>
  226.      <guid></guid>
  227.      <description>&lt;p&gt;WOW!!&lt;/p&gt;
  228. </description>
  229.      <dc:creator>Sarsa</dc:creator>
  230.      <pubDate>Wed, 01 Jul 2020 13:29:21 +0000</pubDate>
  231.      <comments></comments>
  232.      <geo:lat>47.6357835908649</geo:lat>
  233.      <geo:long>-122.36572265625</geo:long>
  234.      <georss:point>47.6357835908649 -122.36572265625</georss:point>
  235.    </item>
  236.    <item>
  237.      <title>  Подскажите, где помапить?</title>
  238.      <link></link>
  239.      <guid></guid>
  240.      <description>&lt;p&gt;А то что-то идей нет.&lt;/p&gt;
  241. </description>
  242.      <dc:creator>DavisMNT</dc:creator>
  243.      <pubDate>Wed, 01 Jul 2020 12:07:43 +0000</pubDate>
  244.      <comments></comments>
  245.    </item>
  246.    <item>
  247.      <title>Mapping a Zoo in Dundee, Scotland</title>
  248.      <link></link>
  249.      <guid></guid>
  250.      <description>&lt;p&gt;In a recent phone conversation with a relative who lives in Dundee, Scotland, I discovered Dundee has it’s own zoo, &lt;a href="" rel="nofollow noopener noreferrer"&gt;Camperdown Wildlife Centre.&lt;/a&gt;&lt;/p&gt;
  252. &lt;p&gt;This is contained within &lt;a href="" rel="nofollow noopener noreferrer"&gt;Camperdown Country Park.&lt;/a&gt;&lt;/p&gt;
  254. &lt;p&gt;After the phone call I checked the &lt;a href="" rel="nofollow noopener noreferrer"&gt;park&lt;/a&gt; and the &lt;a href="" rel="nofollow noopener noreferrer"&gt;zoo&lt;/a&gt; on OSM and I saw that the park needed much improved tracing, and that the zoo was simply a border outline trace on the map and nothing else.&lt;/p&gt;
  256. &lt;ul&gt;
  257.  &lt;li&gt;Camperdown Country Park &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/li&gt;
  258.  &lt;li&gt;Camperdown Wildlife Centre / Zoo &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/li&gt;
  259. &lt;/ul&gt;
  261. &lt;p&gt;So I set out to improve this. Firstly I improved the accuracy of the tracing for the country park and added some missing traces. This was a general tidy up and much still needs to be done to improve the mapping for the Country Park. Apparently there are many interesting trees growing in the park that could be individually tagged.&lt;/p&gt;
  263. &lt;p&gt;I spent what must have been 5 or 6 hours getting information on the park from the Camperdown Wildlife centre site (zoo) and putting it into the map (OSM).&lt;/p&gt;
  265. &lt;p&gt;I doubt I will have time to keep the animal enclosure information up to date as this changes with time.&lt;/p&gt;
  267. &lt;p&gt;I’d be interested in any comments about mapping zoo’s and / or parks.&lt;/p&gt;
  269. </description>
  270.      <dc:creator>ABZ_OSM</dc:creator>
  271.      <pubDate>Wed, 01 Jul 2020 09:26:06 +0000</pubDate>
  272.      <comments></comments>
  273.      <geo:lat>56.4816907192632</geo:lat>
  274.      <geo:long>-3.04456472396851</geo:long>
  275.      <georss:point>56.4816907192632 -3.04456472396851</georss:point>
  276.    </item>
  277.    <item>
  278.      <title>Covid and adding local schools contact information tags for the North East of Scotland</title>
  279.      <link></link>
  280.      <guid></guid>
  281.      <description>&lt;p&gt;Because of covid and the particular need for parents to be in touch with schools, I’ve joined with  &lt;a href="" rel="nofollow noopener noreferrer"&gt;Robert Whittaker’s&lt;/a&gt; efforts to map school information.
  282. &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  284. &lt;p&gt;Robert has produced some very good analytics maps, which show the percentage of schools that have a complete mapped data set in each part of Scotland.&lt;/p&gt;
  286. &lt;p&gt;This can be used to add information where existing tag sets are lacking, or tag correction is necessary.&lt;/p&gt;
  288. &lt;p&gt;Mostly this information can be found on local schools web sites.&lt;/p&gt;
  290. &lt;h5 id="a-typical-school-mapping"&gt;A typical school mapping&lt;/h5&gt;
  292. &lt;ul&gt;
  293.  &lt;li&gt;A typical school mapping in Scotland might look like this &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/li&gt;
  294. &lt;/ul&gt;
  296. &lt;h5 id="how-to-tag-contact-information"&gt;How to tag contact information&lt;/h5&gt;
  298. &lt;p&gt;Typically this will look like&lt;/p&gt;
  300. &lt;ul&gt;
  301.  &lt;li&gt;
  302.    &lt;p&gt;“contact:website=http://www…..”&lt;/p&gt;
  303.  &lt;/li&gt;
  304.  &lt;li&gt;
  305.    &lt;p&gt;“contact:phone=+44 ….”&lt;/p&gt;
  306.  &lt;/li&gt;
  307.  &lt;li&gt;
  308.    &lt;p&gt;“contact:[email protected]…..”&lt;/p&gt;
  309.  &lt;/li&gt;
  310.  &lt;li&gt;
  311.    &lt;p&gt;.. see the typical mapping link above to get an idea for how tags at other schools might look&lt;/p&gt;
  312.  &lt;/li&gt;
  313. &lt;/ul&gt;
  315. &lt;h5 id="isced-levels"&gt;Isced levels&lt;/h5&gt;
  317. &lt;ul&gt;
  318.  &lt;li&gt;
  319.    &lt;p&gt;This page explans isced levels rather well &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  320.  &lt;/li&gt;
  321.  &lt;li&gt;
  322.    &lt;p&gt;Isced levels sould be mapped “isced:level=1” for a primary school, and “isced:level=3” for a secondary school.
  323. Have a look at the isced levels link above to be sure, but this seems it will fit most cases.&lt;/p&gt;
  324.  &lt;/li&gt;
  325. &lt;/ul&gt;
  327. &lt;h5 id="scottish-government-seed-codes"&gt;Scottish Government Seed codes&lt;/h5&gt;
  329. &lt;ul&gt;
  330.  &lt;li&gt;
  331.    &lt;p&gt;Scottish Government Seed codes, and other useful school mapping information may be found here &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  332.  &lt;/li&gt;
  333.  &lt;li&gt;
  334.    &lt;p&gt;Seed codes should be mapped, eg “ref:seedcode=123456”&lt;/p&gt;
  335.  &lt;/li&gt;
  336. &lt;/ul&gt;
  338. </description>
  339.      <dc:creator>ABZ_OSM</dc:creator>
  340.      <pubDate>Wed, 01 Jul 2020 08:29:14 +0000</pubDate>
  341.      <comments></comments>
  342.      <geo:lat>57.0560194870795</geo:lat>
  343.      <geo:long>-2.13625073432922</geo:long>
  344.      <georss:point>57.0560194870795 -2.13625073432922</georss:point>
  345.    </item>
  346.    <item>
  347.      <title>01/07/2020: I have discovered OSM diaries.</title>
  348.      <link></link>
  349.      <guid></guid>
  350.      <description>&lt;p&gt;dear diry
  351. today i am discover the open street map diary feature
  352. why do this exist?
  353. is this published to the whole world?
  354. what is the point of this?
  355. am i supposed to like write down how i feel about life in general&lt;/p&gt;
  356. </description>
  357.      <dc:creator>berrybine</dc:creator>
  358.      <pubDate>Wed, 01 Jul 2020 08:27:01 +0000</pubDate>
  359.      <comments></comments>
  360.    </item>
  361.    <item>
  362.      <title>First with Open Map</title>
  363.      <link></link>
  364.      <guid></guid>
  365.      <description>&lt;p&gt;Starting with the &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt; option.
  366. 🆎 Alan B
  367. 1 July 2020
  368. —————–&lt;/p&gt;
  369. </description>
  370.      <dc:creator>Alanz Jazzy</dc:creator>
  371.      <pubDate>Wed, 01 Jul 2020 02:02:29 +0000</pubDate>
  372.      <comments></comments>
  373.    </item>
  374.    <item>
  375.      <title>Koordinatentransformation Bundesmeldenetz System MGI Österreich</title>
  376.      <link></link>
  377.      <guid></guid>
  378.      <description>&lt;p&gt;Ein freundlicher Gastwirt schickte mir einen Kartenauszug mit den von ihm 1992 ausgeschilderten Radwegen. 28 Jahre sind eine lange Zeit, ob die Route auch heute noch “scenic” ist?&lt;/p&gt;
  380. &lt;p&gt;Leider war die Fotokopie so schlecht, dass ein Georeferenzieren über Landmarken mühselig zu werden drohte. Aussichtsreicher erschien der Weg über das Koordinatengitter.&lt;/p&gt;
  382. &lt;table&gt;
  383.  &lt;thead&gt;
  384.    &lt;tr&gt;
  385.      &lt;th style="text-align: center"&gt;&lt;img src="" alt="002_TourMap_s"&gt;&lt;/th&gt;
  386.    &lt;/tr&gt;
  387.  &lt;/thead&gt;
  388.  &lt;tbody&gt;
  389.    &lt;tr&gt;
  390.      &lt;td style="text-align: center"&gt;&lt;em&gt;Abb 1: Radrouten um Laßnitzhöhe (1992). Quelle: [1]&lt;/em&gt;&lt;/td&gt;
  391.    &lt;/tr&gt;
  392.  &lt;/tbody&gt;
  393. &lt;/table&gt;
  395. &lt;p&gt;&lt;br&gt;
  396. Das Kartenbild enthielt ein Koordinatengitter, die Beschriftungen waren jedoch außerhalb des Auszuges. Durch Vergleich mit einer ÖK25-V Karte war jedoch bald klar, das ist ein Bundesmeldenetz in Gauß-Krüger Projektion.&lt;/p&gt;
  398. &lt;p&gt;Doch wie zu den Koordinaten kommen? Das System ist schon so lange nicht mehr in Verwendung, dass die Online-Recherchen nur mehr spärliche Informationen liefern. Die Mosaiksteinchen zusammengesetzt ergeben folgendes Bild:&lt;/p&gt;
  400. &lt;table&gt;
  401.  &lt;thead&gt;
  402.    &lt;tr&gt;
  403.      &lt;th style="text-align: center"&gt;&lt;img src="" alt="BMN-BEV"&gt;&lt;/th&gt;
  404.    &lt;/tr&gt;
  405.  &lt;/thead&gt;
  406.  &lt;tbody&gt;
  407.    &lt;tr&gt;
  408.      &lt;td style="text-align: center"&gt;&lt;em&gt;Abb 2: Ausschnitt der Österreichischen Karte 1:25 000, Blatt BMN 6707, Graz. Das „&lt;strong&gt;X&lt;/strong&gt;“ repräsentiert den Messort mit den abgelesenen Koordinaten: Rechtswert y = 676 000 und Hochwert x = 210 000 (Quelle: &lt;a href="" rel="nofollow noopener noreferrer"&gt;Wikimedia Commons&lt;/a&gt;)&lt;/em&gt;&lt;/td&gt;
  409.    &lt;/tr&gt;
  410.  &lt;/tbody&gt;
  411. &lt;/table&gt;
  413. &lt;p&gt;&lt;br&gt;&lt;/p&gt;
  415. &lt;h3 id="bmn-gk-koordinaten-ablesen"&gt;BMN GK-Koordinaten ablesen&lt;/h3&gt;
  417. &lt;p&gt;Das Bundesmeldenetz (BMN) dient der vereinfachten Ortsangabe. Vorteilhaft sind die kleinen Zahlen und der Entfall des Bezugsmeridians. Die BMN-Werte in Gauß-Krüger Abbildung (GK) können einfach aus der Karte berechnet werden: Kleine und große Ziffern aus der Karte zusammennehmen und mit 1000 multiplizieren.&lt;/p&gt;
  419. &lt;p&gt;Beispiel für den Ort „&lt;strong&gt;X&lt;/strong&gt;“ in Abb 2:&lt;/p&gt;
  421. &lt;p&gt;&lt;code&gt;X(y_BMN_GK, x_BMN_GK): 676 000, 210 000&lt;/code&gt;&lt;/p&gt;
  423. &lt;p&gt;Eine einfache Transformation stellt den Zusammenhang zwischen BMN GK-Koordinaten und den GK-Koordinaten her [2]. Genau diese Transformationsparameter müssen im EPSG-Code enthalten sein.&lt;/p&gt;
  425. &lt;p&gt;&lt;code&gt;Hochwert:           x_BMN_GK = x_GK – 5 000 000&lt;/code&gt;&lt;br&gt;
  426. &lt;code&gt;Rechtswert M28:     y_BMN_GK = y_GK + 150 000&lt;/code&gt;&lt;br&gt;
  427. &lt;code&gt;Rechtswert M31:     y_BMN_GK = y_GK + 450 000&lt;/code&gt;&lt;br&gt;
  428. &lt;code&gt;Rechtswert M34:     y_BMN_GK = y_GK + 750 000&lt;/code&gt;&lt;/p&gt;
  430. &lt;p&gt;Die genaue Lage der Katastralgemeinden zu den Bezugsmeridianen ist in [3], S15ff dokumentiert.&lt;/p&gt;
  432. &lt;h3 id="beschreibung-der-koordinaten-mit-epsg-codes"&gt;Beschreibung der Koordinaten mit EPSG-Codes&lt;/h3&gt;
  434. &lt;p&gt;Den passenden EPSG-Code [4] zu finden ist nicht ganz einfach. Der Name gibt nur einen groben Anhaltspunkt. Auf die Parameter schauen oder durchprobieren. Für die BMN GK-Koordinaten in M34 passt&lt;/p&gt;
  436. &lt;p&gt;&lt;code&gt;EPSG:31259 - MGI/Austria GK M34&lt;/code&gt;&lt;/p&gt;
  438. &lt;p&gt;Mit dem proj.4-Code [5]:&lt;/p&gt;
  440. &lt;p&gt;&lt;code&gt;+proj=tmerc +lat_0=0 +lon_0=16.33333333333333 +k=1&lt;/code&gt;
  441. &lt;code&gt;+x_0=750000 +y_0=-5000000 +ellps=bessel   +towgs84=577.326,90.129,463.919,5.137,1.474,5.297,2.4232 +units=m +no_defs&lt;/code&gt;&lt;/p&gt;
  443. &lt;h4 id="alle-epsg-codes-fr-das-bmn-in-gk"&gt;Alle EPSG-Codes für das BMN in GK&lt;/h4&gt;
  445. &lt;p&gt;&lt;code&gt;EPSG:31257 - MGI/Austria GK M28&lt;/code&gt;&lt;br&gt;
  446. &lt;code&gt;EPSG:31258 - MGI/Austria GK M31&lt;/code&gt;&lt;br&gt;
  447. &lt;code&gt;EPSG:31259 - MGI/Austria GK M34&lt;/code&gt;&lt;/p&gt;
  449. &lt;h3 id="georeferenzieren"&gt;Georeferenzieren&lt;/h3&gt;
  451. &lt;p&gt;Mit dem Gitterwerkzeug in &lt;a href="" rel="nofollow noopener noreferrer"&gt;QMap Tool&lt;/a&gt; und der Kenntnis des richtigen EPSG-Codes (&lt;code&gt;+init=epsg:31259&lt;/code&gt;) war es in wenigen Minuten erledigt. Der maximale Ortsfehler lag bei 100m, das war ausreichend für eine eindeutige Identifizierung der markierten Wege.&lt;/p&gt;
  453. &lt;table&gt;
  454.  &lt;thead&gt;
  455.    &lt;tr&gt;
  456.      &lt;th&gt;&lt;img src="" alt="Bild hsgeoref_otm.jpg"&gt;&lt;/th&gt;
  457.    &lt;/tr&gt;
  458.  &lt;/thead&gt;
  459.  &lt;tbody&gt;
  460.    &lt;tr&gt;
  461.      &lt;td&gt;&lt;em&gt;Abb 3: Georeferenzierte Fotokopie mit transparent überlagerter Landkarte. (Quellen: Kartendaten: (c) OpenStreetMap - Mitwirkende; Rendering: (c) OpenTopoMap; Fotokopie: [1])&lt;/em&gt;&lt;/td&gt;
  462.    &lt;/tr&gt;
  463.  &lt;/tbody&gt;
  464. &lt;/table&gt;
  466. &lt;p&gt;&lt;br&gt;&lt;/p&gt;
  468. &lt;h3 id="tour"&gt;Tour&lt;/h3&gt;
  470. &lt;p&gt;Überwiegend sehr schöne Streckenführung. Beschilderung nur mehr in Resten vorhanden.&lt;/p&gt;
  472. &lt;p&gt;&lt;br&gt;&lt;/p&gt;
  474. &lt;h3 id="referenzen"&gt;Referenzen&lt;/h3&gt;
  476. &lt;p&gt;[1] Fam. Csaszar, persönliche Mitteilung, 30.03.2020&lt;/p&gt;
  478. &lt;p&gt;[2] BEV, Koordinatensysteme&lt;br&gt;
  479. &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  481. &lt;p&gt;[3] BEV, 3-D Referenzsysteme in Österreich&lt;br&gt;
  482. &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  484. &lt;p&gt;[4] BEV, EPSG-Übersicht: Geodätisches Datum und Projektionen in Österreich&lt;br&gt;
  485. &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  487. &lt;p&gt;[5] Spatial Reference&lt;br&gt;
  488. &lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  490. </description>
  491.      <dc:creator>Robhubi</dc:creator>
  492.      <pubDate>Tue, 30 Jun 2020 20:51:23 +0000</pubDate>
  493.      <comments></comments>
  494.      <geo:lat>47.0635765133547</geo:lat>
  495.      <geo:long>15.5895835161209</geo:long>
  496.      <georss:point>47.0635765133547 15.5895835161209</georss:point>
  497.    </item>
  498.    <item>
  499.      <title>Proof of Concepts</title>
  500.      <link></link>
  501.      <guid></guid>
  502.      <description>&lt;p&gt;The code for these POCs can be found &lt;a href="" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt;. This code will still be modified as we test and tweak various options available. This phase is important to establish that our project is going to work as expected, and there are no missing/misbehaving components.&lt;/p&gt;
  504. &lt;p&gt;As a part of this, the following components are designed and tested:&lt;/p&gt;
  506. &lt;h4 id="getting-input"&gt;Getting input:&lt;/h4&gt;
  508. &lt;ul&gt;
  509.  &lt;li&gt;Psycopg2 Python library is used to connect to postgresql and fetch data.&lt;/li&gt;
  510.  &lt;li&gt;
  511.    &lt;p&gt;DictCursors used to fetch data in a dictionary format. (This is necessary to ensure that the hstore data structure used to store name, address fields are fetched correctly.)&lt;/p&gt;
  513.    &lt;p&gt;&lt;strong&gt;Important note&lt;/strong&gt;: These cursors are not thread-safe. So, going ahead, if multithreading is used, this must be kept in mind.&lt;/p&gt;
  514.  &lt;/li&gt;
  515. &lt;/ul&gt;
  517. &lt;h4 id="formatting"&gt;Formatting:&lt;/h4&gt;
  519. &lt;ul&gt;
  520.  &lt;li&gt;Created a &lt;code&gt;Doc&lt;/code&gt; class with necessary fields. (Fields discussed in the last article)&lt;/li&gt;
  521.  &lt;li&gt;Forming addresses using the place_addressline table. These will be finally indexed in elasticsearch along with other necessary fields.&lt;/li&gt;
  522. &lt;/ul&gt;
  524. &lt;h4 id="indexing"&gt;Indexing:&lt;/h4&gt;
  526. &lt;ul&gt;
  527.  &lt;li&gt;Setting up an elasticsearch server and running it.&lt;/li&gt;
  528.  &lt;li&gt;Creating an index, Deleting an index.&lt;/li&gt;
  529.  &lt;li&gt;Inserting documents into the index. Indexing with looping and using bulk indexing.&lt;/li&gt;
  530.  &lt;li&gt;Try indexing with varying numbers of records.&lt;/li&gt;
  531. &lt;/ul&gt;
  533. &lt;h4 id="hug-api"&gt;Hug API:&lt;/h4&gt;
  535. &lt;ul&gt;
  536.  &lt;li&gt;Create a hug API client to add an extra layer of security by avoiding exposure of elasticsearch endpoints.&lt;/li&gt;
  537. &lt;/ul&gt;
  539. &lt;h4 id="searching"&gt;Searching:&lt;/h4&gt;
  541. &lt;ul&gt;
  542.  &lt;li&gt;Setting up the front end on Nominatim. Available &lt;a href="" rel="nofollow noopener noreferrer"&gt;here&lt;/a&gt;&lt;/li&gt;
  543.  &lt;li&gt;Fetching results from the hug API endpoint to Nominatim.&lt;/li&gt;
  544.  &lt;li&gt;Displaying the results as an option list.&lt;/li&gt;
  545.  &lt;li&gt;Selection of results by the user.&lt;/li&gt;
  546. &lt;/ul&gt;
  548. &lt;h3 id="outcomesobservations"&gt;Outcomes/Observations:&lt;/h3&gt;
  549. &lt;ol&gt;
  550.  &lt;li&gt;All the parts work well as expected.&lt;/li&gt;
  551.  &lt;li&gt;The indexing speed differed from system to system. On the server, we can index at a rate of &amp;gt;1500 documents per second. This is something we can work with at the moment, but further changes are to be made, and the goal is to reach 2000 documents per second.&lt;/li&gt;
  552.  &lt;li&gt;Bulk indexing works at exceptional rates for smaller extracts. But the rate goes down as more and more data is given. This needs a bit more work.&lt;/li&gt;
  553.  &lt;li&gt;With our indexing and frontend trials, we got good results using just the &lt;code&gt;match_phrase_prefix&lt;/code&gt; option while querying elasticsearch.&lt;/li&gt;
  554. &lt;/ol&gt;
  556. &lt;h3 id="next-steps"&gt;Next steps:&lt;/h3&gt;
  557. &lt;p&gt;With the POCs now completed, we move forward to the actual planning and design part of the project. Most of the parts are available. Planning will help structure the project and connect all the dots.&lt;/p&gt;
  558. </description>
  559.      <dc:creator>krahulreddy</dc:creator>
  560.      <pubDate>Tue, 30 Jun 2020 17:04:49 +0000</pubDate>
  561.      <comments></comments>
  562.    </item>
  563.    <item>
  564.      <title>Radio 4 Mapping the Future</title>
  565.      <link></link>
  566.      <guid></guid>
  567.      <description>&lt;p&gt;&lt;a href="" rel="nofollow noopener noreferrer"&gt;;/a&gt;&lt;/p&gt;
  569. &lt;p&gt;Writer Jerry Brotton navigates the transformation from paper to digital mapping, from print to pixels, and asks what is being gained and lost.&lt;/p&gt;
  570. </description>
  571.      <dc:creator>Anna_AG</dc:creator>
  572.      <pubDate>Tue, 30 Jun 2020 15:12:59 +0000</pubDate>
  573.      <comments></comments>
  574.    </item>
  575.    <item>
  576.      <title>Cukormentes cukrászda tesztelése (online &amp; személyes)</title>
  577.      <link></link>
  578.      <guid></guid>
  579.      <description>&lt;ul&gt;
  580.  &lt;li&gt;2020-07-02 16:45 &lt;a href="" rel="nofollow noopener noreferrer"&gt;Gyülekező az ivókútnál&lt;/a&gt;&lt;/li&gt;
  581.  &lt;li&gt;17:00 &lt;a href="" rel="nofollow noopener noreferrer"&gt;1126 Budapest, Ugocsa utca 14 szám alatti Cukormentes Cukrászda&lt;/a&gt;, illetve online is lehet csatlakozni.&lt;/li&gt;
  582. &lt;/ul&gt;
  584. &lt;p&gt;További információk a wiki oldalon olvashatók: &lt;a href="álkozók/2020-07-02-osm-cukraszda" rel="nofollow noopener noreferrer"&gt;álkozók/2020-07-02-osm-cukraszda&lt;/a&gt;&lt;/p&gt;
  586. &lt;p&gt;Kérdéseket Matrixon és a levlistán is fogadunk.&lt;/p&gt;
  588. &lt;p&gt;&lt;img src="" alt="desserts"&gt;&lt;/p&gt;
  589. </description>
  590.      <dc:creator>bkil</dc:creator>
  591.      <pubDate>Tue, 30 Jun 2020 14:56:45 +0000</pubDate>
  592.      <comments></comments>
  593.      <geo:lat>47.49465</geo:lat>
  594.      <geo:long>19.02001</geo:long>
  595.      <georss:point>47.49465 19.02001</georss:point>
  596.    </item>
  597.  </channel>
  598. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda