Re: [OSM-dev] OSM Database schema
Ok, thanks. Does that also mean that this Area datatype task in “https://wiki.openstreetmap.org/wiki/Top_Ten_Tasks” is abandoned? Jean Marie Falisse > Le 4 janv. 2020 à 19:18, Stefan Keller a écrit : > > Am Sa., 4. Jan. 2020 um 18:18 Uhr schrieb mmd : >> ... As an example check out: >> https://wiki.openstreetmap.org/wiki/User:Maxbe/Routen_%C3%BCber_Fl%C3%A4chen > > See also the research work from my lab https://eprints.hsr.ch/625/ and > https://github.com/PlazaRoute/plazaroute . > > :Stefan > > Am Sa., 4. Jan. 2020 um 18:18 Uhr schrieb mmd : >> >> On 2020-01-04 17:22, Jean Marie Falisse wrote: >>> that a pedestrian zone, let’s say a big square in a city, cannot be made >>> to be crossed diagonally when used in a route planner. >> >> Getting a bit off topic here... You can calculate some artificial ways >> and feed that into some router. As an example check out: >> https://wiki.openstreetmap.org/wiki/User:Maxbe/Routen_%C3%BCber_Fl%C3%A4chen >> >> -- >> >> >> >> ___ >> dev mailing list >> dev@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/dev > > ___ > dev mailing list > dev@openstreetmap.org > https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] OSM Database schema
Hi, Best wishes to all ! I am new to this list. Lorenzo, I will be very interested in reading the result of your work. Is it still true that in the OSM database, areas are not represented as such? That would mean, for instance, that a pedestrian zone, let’s say a big square in a city, cannot be made to be crossed diagonally when used in a route planner. Am I right? That would mean, Dear Lorenzo, that you are 藍 a designated volunteer for the database overhaul project ! See Area datatype on “https://wiki.openstreetmap.org/wiki/Top_Ten_Tasks”. Just kidding. Still, I wouldn’t mind to be involved in this, especially if some programs could be written in the most beautiful programming language ever, Haskell of course. What you can do with this beast is just awesome. Hope I didn’t disturb too much. Put it on the account of the enthusiasm of the youth! Thanks for reading. JMF Jean Marie Falisse Berensheide, 3 B 1170 Watermael-Boitsfort Belgique +32 2 673 32 22 +32 479 509899 jmfali...@acm.org http://member.acm.org/~jmfalisse > Le 4 janv. 2020 à 11:40, mmd a écrit : > > On 2020-01-04 09:59, Lorenzo Stucchi wrote: >> Thank you Pascal. This is can be more precise than just I looking at the >> visualisation [1]. > > I'm not aware of a comprehensive data model internals documentation > beyond the actual source code in > https://github.com/openstreetmap/openstreetmap-website, in particular > the app/*/api directory > >> >> But, for example, what is the “timestamp” in the “node" table? > > It refers to the current time in UTC when the node create/update/delete > operation was executed. Please see > https://github.com/openstreetmap/openstreetmap-website/blob/master/app/models/node.rb#L243 > > >> And what is the “redactions” table? > > It contains a list of reasons why an object has been redacted, see > https://www.openstreetmap.org/redactions - the actual objects (such as > nodes, ways, relations) refer to this redaction table via the redaction_id. > >> Or, why in the “way_nodes” table there is >> “version", but also it is just a link to the “nodes” table that contains >> also the “version” attribute. > > Basically there are two different sets of tables: the current_* ones, > and the historic ones. "way_nodes" belongs to the historic set of > tables, and you need the version attribute to know that a node was part > of say version 2 of way 12345. On the other hand, the current_way_nodes > table has no version attribute, as it assumes that it refers to the > latest version of an object. > >> >> For this reason, I was trying to look to an explanation of this schema >> if it exists. > > I think one good way to find out more about those different tables is to > install a local version of the Rails port and do some edits via > iD/JOSM/Potlatch. The Rails port is quite verbose and lists every single > database operation on the console. > > > -- > > > ___ > dev mailing list > dev@openstreetmap.org > https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] tagtransform for OSM - An effort make tagging and using OSM data easier; bridging different worlds together
Hi, Sorry for my, probably stupid, questions. 1. Is all this written in java? 2. Is there anything going on in Haskell? I’d love to be involved in something using Haskell. Thanks for your answer. Jean Marie Falisse Berensheide, 3 B 1170 Watermael-Boitsfort Belgique +32 2 673 32 22 +32 479 509899 jmfali...@acm.org http://member.acm.org/~jmfalisse > Le 6 déc. 2019 à 13:33, Sören Reinecke via dev a > écrit : > > There are some available options I see: > a) Not working on this further. > b) Using `tagtransform for OSM` to create an own transformation specification. > c) Writing converters which convert from a format to the format of > `tagtransform for OSM` and writing converters to convert from the format of > `tagtransform for OSM` to another format programs can work with. Using my > specification which needs to be extended to create conpactibility among > different formats while ensuring that my spec can be used on its own. > > What do you prefer or do you have another options to add? > > Cheers > > Sören Reinecke alias Valor Naram > > > Original Message > Subject: Re: [OSM-dev] tagtransform for OSM - A effort make tagging and using > OSM data easier; bridging different worlds together > From: Imre Samu > To: Sören Reinecke > CC: OSM-Dev Openstreetmap > > > > I currently write a specification for tranforming tags in OpenStreetMap to > > make life of data customers easier. > > imho: we can import some good ideas from > https://wiki.openstreetmap.org/wiki/Osmosis/TagTransform > <https://wiki.openstreetmap.org/wiki/Osmosis/TagTransform> schema .. > "The tag transform Osmosis plugin allows arbitrary tag transforms to be > applied to OSM data as a preprocessing step before using other tools. This > allows other tools to concentrate on doing what ever they do, without having > to handle numerous different tagging schemes and error corrections." > imho: regexp is useful. > > probably the "lua" is good glue/meta language - for writing "business rules". > some examples: > Valhalla (routing) admin.lua ( > https://github.com/valhalla/valhalla/blob/master/lua/admin.lua > <https://github.com/valhalla/valhalla/blob/master/lua/admin.lua> ) > Valhalla (routing) graph.lua ( > https://github.com/valhalla/valhalla/blob/master/lua/graph.lua > <https://github.com/valhalla/valhalla/blob/master/lua/graph.lua> ) > > osm2gsql - openstreetmap-carto.lua > https://github.com/gravitystorm/openstreetmap-carto/blob/master/openstreetmap-carto.lua > > <https://github.com/gravitystorm/openstreetmap-carto/blob/master/openstreetmap-carto.lua> > > Regards, > Imre > > > > > > > > Sören Reinecke via dev mailto:dev@openstreetmap.org>> > ezt írta (időpont: 2019. dec. 5., Cs, 15:59): > Hey all, > > I currently write a specification for tranforming tags in OpenStreetMap to > make life of data customers easier. Different tagging schemes have emerged > since the existence of OpenStreetMap, same are existing in parallel and a > newer one deprecated an old one. Data customers without knowing the OSM > community much get lost. This project aims to help developers who want to > take advantage of the OpenStreetMap great database which is by the way a > brilliant project. This project can also help to make tagging in OSM more > orthogonal and more hassle free. > > I saw conflicting interests between OSM community, OSM developers like the iD > developers and data customers. A renderer might need data in another way as > the community contributes. The community might need another tagging scheme > than a renderer. I thought how we can resolve this, how we can get all sites > on "one table" and that is the idea I had come up with: > > A more readable version can be found here: > https://github.com/ValorNaram/transformation-table-osmtags/blob/master/README.md > > <https://github.com/ValorNaram/transformation-table-osmtags/blob/master/README.md> > and the principles can be found at > https://github.com/ValorNaram/transformation-table-osmtags/blob/master/principles.md > > <https://github.com/ValorNaram/transformation-table-osmtags/blob/master/principles.md> > > > > Example 1: They want to have the phone number of a POI. There are some > problems with this: > > 1. They need to know both contact:phone and phone to get them all. > 2. They need to support them both. > 3. They need to remove one in case both keys are mapped on one POI. This > really happens, see http://overpass-turbo.eu/s/OI2 > <http://overpass-turbo.eu/s/OI2>. > > Example 2: They want to k
