Live data from Hacker News

Happy Birthday, OpenStreetMap

tomtom.com

11–20 of 43 posts

Re: Happy Birthday, OpenStreetMap

#11
post #5

It's great to see corporations contributing to OSM. There's only a couple top contenders for mapping data, and the best way to compete with them is to collaborate on a shared resource.

It's a complicated relationship, since companies often struggle with respecting community norms and the overall goals of the project, but I tend to agree.

You can see why they might not want to share data they had to spent money to gather when their competitors would then get access for free.

Re: Happy Birthday, OpenStreetMap

#12
post #5

It's great to see corporations contributing to OSM. There's only a couple top contenders for mapping data, and the best way to compete with them is to collaborate on a shared resource.

It's a complicated relationship, since companies often struggle with respecting community norms and the overall goals of the project, but I tend to agree.

In what way? I'm interested to know more about this.

Re: Happy Birthday, OpenStreetMap

#13

Many of the red areas I see on the map, particularly in France, are fairly obviously where someone's been running a TomTom while on a train or a boat. Of course that's not going match OSM roads. I'm a little surprised this is not mentioned in the blog post - it seems a bit obvious.

>"As you can see above it’s a work in progress: MapMetrics flags, in red, Colorado ski areas and the Denver Airport. Neither of these are bad per se, but ski run and taxiway routing isn’t a thing yet! Over time, MapMetrics will filter these out to focus on just the roads."

Re: Happy Birthday, OpenStreetMap

#15
post #5

It's great to see corporations contributing to OSM. There's only a couple top contenders for mapping data, and the best way to compete with them is to collaborate on a shared resource.

It's a complicated relationship, since companies often struggle with respecting community norms and the overall goals of the project, but I tend to agree.

I find this a good way, where they expose their resources via tools that makes improving OpenStreetMap data with data they have access to easier. This isn't exposing their maps directly, so it does not come with their assumptions.

Re: Happy Birthday, OpenStreetMap

#16

Some years ago you had to pay for updates and they were very slow to add new streets. Has this changed with OSM?

Depends on the package you buy. I have a "lifetime subscription", so theoretically I'll never need to pay for an update.

...but then newer devices only work with newer versions of the service, for which you haven't got a lifetime subscription. Eventually, your old TomTom stops working and your subscription is now worthless so you have to buy a new one.

Re: Happy Birthday, OpenStreetMap

#17
post #5

Earlier quoted context omitted.

It's a complicated relationship, since companies often struggle with respecting community norms and the overall goals of the project, but I tend to agree.

In what way? I'm interested to know more about this.

E.g. by overwhelming a local community with edits from a swarm of outsourced contractors from a wholly different country. Good luck keeping up with verification of their work.

Or making mass edits / imports without discussing with local community beforehand.

Or as in the first point, but with "AI" as FB did.

Re: Happy Birthday, OpenStreetMap

#18
post #6
post #3

It seems that the MapMetrics data mentioned either isn't available everywhere or (less likely) their site is being crushed. The data only loads for California and Colorado.

And France, weirdly. It also is quite low resolution in many areas, making it not super useful at the moment.

And the Netherlands and Albania.

Truly an odd selection.

Re: Happy Birthday, OpenStreetMap

#20
post #3

It seems that the MapMetrics data mentioned either isn't available everywhere or (less likely) their site is being crushed. The data only loads for California and Colorado.

Here too, it seems to be available for western Netherlands, parts of northwest Flanders, all of France, California, Colorado, Albania (fewer trace density it seems though). Maybe they're still importing/processing? Calculating routes for all over the world is a lot of data processing.

There is also a layer named OSM202106 (the default is OSM202103) with even less coverage (e.g. not France), but covering all of the Netherlands rather than just a part of it and covering the USA east coast.

Post reply on HN