![](https://lemmy.world/pictrs/image/db260c2b-778c-4fd8-9faa-9617bc15148e.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
56·
1 year agoIt seems they consider themselves complimentary with OpenStreetMap, as stated on their FAQ https://overturemaps.org/resources/faq/#
Overture is a data-centric map project, not a community of individual map editors. Therefore, Overture is intended to be complementary to OSM. We combine OSM with other sources to produce new open map data sets. Overture data will be available for use by the OpenStreetMap community under compatible open data licenses. Overture members are encouraged to contribute to OSM directly.
I don’t know a lot about any of both projects, but it seems fair.
The behaviour you mention is from npm install, which will put the same exact version from the package-lock.json, if present. If not it will act as an npm update.
npm update will always update, and rewrite the package-lock.json file with the latest version available that complies with the restrictions defined on the package.json.
I may be wrong but, I think the difference may be that python only has the behaviour that package-lock.json offer, but not the package.json, which allows the developer to put constraints on which is the max/min version allowed to install.