FactGrid talk:Postal routes: Difference between revisions
Jump to navigation
Jump to search
Olaf Simons (talk | contribs) No edit summary |
Olaf Simons (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
The information itself is available in contemporary publications. One would probably establish the details with a place to place data model - a model that notes on a place the connections to the very next places, from where again you would get just the arrivals and departures to the next surrounding places. | The information itself is available in contemporary publications. One would probably establish the details with a place to place data model - a model that notes on a place the connections to the very next places, from where again you would get just the arrivals and departures to the next surrounding places. | ||
My initial thought was | My initial thought was this query: take a look at Gotha, see the departures, take a look at the given places and see from there the new departures - and eventually a filter for the final destination. That, however, did not work (and it seems SPARQL cannot do this). The basic script that establishes the net from a given point is simple - here with Gotha at starting point: | ||
* [https://database.factgrid.de/query/#SELECT%20%3Fnext%20%3FnextLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20wd%3AQ10279%20wdt%3AP972%2a%20%3Fnext.%0A%7D%0A you are in Gotha, move to the next connection and continue] | * [https://database.factgrid.de/query/#SELECT%20%3Fnext%20%3FnextLabel%20WHERE%20%7B%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%20%20wd%3AQ10279%20wdt%3AP972%2a%20%3Fnext.%0A%7D%0A you are in Gotha, move to the next connection and continue] | ||
I failed to tell the machine how to always connect next places. (though I was | I failed to tell the machine how to always connect next places with a line. (though I was somehow able to create this look at [https://database.factgrid.de/query/index.html#%23defaultView%3AMap%7B%22hide%22%3A%5B%22%3Fpoint%22%2C%20%22%3Fline%22%2C%20%22%3Frgb%22%5D%7D%0ASELECT%20%0A%20%20%20%20%3Fstay%20%3FstayLabel%20%3Fpoint%20%3Fline%20%3FdayLabel%20%3Ftime%20%3Fvisualisation%20%3Frgb%0AWITH%20%7B%0A%20%20SELECT%20%3Fbegin%20%3Fstay%20%3Fjourney%20%3Fdate%20%3Fpoint%20%3Fday%20%3FdayLabel%20%3Ftime%20%3Fpoint_str%20WHERE%20%7B%0A%20%20%20%20VALUES%20%3Fjourney%20%7B%20%0A%20%20%20%20%20%20wd%3AQ635754%0A%20%20%20%20%7D%20.%20%20%0A%20%20%20%3Fjourney%20p%3AP971%20%5Bps%3AP971%20%3Fstay%20%3B%20%28pq%3AP499%29%20%3Fbegin%5D%20.%20%20%20%0A%20%20%20%3Fjourney%20p%3AP971%20%5Bps%3AP971%20%3Fstay%20%3B%20%28pq%3AP973%29%20%3Fday%5D%20.%20%20%0A%20%20%20%3Fjourney%20p%3AP971%20%5Bps%3AP971%20%3Fstay%20%3B%20%28pq%3AP509%29%20%3Ftime%5D%20.%20%20%0A%20%20%20%3Fstay%20p%3AP48%20%5B%20ps%3AP48%20%3Fpoint%20%3B%20psv%3AP48%20%2F%20wikibase%3AgeoLatitude%20%3Flat%20%3B%20psv%3AP48%20%2F%20wikibase%3AgeoLongitude%20%3Flong%20%5D%20.%0A%20%20%20%20BIND%28CONCAT%28STR%28%3Flong%29%2C%20%27%20%27%2C%20STR%28%3Flat%29%29%20AS%20%3Fpoint_str%29%0A%20%20%7D%0A%20%20ORDER%20BY%20%28%3Fbegin%29%0A%7D%20AS%20%25points%0A%0AWITH%20%7B%0A%20%20SELECT%20%3Fjourney%20%28STRDT%28%20CONCAT%28%27LINESTRING%20%28%27%2C%20GROUP_CONCAT%28%3Fpoint_str%3B%20separator%3D%27%2C%27%29%2C%20%27%29%27%29%2C%20geo%3AwktLiteral%29%20AS%20%3Fline%29%20%3Frgb%20WHERE%20%7B%0A%20%20%20%20INCLUDE%20%25points%0A%20%20%20OPTIONAL%20%7B%20%3Fjourney%20p%3AP693%20%5Bpq%3AP697%20%3Fcolor%5D%20.%0A%20%20%20%20%3Fcolor%20wdt%3AP696%20%3Frgb.%20%7D%0A%20%20%7D%20GROUP%20BY%20%3Fjourney%20%3Frgb%0A%7D%20AS%20%25line%0A%0AWHERE%20%7B%0A%20%20INCLUDE%20%25points%0A%20%20INCLUDE%20%25line%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D one particular route for which I created one specific item]). The notion of immediate vicinity does not get into the table which I can create with the search that goes from next to next. --[[User:Olaf Simons|Olaf Simons]] ([[User talk:Olaf Simons|talk]]) 08:49, 8 November 2023 (CET) | ||
Latest revision as of 14:35, 8 November 2023
Data Model
The Frankfurt-Leipzig Route is exceptionally well documented (the entire route, each halt with the respective inn, arrival end departure time). The regular documentation is from a local perspective. You are in Amsterdam and you want to know the departures into various directions (and also the arrivals of mail from these regions). We can theoretically reconstruct the network.
The cool thing would be an option to state a place and a destination - from where the tool would give you a map view of connections and changing points in the ideal case with the respective time and price information.
The information itself is available in contemporary publications. One would probably establish the details with a place to place data model - a model that notes on a place the connections to the very next places, from where again you would get just the arrivals and departures to the next surrounding places.
My initial thought was this query: take a look at Gotha, see the departures, take a look at the given places and see from there the new departures - and eventually a filter for the final destination. That, however, did not work (and it seems SPARQL cannot do this). The basic script that establishes the net from a given point is simple - here with Gotha at starting point:
I failed to tell the machine how to always connect next places with a line. (though I was somehow able to create this look at one particular route for which I created one specific item). The notion of immediate vicinity does not get into the table which I can create with the search that goes from next to next. --Olaf Simons (talk) 08:49, 8 November 2023 (CET)