This request/response format is a bit different than the native Photon format, but with GraphHopper Geocoding it is possible to easily switch between different "providers" (like Nominatim, OpenCage etc.), which are all usable under the same contract.
Yeah, my guess is that they implemented some EU regulation very lazily.
> Unfortunately under these laws the issue isn’t yours or your projects. It was the users.
Are you sure? How it comes reddit implemented this differently?
The argument that the issues is owned by the creator might be true, but on the other hand the user creates the issue at a "foreign" project and knows that they don't "own" this conversation. Especially the comments in these issues are not "owned" by the issue creator. This does not make any sense, especially as it is a public issue.
> Are you sure? How it comes reddit implemented this differently?
User data removal requests are handled separately from user initiated account deletion. On Reddit you can find old threads where all of one person’s posts are removed.
> but on the other hand the user creates the issue at a "foreign" project and knows that they don't "own" this conversation.
Unfortunately it doesn’t matter what you, I, or the user thinks is right at time of creation.
The only thing that matters is what the law says or implies. Users who invoke these laws often no longer care or even feel like they’re doing a good thing by hurting the original site in removing something they created.
Maybe a stupid question. When just looking at the data model (and not e.g. the query language) ... but is there a real difference between a "graph" database and a "normal SQL" database when the SQL database is able to directly point to rows (ROWID?) without a separate index?
Sorry, but this is a strange article. Not sure what the reader should learn from it.
> However, while OSM’s open, collaborative nature is a major strength, the quality and accuracy of its data still lag behind proprietary services like Google Maps.
Such a general statement is wrong. For car routes maybe. But even for POIs I have found that OSM catches up fast.
But Google Maps has definitely not the best quality for outdoor routes (like walking, hiking and biking). And this is not just my personal opinion.
> These pipelines, which process and format the data appropriately, are typically only feasible for large companies.
No, this is wrong. Already smaller companies can handle these pipelines.
Furthermore there are many companies that offer OSM data as a SaaS (routing, geocoding and/or maps)
> they are largely ineffective without access to the latest and most accurate map data.
'largely ineffective' is misleading here. OSM is already sufficiently precise atm (ofc depending on your needs). Sure, you do not have live traffic, but there are already many (Uber-like) companies that use OSM and enhance them with their own data. And also there are a few options to buy live traffic for OSM data.
> Therefore, currently, their best option is to utilize Google's APIs
From my experience many customers find them too expensive especially for the ride-hailing use case OP describes.
The GraphHopper Matrix API has an (IMO) attractive pricing especially for large matrices. The pricing is credit based and for large matrices we do not charge for every matrix cell but instead we only charge "locations*10". E.g. for a 200x200 matrix we only charge 2000 and not 40 000 credits as our underlying algorithm is very efficient (scales nearly linear). And let's say you need this calculation 25 times a day (using the premium package) then this leads to $0.016 for 1000 matrix elements. Of course even cheaper for larger matrices.
And larger packages will furthermore include a volume discount.
Except for printer driver support in my case. I wasn't able to get an Epson ET working like on Ubuntu (wifi, scanner) where under Ubuntu it works without any configuration.
Ubuntu has still the best driver support IMO (printer, fingerprint, etc). And so I only have to replace all snaps with flatpaks which works fine since 2 years.
reply