Hi Léo_M

Since I was working in JOSM using Esri World Imagery (much better than any of the other imagery) I right-clicked on the display & chose “Show tile info”. Annoyingly no Copy available so laboriously typed in the URL & downloaded the tile. The dates in the metadata were entirely for the instant that it was downloaded. What a waste of intelligence.

$ file 260547 260547: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 256x256, frames 3
$ exiftool 260547
ExifTool Version Number         : 10.40
File Name                       : 260547
Directory                       : .
File Size                       : 11 kB
File Modification Date/Time     : 2019:03:11 10:35:39+00:00
File Access Date/Time           : 2019:03:11 10:35:39+00:00
File Inode Change Date/Time     : 2019:03:11 10:35:39+00:00

Here’s a couple of help-hints:-

• Getting started (forum)
• Beginners’ guide (wiki)

Hello masowd1407

No-one is stopping you from adding it. If it exists then add the town, to whatever level of detail that you see fits.

Hi @majkaz

Well, that was excellent feedback, and they ignored it. In fact it is worse now, since you can only edit your own blurs; any stupid blurs from any other source must remain.

Hi westnordost

My recall from early days is that yes, it is a so-called intelligent algorithm. I certainly hope so, since that is the reason that I keep plugging away making the edits.

My main worry is that there has been zero feedback (support says “I have fed your comments to the developers”, but nothing other than that) & zero changes to edited photos. This means that I am unsure whether my edits are even connected to Mapillary & their routines at all.

@TheSwavu:
Are you saying that only non-network connected client GPS devices greater than 20 years old will suffer problems on April 6? I certainly hope that you are right, though you may have more belief in software writers than I do.

My recall shortly after the Millennium rollover was that an analogue modem stopped working and Y2K was blamed for that by the driver supplier. I recall distinctly being boggled that (completely seriously) Y2K could stop a modem from squawking.

It is not the Smartphone time that is the issue; as you say, ’phones get their time from the network, not GPS.

the GPS rollover doesn’t affect the ability to provide accurate location data

Clearly you do not understand GPS, else you would understand that the embedded-timestamp within the GPS-satellite server-signal is integral to all client GPS devices being able to derive their location from that signal.

Try How does GPS work?:–

(GPS-satellite signals) are intercepted by your GPS receiver, which calculates how far away each satellite is based on how long it took for the messages to arrive.

Thus, the receiving device needs:

1. To accurately know what time of day it is, independent of the GPS satellite
2. To check that time against the embedded GPS signal time from a number of GPS satellites (speed of light)
3. Between the two to work out each of those satellites’ distance from itself
4. To integrate the whole set of data to calculate it’s own location.

It is at #2 above that the 2¹⁰ allowance becomes an issue.

WhatIsMyBrowser will give some broad feedback on what meta-data your browser shows to servers on the net (although it is not specific enough to distinguish between en-GB & en-US). Mine is Chromium (open-source version of Chrome) and Language Settings are at chrome://settings/languages.

Arul John sucessfully shows that although it misses on how to setup language for Chrome (must be old; advice given for FireFox, MSIE & Opera).

Bah! I forgot to say that these scripts all produce raster results. I have never seen any vector (EPS) results.

Hi there Krijn
I know almost nothing about this, so take my response with a dose of salt.

From some words at the bottom of this GitHub page I am confident that you will need to make use of nik2img.py (a Python script, I believe). There is also some outdated help here.

And, sadly, that is where my help runs out.

Hi @Rovastar

Did you not update the image used?

Well, so far I’ve had to learn about SVG1.1, SVG1.2, SVG2.0, Inkscape, GitHub & git, Bleed & crop-marks, printing from PDFs, pdfunite, unix2dos - and all without a scap of formal education in these things. Somehow I found myself avoiding updating any of the source PNGs for the leaflets during that process. And yes, it is more than a few years out of date.

I would be most happy to accept donations from anybody of replacements/alternatives for any of the PNGs, but particularly:

globe_part_halo.png (front cover)
london.png (inside 2-pages)

For my own situation (I live in Nottingham) I thought that a map of the heart of Nottingham would be suitable to replace london.png, and I’m quite certain that Americans, Australians, etc. want something less Eurocentric for the front-cover & middle. I would be most happy to accept pushes with PNGs of other places. The SVG is set for 96dpi.

For the alternate (osmflyer1-2) I’ve placed the London map under a mask, so any PNG that you provide could be a more generous size. I have thought that it would be best to bleed it off at top & bottom & did not only because I was concerned that the resolution might then be too low.

Hi @zarl

Inkscape has an option during the Save As…(PDF) process to add bleed to the PDF. It also auto-saves the PDF in PDF/X, adding font glyphs to the PDF. There also appears to be options to add a colour-profile, though I never explored that.

I think that the padding issues came about due to a combo of:

1. The change from 90dpi to 96dpi in SVG standards
2. An error on either my and/or Inkscape’s part during the update
3. Ignorance on my part to spot the possible error, and mistaking the effects of bleed (which is actually margin) for padding.

The bottom line is that the printer I used was able to use the PDF to produce a print accurate to the drawing.

We cannot read your hard-disk. Upload the file to a host-site then use the Markdown for an image and we will be able to see the picture.

Also, please remove the nonsense-letters above/below your hard-disk location.

Thank you.

Howdy @Laurent (sorry for using English)

You will find help at osm.wiki/Tag:amenity%3Dparking . Near the bottom of the table is capacity:disabled.

HTH

@Rovastar:

“Allow only verified active mappers to vote and run for the board” This will never pass here.

Ask yourself a simple question:
“Do I want anyone that does NOT have OSM’s best interests at heart to have a say in it’s governance?”

I would suggest that the answer is that you want all those that govern what & how OSM does what it does should have OSM’s best interests at heart. If you agree with this, then the next question becomes:

“Is there a way to measure whether a person has OSM’s best interests at heart?”.

The answer is “Yes there is”. If they want OSM to succeed, then they go out and do some mapping. If they do NOT map for OSM it does not mean that they hate OSM. It just means that they do not like mapping, and therefore are (at best) indifferent to OSM. Now, I don’t want folks that are indifferent to OSM on the OSMF Board. I want folks that are committed to OSM. And if they are committed to OSM then they will, of their own desire, go out & do a little mapping each month (at the very least).

Finally, if they are NOT committed to OSM and they are on the OSMF Board will they please go off and do something else that they are committed to because, frankly, we don’t want them here.

Hi rorym 🏳️‍🌈

● Allow only verified active mappers to vote and run for the board

very easy to game and fix with a bot

First, let’s point out that this is one option promoted by the OSMF Membership Working Group (MWG) in their PDF as part of a suite of actions to try to stop future influence campaigns from rendering OSMF elections unfair and/or distorted and/or utterly corrupted.

Second, yes indeed, agree totally. For that reason I assume (and sincerely hope) that rate-limiting is normal on the OSM servers to prevent classic bot-spam activity. I dealt with this on a daily (hourly!) basis 15 years ago when I ran a website + forum on an internet server. It is reasonably trivial to stop bots by this method (they always run as fast as they can) although I found that the SEs can tend to also mimic bots as they scrape the site, which then leads to difficult decisions on whether to white-list those SEs.

Third, if the premise of active, verified mappers is accepted, then it becomes necessary to compile a list of bots to form a further blacklist to prevent signups. I’ve actually advocated this before by pointing to SFS as an open-source compiler of sources of both bot- and human-spam which has proven itself as both safe and successful in stopping such malign behaviour.

These are the options that (it seems to me) MUST be adopted:

• Verify OSM usernames when they are entered
• Require affirmative email confirmation of new memberships
• Allow only verified active mappers to vote and run for the board

The last one, in particular, seems vital. Why on earth non-mappers, or those that mapped a little then gave it up, are allowed to be on the Board is beyond me.

My extra suggestions are:

• One vote per OSM username per election
• One vote per IP, if that IP resolves to a business

@mmd:
Thanks for the link to the Markdown syntax; I’d wondered about that myself.

PS
Pointing out that something is wrong is not ‘abusive’ in itself, it is simply factual.

It is one of my most common comments. This was the latest (author fixed it very quickly).

I would have suggested a different route if you are using Inkscape to produce a printed-map.

Instead of:

SVG → PNG → JPG

…use:

SVG → PDF

The main advantage becomes that you would retain all vectors & text as mathematical curves, which means a highly-professional end-product (most essential for very small text + map-features). PDFs are found via the File | Save-As option (choose ‘PDF’ from the drop-down at bottom-right).

Note:
The SVG file is designed as Inkscape’s native file-format. In certain circumstances it will make use of v1.2 methods which are now deprecated (web-SVGs can only use v1.1 features until v2 gets accepted). If you try to use the native SVG on a web-page it will show odd artifacts if it contains any v1.2 features.