>To this end, all three institutions would like to reduce our spend with Elsevier by half of the current amounts paid by each institution. We are interested in obtaining a concession that would allow articles published by authors at each institution to be converted from closed to open access. We will be asking Elsevier to remove any limitations on inter-library lending (ILL). We will seek concessions that ensure end-users’ identifiable account information is not utilized inappropriately, and we will seek removal of any language that does not allow us to openly disclose the contract we have negotiated.
Almost everything is manual unless an import for an area is happening. Imports require a bunch of documentation and notifications before the data gets pulled in. The data is typically for building and addresses from the government.
Adding together OSM’s rules are stacked against imports, the vocal anti import contingent and specialized software knowledge needed means that few imports happen.
Generally, distros supply security updates. For example, Debian picks a version for a release and makes sure it has security updates for the entire release. Sometimes this requires backporting patches because the version is no longer supported upstream. This means an app can be shipped that will work for the life of the release without changes, while staying secure.
In theory, yes. In practice I'm very skeptical that maintainers can correctly backport patches without having a solid understanding of the source code. And I'm skeptical that maintainers can have a solid understanding of the source code without reading a substantial portion of it, and I know they haven't got the time to do that.
I’m sure what you’re saying happens. There’s 1000s of packages with maintainers of varying skill.
That said the track record speaks for itself. I can only remember one time a maintainer introduced a vuln in Debian. The system works even though you’ll find cracks if you look.
Addresses in OSM are in expanded format eg 100 south 35th street. What you’re entering is likely 100 s 35th st. Osmand looks for exact string matches so it won’t find the address.
Addresses in OSM are divided into their constituent parts, so you have separate house number, street (or place), city, suburb, country, etc.
Of course, you still need country-specific code to account for all the various abbreviations, e.g. Str. in German, or the cardinal directions and road type abbreviations common in the US (blvd, hwy, dr, etc. ... I've recently fixed a bunch of those in OSM and it's quite a list). Well, and checking alt_name, local names and names in other languages in OSM as well.
>To this end, all three institutions would like to reduce our spend with Elsevier by half of the current amounts paid by each institution. We are interested in obtaining a concession that would allow articles published by authors at each institution to be converted from closed to open access. We will be asking Elsevier to remove any limitations on inter-library lending (ILL). We will seek concessions that ensure end-users’ identifiable account information is not utilized inappropriately, and we will seek removal of any language that does not allow us to openly disclose the contract we have negotiated.