motorway | Cloud ready pure-python streaming data pipeline library | Stream Processing library

For navigation you register at the RouteProgressListener (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/navigation/RouteProgressListener-class.html) for progress updates.

In this callback (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/navigation/RouteProgressListener/onRouteProgressUpdated.html) your get the route progress object (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/navigation/RouteProgress/RouteProgress.html).

With this you know the index for the next maneuver and you query the Navigator for the concrete maneuver object via getManeuver (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/navigation/NavigatorInterface/getManeuver.html)

In this maneuver object (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/routing/Maneuver-class.html) you can get the exist sign text (https://developer.here.com/documentation/flutter-sdk-navigate/4.8.3.0/api_reference/routing/Maneuver/exitSignTexts.html) if available (in most cases only for highways of course).

Basically, I was trying to read broken JSON, as Felix mentioned JSON cannot contain literal line breaks.

Solution: use https://www.npmjs.com/package/jsonrepair module. It detected the bad lines and fixed them, this is likely what google does (some sort of JSON repair).

PS: I tried https://www.npmjs.com/package/json-fixer without success

It works .... I think I had a dodgy chrome instance running

Consider a sf::st_join() call, using first your polygons and secondly your line string objects, with parameter left set to false.

It will perform an inner (filtering) spatial join of the two objects. Only those polygons (the first argument) that contain a motorway will be retained.

Here is the benchmarking for the existing to OP's question (borrow test data from @Marek Fiołka but with n <- 10000)

This is in principle and through design not possible, because the underlying data model of OSM is entirely different from the data model of Simple Features. The osmdata package reflects one mapping of the former data model onto the latter (with design decisions explained at some length in a package vignette). The points are always there, because they are the only parts of the OSM data base that contain the actual coordinates. The omsdata package simply converts them to Simple Features form, but they are always delivered regardless. OSM only knows three things: nodes, ways, and relations. Both lines and polygons (as well as anything else) can be formed of multiple individual "ways" which have to be stitched together to form Simple Features "lines" or "polygons". Those ways in turn have no coordinates, but are only sequences of point IDs, which is why the points always have to be delivered. That effectively prevents any simplification of queries along the lines you suggest - there is no "waste of resources" because what you want (lines and polygons) requires all the data to be delivered regardless. The only things you could do would be either reduce your bounding box, or refine your query with more specific key-value pairs (or both).

I traced the issue back to the road with index 125779, which has these coordinates: [(11.8892841, 57.6579022), (11.8892841, 57.6579022)], so it is basically a point. When clipping, this geometry is converted to "LINESTRING EMPTY". Maybe it should instead convert this empty line to the corresponding Point, but anyway I guess a fix should be made in geopandas' plotting to ignore these empty lines instead of raising such an unclear error (feel free to submit an issue https://github.com/geopandas/geopandas/issues).

In the meantime, you can plot your data by selecting only non-emtpy geometries:

As it turns out i was looking for a proper use of function "log_()" and "get_selected()"

Something along the lines of