Teste do aparelho

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.

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.

OpenStreetMap contributors are keeping up with the local authority efforts by updating map data as changes are made.

Most of these updates make use of the conditional access key/values outlined in https://wiki.openstreetmap.org/wiki/Conditional_restrictions

Here’s an example change in Cork, Ireland that I did earlier today: https://osmcha.org/changesets/87507009/

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).

Note: I also posted this on my blog.

For those who have never heard of indoor=, you may want to read the introductory blog post. In short, it is a map that displays the indoor data of OpenStreetmap with a level selector.

I’ve released a new version of indoor= that brings visual, interaction and deployment enhancements.

Visual Enhancements

Display of contiguous areas without walls

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.

Columns management

The indoor=column tag is an undocumented but fairly widespread (> 2000 uses) tag that is used to render indoor poles.

Room Names

In most public buildings, rooms have names. It is displayed in the centre of the room.

Points of interest details

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.

Different details are displayed such as the phone number, the website, the facebook page or the accessibility of the place.

Openmaptiles-tools update

indoor= is built with the invaluable help of openmaptiles-tools. 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.

Other new features

Translation

It is possible to translate the interface of indoor= into your language. Please visit Transifex for this matter.

Indoor= integration in your map

If you missed it, it is possible to integrate the tiles and the indoor= style everywhere with the mapbox-gl-indoorequal plugin.

What’s next?

Do you have any improvement ideas? You can submit your requests on the github project page.

Segnalazione di alberi da frutto abbandonati dai quali si può raccogliere frutta

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.

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.

While you can see the culverts on the regular map, they are usually below the streets and thus not visible. I set up an overpass query 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 Sumwalt Run in Charles Village or Ogier’s Run in Highlandtown, have been completely erased from modern maps. By adding them to OSM, I hope to reintroduce them to the world.

There’s a timestamp on them, but I put 01/07/2020 on my last entry. 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?

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.

Test

溫王殿（外垵）石敢當、三仙塔、部分營頭 金王廟（外垵） 魯國大夫廟(外塹) 二興宮(內塹)

小池角關帝廟（五營頭全拍）

Sssss

Однією з killer feature для мене у JOSM є фільтри, які дозволяють бачити лише ту інформацію, яка мені потрібна зараз. Найбільш “неприємним” для ока є бачити десятки маленьких жовтих квадратиків node, які не несуть великої інформації, особливо, коли редагуєш дороги. Чи можна їх сховати? Льогко! У фільтр задаємо:

type:node untagged

після цього ставимо галочки E та H.

Насолоджуємося результатом!

WOW!!

А то что-то идей нет.

In a recent phone conversation with a relative who lives in Dundee, Scotland, I discovered Dundee has it’s own zoo, Camperdown Wildlife Centre.

This is contained within Camperdown Country Park.

After the phone call I checked the park and the zoo 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.

• Camperdown Country Park https://www.openstreetmap.org/way/26601574#map=14/56.4881/-3.0328
• Camperdown Wildlife Centre / Zoo https://www.openstreetmap.org/way/767357922

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.

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).

I doubt I will have time to keep the animal enclosure information up to date as this changes with time.

I’d be interested in any comments about mapping zoo’s and / or parks.

Because of covid and the particular need for parents to be in touch with schools, I’ve joined with Robert Whittaker’s efforts to map school information. https://osm.mathmos.net/schools/progress

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.

This can be used to add information where existing tag sets are lacking, or tag correction is necessary.

Mostly this information can be found on local schools web sites.

A typical school mapping

• A typical school mapping in Scotland might look like this https://www.openstreetmap.org/way/112682827

How to tag contact information

Typically this will look like

• “contact:website=http://www…..”

• “contact:phone=+44 ….”

• “contact:email=abc@xyz…..”

• .. see the typical mapping link above to get an idea for how tags at other schools might look

Isced levels

• This page explans isced levels rather well https://wiki.openstreetmap.org/wiki/Key:isced:level

• Isced levels sould be mapped “isced:level=1” for a primary school, and “isced:level=3” for a secondary school. Have a look at the isced levels link above to be sure, but this seems it will fit most cases.

Scottish Government Seed codes

• Scottish Government Seed codes, and other useful school mapping information may be found here https://www2.gov.scot/Topics/Statistics/Browse/School-Education/Datasets/contactdetails

• Seed codes should be mapped, eg “ref:seedcode=123456”

dear diry today i am discover the open street map diary feature why do this exist? is this published to the whole world? what is the point of this? am i supposed to like write down how i feel about life in general

Starting with the www.openstreetmap.org option. 🆎 Alan B 1 July 2020 —————–

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?

Leider war die Fotokopie so schlecht, dass ein Georeferenzieren über Landmarken mühselig zu werden drohte. Aussichtsreicher erschien der Weg über das Koordinatengitter.

Abb 1: Radrouten um Laßnitzhöhe (1992). Quelle: [1]

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.

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:

Abb 2: Ausschnitt der Österreichischen Karte 1:25 000, Blatt BMN 6707, Graz. Das „X“ repräsentiert den Messort mit den abgelesenen Koordinaten: Rechtswert y = 676 000 und Hochwert x = 210 000 (Quelle: Wikimedia Commons)

BMN GK-Koordinaten ablesen

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.

Beispiel für den Ort „X“ in Abb 2:

X(y_BMN_GK, x_BMN_GK): 676 000, 210 000

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.

Hochwert: x_BMN_GK = x_GK – 5 000 000
Rechtswert M28: y_BMN_GK = y_GK + 150 000
Rechtswert M31: y_BMN_GK = y_GK + 450 000
Rechtswert M34: y_BMN_GK = y_GK + 750 000

Die genaue Lage der Katastralgemeinden zu den Bezugsmeridianen ist in [3], S15ff dokumentiert.

Beschreibung der Koordinaten mit EPSG-Codes

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

EPSG:31259 - MGI/Austria GK M34

Mit dem proj.4-Code [5]:

+proj=tmerc +lat_0=0 +lon_0=16.33333333333333 +k=1 +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

Alle EPSG-Codes für das BMN in GK

EPSG:31257 - MGI/Austria GK M28
EPSG:31258 - MGI/Austria GK M31
EPSG:31259 - MGI/Austria GK M34

Georeferenzieren

Mit dem Gitterwerkzeug in QMap Tool und der Kenntnis des richtigen EPSG-Codes (+init=epsg:31259) war es in wenigen Minuten erledigt. Der maximale Ortsfehler lag bei 100m, das war ausreichend für eine eindeutige Identifizierung der markierten Wege.

Abb 3: Georeferenzierte Fotokopie mit transparent überlagerter Landkarte. (Quellen: Kartendaten: (c) OpenStreetMap - Mitwirkende; Rendering: (c) OpenTopoMap; Fotokopie: [1])

Tour

Überwiegend sehr schöne Streckenführung. Beschilderung nur mehr in Resten vorhanden.

Referenzen

[1] Fam. Csaszar, persönliche Mitteilung, 30.03.2020

[2] BEV, Koordinatensysteme
http://www.bev.gv.at/pls/portal/docs/PAGE/BEV_PORTAL_CONTENT_ALLGEMEIN/0200_PRODUKTE/PDF/KOORD-SYS.PDF

[3] BEV, 3-D Referenzsysteme in Österreich
https://www.bev.gv.at/pls/portal/docs/PAGE/BEV_PORTAL_CONTENT_ALLGEMEIN/0200_PRODUKTE/SCHNITTSTELLENBESCHREIBUNGEN/SYSTEME_LANDESVERMESSUNG_2015.PDF

[4] BEV, EPSG-Übersicht: Geodätisches Datum und Projektionen in Österreich
http://www.bev.gv.at/pls/portal/docs/PAGE/BEV_PORTAL_CONTENT_ALLGEMEIN/0100_NEWS/ARCHIV_2007/NEUE%20EPSG%20-%20CODES%20FUER%20OESTERREICH/PROJEKTIONEN_TRANSF.PDF

[5] Spatial Reference
https://spatialreference.org/ref/epsg/31259/

The code for these POCs can be found here. 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.

As a part of this, the following components are designed and tested:

Getting input:

• Psycopg2 Python library is used to connect to postgresql and fetch data.

• 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.)

  Important note: These cursors are not thread-safe. So, going ahead, if multithreading is used, this must be kept in mind.

Formatting:

• Created a Doc class with necessary fields. (Fields discussed in the last article)
• Forming addresses using the place_addressline table. These will be finally indexed in elasticsearch along with other necessary fields.

Indexing:

• Setting up an elasticsearch server and running it.
• Creating an index, Deleting an index.
• Inserting documents into the index. Indexing with looping and using bulk indexing.
• Try indexing with varying numbers of records.

Hug API:

• Create a hug API client to add an extra layer of security by avoiding exposure of elasticsearch endpoints.

Searching:

• Setting up the front end on Nominatim. Available here
• Fetching results from the hug API endpoint to Nominatim.
• Displaying the results as an option list.
• Selection of results by the user.

Outcomes/Observations:

1. All the parts work well as expected.
2. The indexing speed differed from system to system. On the server, we can index at a rate of >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.
3. 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.
4. With our indexing and frontend trials, we got good results using just the match_phrase_prefix option while querying elasticsearch.

Next steps:

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.

https://www.bbc.co.uk/programmes/m000kgt8

Writer Jerry Brotton navigates the transformation from paper to digital mapping, from print to pixels, and asks what is being gained and lost.