OpenStreetMap

Diary Entries in English

Recent diary entries

qishan

Posted by Ghostpayroll on 16 January 2017 in English (English)

made it into the qishqn forest park.

very nice. bettercthan gushan

Location: 旗山水项古道, 双峰, Minhou County, Fuzhou City, Fujian, China

Egleton Triangulation Pillar

Posted by Peter Fowler on 15 January 2017 in English (English)

See TL08/T16 - Egleton.

I went out today to compare my Garmin eTrex 10's idea of the location of this Triangulation Pillar with the Ordnance Survey National Grid reference of 486466.32,306589.94 .

I am pleased to report that the Garmin read 52N39.0111 0W43.399 (WGS84 decimal minutes), the closest representation of the Ordnance Survey data. I converted the National Grid reference at Coordinate transformation tool to give 52N39.010738 0W43.399301, note that not all online co-ordinate conversion tools agree!

This pillar has a flush bracket with the number S6767.

I have added this as a point, in changeset 45201297.

I do not know that it is in the perfectly correct place as I do not know that Bing's idea of the absolute position of points on the earth's surface is the same as mine. OK, the location of my new point is 52.6501638, -0.723312, and it should be 52.6501790, -0.723322. Do I need to fix this, and if so, how?

Location: Egleton CP, Egleton, Rutland, East Midlands, England, United Kingdom

OpenStreetMap Community Statistics Revisited

Posted by SimonPoole on 15 January 2017 in English (English)

In November 2015 I produced a blog post on the relative sizes of our national communities and their development over time. When I updated the contributor stats on our wiki a couple of days back and looking at the massive impact the influx of first time users using maps.me have on the contributor numbers (not necessarily on anything else as I have pointed out in earlier posts), I thought it would be interesting to update the numbers and have a look at what has changed over slightly more than a year.

The most notable changes in the top 20 ranking by absolute community size are Russia overtaking France, Ukraine moving up 6 places and the Philippines moving in to the top 20 at the expense of the Czech Republic.

It is reasonable to assume that these changes are mainly due to the differences in the popularity of maps.me, No surprise and expected that it is most popular in Russia and the Ukraine, not so clear why it is so popular in the Philippines:

Numerous small changes in the contributors per capita ranking, but I suspect the fact to take away from this is that even in countries that already had the best results we are still improving the penetration levels.

In the first blog I singled out Germany and the United States as the two largest communities with very different growth patterns. Particularly in Germany there has been some concern as both the number of active contributors over short periods and the absolute number of edits have been decreasing slightly over the last two years. However new contributor influx does not show the same trend and we might put the “negative” trend simply down to the major urban areas of Germany being extremely well mapped.

As in 2015 the trend in the United States is very different, with a very large growth peak in December 2016. 3500 mappers in a month is roughly what would be required to grow at the same rate relative to population as Germany, so this should be a great achievement.

Unluckily it is not.

Closer inspection shows that a large number (in the 1000s) of the accounts created in December and in the proceeding months are fake accounts created by one or more SEO companies. While it is rather unclear if the data added itself is legit, the accounts themselves are not.

Back to numbers with a more positive context, the continental distribution of mappers continues to even out, while Europe continues to dominate, both Asia and South America have increased their relative share.

The raw data for the stats is available as LibreOffice Calc files. Notes on the methodology can be found in the original blog post.

Bugfixing terracer: 6. Importing the Project Bugs

Posted by alexkemp on 15 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

Under Compiling using Eclipse the Developers' Guide says:

Use Eclipse and the provided .project and .classpath file. Just import project using the JOSM core folder as root directory.

Those are brave words, but more than a touch useless for noobs like me (how do I do that?) (and exactly why do I need to compile anything anyway, since a full build is provided? I come here to debug a plugin, not compile it).

The nightmare of Black Friday 13 & Saturday suggest that I do need to import the provided project. So, here is how to do that (and, unfortunately, import the project's bugs at the same time):

  1. File ▸ Import
  2. (expand General) select Existing Projects into Workspace
    (press Next>)
  3. (click Browse... on Select root directory)
  4. select josm dir + press OK
     
    A ghost-in-the-machine now appears within the Projects box. The entire thing is grey rather than black (including the checkbox) and cannot be selected. After the initial checkbox, the text reads: josm (~/workspace/josm) (the dir in brackets is identical to the workspace dir that has been selected) (this result previously stopped me going any further). Under the dialog title (Import Projects) it says:

    Some projects cannot be imported because they already exist in the workspace

  5. (click Browse... on Select root directory)

  6. select core dir + press OK
     
    The text in the Projects box now reads JOSM (~/workspace/josm/core) and is both pre-selected & selectable.  

  7. Press Finish

Back at the main window a Building Workspace notice appears at bottom right. After a short while it concludes with 2 show-stopping errors:

  • The project was not built since its build path is incomplete. Cannot find the class file for AuthorizationProcedure. Fix the build path then try building this project
  • The type AuthorizationProcedure cannot be resolved. It is indirectly referenced from required .class files

Debug As ▸ Java Application on ~/workspace/josm/core/eclipse/JOSM (Java 8).launch now has a Proceed button (although errors are reported) and clicking gives the result:

The specified JRE installation does not exist

Not good, but it is progress.

Coda 1: Missing AuthorizationProcedure

This is located as follows (though atm I have zero idea as to why it is missing):

~/workspace/josm$ head ./core/src/org/openstreetmap/josm/gui/oauth/AuthorizationProcedure.java
// License: GPL. For details, see LICENSE file.
package org.openstreetmap.josm.gui.oauth;

public enum AuthorizationProcedure {
    /**
     * Run a fully automatic procedure to get an access token from the OSM website.
     * JOSM accesses the OSM website on behalf of the JOSM user and interacts
     * with the site using an OSM session, form posting and screen scraping.
     */

Coda 2: The source of this problem?

It begins to look likely that the source of this problem is that the 3.8.1 version of Eclipse provided with Debian Stable (Jessie) is much, much too old, and thus cannot support JAVA-8. My first clue on this came with a stackoverflow question. The questioner answered his own question:

This was fixed by changing my Eclipse IDE version from indigo to luna. Luna comes with support for Java 8 so all issues have now been resolved.

Luna is 4.4 and was released in 2014 so yes, 3.8 (Juno) will not work with JAVA-8.

As necessary cross-confirmation, with advice from here, the compliance level needs to be at least 1.8 (Window ▸ Preferences (open Java) Compiler ▸ JDK Compliance). If the JDK Compliance Level is not set to 1.8 (or better), then that version can NOT support JAVA-8. In my case it was 1.4 & has 1.7 as the maximum available.

Eclipse has an Installer which promises easy updates (release-notes). Advice from linuxconfig.org if you would rather go the direct route. For me:

$ cd ~
$ tar xpf Downloads/eclipse-inst-linux64.tar.gz
$ cd eclipse-installer
$ ls -Al
total 296
-rw-r--r--  1 alexk alexk  42735 Dec 14 10:58 artifacts.xml
drwxr-sr-x  4 alexk alexk   4096 Dec 14 10:58 configuration
-rwxr-xr-x  1 alexk alexk  80393 Dec 14 10:58 eclipse-inst
-rw-r--r--  1 alexk alexk    316 Dec 14 10:59 eclipse-inst.ini
drwxr-sr-x 18 alexk alexk   4096 Dec 14 10:58 features
-rwxr-xr-x  1 alexk alexk 134914 Dec 14 10:58 icon.xpm
drwxr-sr-x  4 alexk alexk   4096 Dec 14 10:58 p2
drwxr-sr-x  4 alexk alexk  20480 Dec 14 10:58 plugins
drwxr-sr-x  2 alexk alexk   4096 Dec 14 10:58 readme

$ ./eclipse-inst
java version "1.7.0_111"
OpenJDK Runtime Environment (IcedTea 2.6.7) (7u111-2.6.7-2~deb8u1)
OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode)

Notice how the damn thing is running JAVA-7, even though I've set the alternatives system to prefer JAVA-8. That makes me spit. However, it is up & running with Version: Oxygen Release Milestone 4 (4.7.0 M4), and is set internally to use JAVA-8, except that we now get 56 errors, 6,082 warnings, 17 others after building the workspace.

Fortunately, I spotted the name MapCSSParser, which was referenced as Mappaint MapCSS in the Wiki under 'Compiling':

  1. Go Help ▸ Install New Software...
  2. Add URL http://eclipse-javacc.sourceforge.net/
  3. Add name JavaCC Plugin
    (pressing Enter put it in the Work with selection, whilst JavaCC Eclipse Plugin appeared in the box below, and needed to be selected)
  4. Press Next>
  5. (version 1.5.33) Press Next>
  6. (accept license agreement) Press Finish
  7. (warning about unsigned content) (prats - accept it)
  8. Restart Eclipse

That only puts us into a situation where we can compile the required .java files from MapCSSParser.jj using the newly installed JavaCC (try to keep up). Unfortunately, the Wiki has the wrong location for this file. You can find it at ~/workspace/josm/core/src/org/openstreetmap/josm/gui/mappaint/mapcss/MapCSSParser.jj. Locate it within the package explorer, right-click on it & select Compile with javacc. When that completes all errors have gone, although there are now 6,299 warnings.

Debug As ▸ Java Application on ~/workspace/josm/core/eclipse/JOSM (Java 8).launch now launches the JOSM load window (I almost fainted, but it immediately stopped on Error: Unknown projection code & restored my faith in buggy builds!).

Bugfixing terracer: 5. wORD cASE bLINDNESS

Posted by alexkemp on 14 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

fRIDAY 13 jANUARY WAS NOT A GOOD DAY.

tHE vOGELLA TUTORIAL SAYS:

1.4. Starting the Debugger
To debug your application, select a Java file with a main method. Right-click on it and select Debug As ▸ Java Application.

tHAT SEEMS SIMPLE ENOUGH. hOWEVER, FINDING A main METHOD IN josm IS MUCH HARDER THAN AT FIRST IT SEEMS:-

~$ cd ~/workspace/josm
~/workspace/josm$ fgrep -ir 'main {' ./
./plugins/Mapillary/.svn/pristine/(removed).svn-base:  main {
./plugins/Mapillary/build.gradle:  main {
./core/src/org/openstreetmap/josm/Main.java:public abstract class Main {
./core/src/org/openstreetmap/josm/gui/MainApplication.java:public class MainApplication extends Main {

(aWARD YOURSELF A gOLD sTAR IF YOU SPOTTED THE -i IN fgrep)

sO, ONLY 2 SOURCE-FILES, + ./core/src/JOSM.java (DECLARED IN ./core/build.xml AS THE "Main-class"):

JOSM.java:
/*
 * JOSM main class (entry point of the application)
 */

  1. Main.java : public abstract class Main
  2. MainApplication.java : public class MainApplication extends Main
  3. JOSM.java: public class JOSM extends MainApplication

nONE OF THE 3 PROGRAMS ABOVE HAVE A Java Application AVAILABLE WHEN Right-click | Select Debug As IS TRIED. hOWEVER, Debugging a Java Program, tutorials.point POINTED OUT THAT THERE WAS A KEYBOARD SHORTCUT (i LOVE KEYBOARD SHORTCUTS) (PROGRAM NEEDS TO BE PRE-SELECTED WITHIN Package Explorer):

Alt + Shift + D, J

tHAT GIVES THE VERY WONDERFUL ERROR MESSAGE:

Selection does not contain a main type

...AND THAT LEADS TO HUNDREDS OF FORUMS & OTHER SITES ALL SAYING THE SAME THING:

Your class is supposed to be called ‘main’, not ‘Main’

i HAD TO GO AND SIT DOWN IN A DARKENED ROOM FOR MANY HOURS AFTER DISCOVERING THIS.

iT'S NOT POSSIBLE TO CHANGE THE NAME OF THAT CLASS (AT LEAST, NOT BY ME) AND i COULD NOT FIND ANY WAY TO RE-CONFIGURE eCLIPSE TO CHOOSE A DIFFERENT CLASS NAME. oN AN INSPIRATION, i LOOKED AT josm/core/eclipse/ AND DISCOVERED JOSM (Java 8).launch. rIGHT-CLICKING ON THAT & Debug As HAD A LAUNCH OPTION. oH! jOY!

cHOOSING IT GAVE AN ERROR MESSAGE:

Launch configuration JOSM (Java 8) references non-existing project josm.

cHECKING THE PROJECT CONFIG FILE + LAUNCH FILE CONFIRMED MY WORST FEARS:

~$ head -3 "workspace/josm/core/.project"
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
    <name>JOSM</name>
~$ tail -4 "workspace/josm/core/eclipse/JOSM (Java 8).launch"
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="JOSM"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="--debug"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="josm"/>

sO, JAVA WANTED AN ENTRY CLASS CALLED main & OUR SOFTWARE WRITERS CALLED IT Main. tHEN, THEY CALLED THE eCLIPSE PROJECT JOSM BUT IN THE LAUNCH FILE CALLED IT josm. i WAS DETECTING A TREND HERE.

bY THIS MOMENT IT WAS THE WEE HOURS OF TODAY (sATURDAY) AND i THOUGHT IT BEST THAT i GO & LIE DOWN IN THAT DARKENED ROOM AGAIN, THIS TIME UNTIL THE MORNING.

iN THE MORNING i RESTARTED THE COMPUTER & CHANGED THE PROJECT NAME IN THE LAUNCH FILE TO JOSM, THEN BOOTED UP eCLIPSE AND TRIED AGAIN. tHIS TIME, THE ERROR MESSAGE SAID:

Launch configuration JOSM (Java 8) references non-existing project JOSM.

bUGGER. iT LOOKS LIKE NO PROJECT MAY BE REGISTERED WITHIN eCLIPSE, EVEN THOUGH i RECALL THE SCREEN (BRIEFLY) FLASHING UP INFO ON REGISTERING IT AFTER THE svn CHECKOUT PROCESS.

bUGGER BUGGER BUGGER. i CANNOT FIND ANY MEANS OF REGISTERING/IMPORTING/CREATING/RE-CREATING AN eCLIPSE PROJECT. oH DAMMIT; DOES ANYONE HAVE A DOG i CAN KICK?

hOW ON EARTH CAN A WRITER NOT NOTICE THAT, AS ONE OBVIOUS EXAMPLE, THAT THEY HAVE THEIR cAPS-lOCK KEY ON AND THAT THEIR WORD CASE IS THUS ALL WRONG? i USE THE LINUX TERMINAL, SO I KNOW IMMEDIATELY IF THE CASE IS WRONG. i SUPPOSE THAT THESE GUYS ALL USE wINDOWS. bUGGER.

Coda: Restart Attempt

It got so bad that I decided to restart from scratch: shut down Eclipse, empty everything inside ~/workspace & redo Checkout Projects from SVN after opening Eclipse (concise list at bottom). When the Checkout was complete I went to workspace/josm/core/eclipse/JOSM (Java 8).launch & did right-click Debug As ▸ Java Application. It threw an error message:

Launch configuration JOSM (Java 8) references non-existing project JOSM.

Have the software authors changed that value to now be (correctly) upper-case? I've checked, and that's how it now is on the SVN server. Or did I get it wrong the first time? I am no longer certain. I only know that the damn thing will not work, no matter what I do. Even with completely default settings.

I cannot do anything further; time for bed.

Here is the concise list to setup Eclipse. Y'know, the list that doesn't work...

  1. Create an empty workspace dir
  2. Open Eclipse & select "workspace/" as the Workspace
  3. Remove the Welcome screen (click on 'x')
  4. Click on File ▸ New ▸ Other
  5. Open the SVN category and select Checkout Projects from SVN
  6. Press the Next> button in the Wizard
  7. Select Create a new repository location; press Next>
  8. Paste: https://svn.openstreetmap.org/applications/editors/
    ("Select/Create Location") + Press Next>
  9. Enter josm ("Select Folder") + Press Next>
  10. Select Checkout as a project in the workspace
    ("Check Out As") + Press Next>
  11. (use defaults)
    ("Select the project location") + Press Finish

Sault ste. marie ont canada

Posted by james guertin on 14 January 2017 in English (English)

today was my first time imputing to any mapping program kind feels like the old days exploring the new world lol James guertin

Location: Gore Street, Sault Ste. Marie, Ontario, P6A 1X3, Canada

Raster gpstrace tiles as OsmAnd overlays

Posted by HolgerJeromin on 13 January 2017 in English (English)

OSM has (since long time) raster tiles of all uploaded GPS traces.

Since a few days they are available as a overlay (like data overlay) on the OSM.org mainpage. Hurray.

This reminded me of using the overlay of mapillary traces for OsmAnd. The same is possible with the GPS traces!

The tileset addresses are:

https://gps-{s}.tile.openstreetmap.org/lines/{z}/{x}/{y}.png and http://gps-{s}.tile.openstreetmap.org/lines/{z}/{x}/{y}.png

In OsmAnd you can use (needs the online tile plugin active)

http://gps-a.tile.openstreetmap.org/lines/{0}/{1}/{2}.png

Step-by-step instructions are shown in Peters blog.

So now you can toggle the gps and mapillary traces in osmand whatever you are interested right now.

Bugfixing terracer: 4. Eclipse Debugging Routines

Posted by alexkemp on 12 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

Hours & hours of using terms such as “bugfix” as a search-string for Eclipse in Google were getting me nowhere. I finally broke through into sunlit uplands when I tried using “Debug|Debugger” as the search-string. That led to the following tutorial:

http://www.vogella.com/tutorials/EclipseDebugging/article.html

I'm getting very frustrated at this slow progress, but perhaps need to be a little less hard on myself. Remembering that my knowledge on all these apps was zilch at the start (just a little on using Subversion), I think that I'm heading in the correct direction.

Userbox: User Translator

Posted by dcapillae on 12 January 2017 in English (English)

I have created a new userbox for users who collaborate translating the OSM Wiki, a first userbox to make known the translation works of the wiki and promove them. The userbox includes a link to the wiki translation guidelines. Userbox:User Translator Image: Userbox “User Translator”. Source: OSM Wiki, OpenStreetMap Wiki contributors (CC BY-SA 2.0).

At the moment, the userbox is available both in English (Template:User Translator) and Spanish (Template:ES:Usuario traductor).

Bugfixing terracer: 3. Creating Eclipse Project

Posted by alexkemp on 11 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

Eclipse is an IDE (“Integrated Development Environment”). From the bug-fixing point of view, an IDE allows a program to be run until the program throws a software exception, when the IDE can re-appear, both showing the line within the source-code file that caused the error & giving opportunities to step forwards/backwards through the code, whilst examining changing values in key properties.

This is how Eclipse describes itself:-

Eclipse provides IDEs and platforms for nearly every language and architecture. We are famous for our Java IDE, C/C++, JavaScript and PHP IDEs built on extensible platforms for creating desktop, Web and cloud IDEs. These platforms deliver the most extensive collection of add-on tools available for software developers.

Having already used Subversion (SVN) to download the JOSM/plugins code, I thought that it would be easy to create a new Eclipse project from that directory, but could not find the way to do that, in spite of the advice in the Wiki:

Use Eclipse and the provided .project and .classpath file. Just import project using the JOSM core folder as root directory.

So, I decided instead to follow the YouTube Video to Checkout JOSM into Eclipse, even though it is years out of date.

  1. Create new workspace directory: ~/workspace
  2. Eclipse is installed on the system:

    :~$ apt --installed list | fgrep eclipse

    WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

    eclipse/stable,now 3.8.1-7 all [installed]
    eclipse-jdt/stable,now 3.8.1-7 all [installed,automatic]
    eclipse-pde/stable,now 3.8.1-7 amd64 [installed,automatic]
    eclipse-platform/stable,now 3.8.1-7 amd64 [installed,automatic]
    eclipse-platform-data/stable,now 3.8.1-7 all [installed,automatic]
    eclipse-rcp/stable,now 3.8.1-7 amd64 [installed,automatic]
    eclipse-subclipse/stable,now 1.10.3-1 all [installed]

  3. Use the URL:

    https://svn.openstreetmap.org/applications/editors/josm/

    IIRC that created both JOSM core + the plugins as one operation, with the base at ~/workspace/josm. It also created the Eclipse project (“Checkout as a project in the workspace”).

  4. Selecting core/build.xml + compile created josm-custom.jar in directory core/dist

  5. Running that file launched JOSM in the normal way:

    ~/workspace/josm/core/dist$ java -jar josm-custom.jar

I also tested compile + dist [default] for terracer. It produced ~/workspace/josm/dist/terracer.jar, which seems to be the identical file that was downloaded via SVN. My main concern on that at this moment is that I'm uncertain whether the SVN JOSM that is launched this way is using the Plugins available from local SVN download or the set of plugins available from the Debian install. I guess that I'll find out eventually.

I made a survey on Tuesday of Besecar Avenue (my next survey target in Gedling) & have compiled all the houses ready to enter under JOSM. Today (Wednesday) has been blowing cold & strong all day, and snow is forecast for tomorrow & the rest of the week. Brrr!

I now need to find out how to launch Eclipse in bug-checker mode, and it should then be Go! Go! Go! Hopefully.

Mapping bus route in Ayacucho - Perú

Posted by karitotp on 10 January 2017 in English (English)

As part of the goal of making Ayacucho the best-mapped city in Latin America, the OSM community of Ayacucho, along with the Mapbox Perú team, added 20 bus routes relations to OpenStreetMap of 22 public transport services that there are in the city.

bus1 Bus routes added in Ayacucho

During the mapping, 41 public_transport = stop_position and 15public_transport = platform has been added/updated in downtown.

public Stop_positions and platforms of public transport added in Ayacucho

Our local knowledge was fundamental to this mapping, however, many of the added relations are still incomplete because we do not know the complete route of some buses, such routes are being completed by using tools such as Osmtracker.

MapThe.UK with Mapillary support, over 3000 Schools mapped

Posted by Christian Ledermann on 10 January 2017 in English (English)

To make it easier to identify schools Schools.MapThe.UK now displays Mapillary photos near the school location.

Mapillary example

Mapillary example

Bugfixing terracer: 2. Errors whilst Compiling using Ant

Posted by alexkemp on 10 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

Having used SVN to install the whole of the build directory into ~/josm, the developer's Wiki says:-

The easiest way to compile JOSM ... is to go to the josm directory and type: ant.

Hah! This is what happened to me:

~$ cd josm    
~/josm$ ant    
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar    
Buildfile: build.xml does not exist!    
Build failed

The reason for the error is that I've only got the JAVA-7 JDK installed (the default JRE is JAVA-8, but that is the runtime environment, and it is the development kit that is needed here):

~/josm$ locate /tools.jar
/usr/lib/jvm/java-7-openjdk-amd64/lib/tools.jar

The fix is to install the missing openjdk-8-jdk, which I do via Synaptic. The result is still disappointing:

~/josm$ ant
Buildfile: build.xml does not exist!
Build failed

This is getting boring. build.xml is the buildfile (configuration-file) for the compiler. It's default location is within the root of the directory from which the compiler is launched (./). Naturally, there isn't a buildfile in the base directory, though there is within core/ & other directories. Which one to use? Who knows?

I try to use an intelligent pin:

~/josm$ ls
core  dist  i18n  plugins  webgrabber
~/josm$ cd core
~/josm/core$ ant
Buildfile: ~/josm/core/build.xml

init-properties:

init:
    [mkdir] Created dir:~/josm/core/build
    [mkdir] Created dir: ~/josm/core/dist

javacc:
    [mkdir] Created dir: ~/josm/core/src/org/openstreetmap/josm/gui/mappaint/mapcss/parsergen
     [exec] Java Compiler Compiler Version 6.1_9 (Parser Generator)
     [exec] (type "javacc" with no arguments for help)
     [exec] Reading from file ~/josm/core/src/org/openstreetmap/josm/gui/mappaint/mapcss/MapCSSParser.jj . . .
     [exec] Warning: Line 4, Column 3: Command line setting of "OUTPUT_DIRECTORY" modifies option value in file.
     [exec] Warning: Line 168, Column 5: Non-ASCII characters used in regular expression.
     [exec] Please make sure you use the correct Reader when you create the parser, one that can handle your character set.
     [exec] File "TokenMgrError.java" does not exist.  Will create one.
     [exec] File "ParseException.java" does not exist.  Will create one.
     [exec] File "Token.java" does not exist.  Will create one.
     [exec] File "SimpleCharStream.java" does not exist.  Will create one.
     [exec] Parser generated with 0 errors and 2 warnings.

compile:
    [javac] Compiling 360 source files to ~/josm/core/build
    [javac] Note: ~/josm/core/src/oauth/signpost/AbstractOAuthProvider.java uses or overrides a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] Compiling 51 source files to ~/josm/core/build
    [javac] Compiling 1455 source files to ~/josm/core/build
    [javac] ~/josm/core/src/org/openstreetmap/josm/gui/layer/OsmDataLayer.java:901: warning: [deprecation] isChanged() in Layer has been deprecated
(many other similar deprecation & other warnings removed)
    [javac] 8 warnings
     [copy] Copying 1 file to ~/josm/core/build

init-svn-revision-xml:

init-git-revision-xml:

create-revision:
   [delete] Deleting: ~/josm/core/REVISION.XML

check-schemas:

epsg-compile:
    [mkdir] Created dir: ~/josm/core/build2
    [javac] Compiling 1 source file to ~/josm/core/build2

epsg:
    [touch] Creating ~/josm/core/data/projection/custom-epsg

dist:
     [echo] Revision 11444
     [copy] Copying 1 file to~/josm/core/build
     [copy] Copying 1 file to ~/josm/core/build
     [copy] Copying 1 file to ~/josm/core/build
      [jar] Building jar: ~/josm/core/dist/josm-custom.jar

BUILD SUCCESSFUL
Total time: 1 minute 40 seconds

That is a horrible, large number of warnings, but it works now!

Bugfixing terracer: 1. There May be Troubles Ahead

Posted by alexkemp on 10 January 2017 in English (English)
  1. There May be Troubles Ahead
  2. Errors whilst Compiling using Ant
  3. Creating Eclipse Project
  4. Eclipse Debugging Routines
  5. wORD cASE bLINDNESS
  6. Importing the Project Bugs
  7. Have you Tried Restarting Your Program, Sir?
  8. Show Your Bugs, Damn You!
  9. Be Careful What You Wish For
  10. Installing NetBeans

terracer is one of the JOSM standard plugins. Almost all of my work updating the map involves adding houses in Nottingham, and most of those are either Terraces, Semi-Detached or Detached houses; terracer is invaluable in adding any or all of those houses.

Unfortunately, terracer began to show bugs soon after I started using it, and it rapidly became impossible to use any of it's Relation capabilities. JOSM core was being rewritten to move from JAVA-7 to JAVA-8 (now complete), and I have a suspicion that terracer was written in the days of JAVA-6! Whatever the case, it has degraded throughout 2016 & is now almost completely unusable (at least in my experience).

6 months or so ago I declared that I wanted to bug-fix terracer. I've spent all the time since then finding excuses to put off making that promise good. It's not that I don't want to. It's simply that, whilst the weather is good enough, I want to get out of the house, make the survey, then get it up on the map. Before Xmas I caught two new 'flu on the run; it took until Sunday, 8 January before I finally overcame the Bronchitus & felt strong again. Today the weather forecasters promised Britain a blast of Siberian air & snow by the end of this week. So, I've finally run out of excuses...

I've done a little C/C++ Linux/Windows programming + command-line x-compilation & bugfixing plus lots of PHP, HTML, javascript, database & other scripting, but have little experience with SVN & zero experience with ant, Eclipse and/or Java. So, as the Chinese proverb goes, the future should be interesting.

I'm writing this up as a Preface to the whole thing, and expect to have numerous posts in the future as I meet (and hopefully fix) yet another snag along the route. The only help I've been able to find so far is:

https://josm.openstreetmap.de/wiki/DevelopersGuide

Steps taken so far:

  1. This is the platform I'm using:
    ~$ lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description: Debian GNU/Linux 8.6 (jessie)
    Release: 8.6
    Codename: jessie

  2. Here are relevant installed applications:
    (some results removed):
    :~$ apt --installed list | egrep -i 'ant|eclipse|jdk|subversion'

    WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

    ant/stable,now 1.9.4-3 all [installed,automatic]
    default-jdk/stable,now 2:1.7-52 amd64 [installed,automatic]
    eclipse/stable,now 3.8.1-7 all [installed]
    openjdk-7-jdk/stable,now 7u111-2.6.7-2~deb8u1 amd64 [installed,automatic]
    openjdk-7-jre/stable,now 7u111-2.6.7-2~deb8u1 amd64 [installed,automatic]
    openjdk-7-jre-headless/stable,now 7u111-2.6.7-2~deb8u1 amd64 [installed,automatic]
    openjdk-8-jre/jessie-backports,now 8u111-b14-2~bpo8+1 amd64 [installed]
    openjdk-8-jre-headless/jessie-backports,now 8u111-b14-2~bpo8+1 amd64 [installed,automatic]
    subversion/stable,stable,now 1.8.10-6+deb8u4 amd64 [installed]

  3. Install sourcecode via SVN:
    (the following also creates /josm (for me, /JOSM already exists)):
    ~$ svn co http://svn.openstreetmap.org/applications/editors/josm

    ~$ du -h --max-depth=1 josm
    24K josm/webgrabber
    356K josm/i18n
    533M josm/plugins
    235M josm/core
    428M josm/.svn
    54M josm/dist
    1.3G josm

OSM go - Nodes and Data (EN)

Posted by -karlos- on 9 January 2017 in English (English)

London

It’s still fun to improve "OSM go" and add new features. After adding some lines of code, and trees get visible; and there are really a lot of trees in OSM. The main idea still is visualising OSM data. A really realistic view may be possible and may be done (much) later (As teamwork with OSMBuildings and OSM2WORLD, I hope)

We made an experiment: OSM2WORD offers to export an area as 3D format “obj”. And "OSM go" is able to show this, including colours. Jan (OSMBuildings) exported some areas to test, they may be used as 3D-tiles in an thin client. Works fine: Twitter-Post

The controls have been reworked generally. Now there are two ways to move and look around, the 'Inspection-' and the 'Segway-Mode'. 'Inspection' is default, use the key “C” to change the mode. 'Inspection' is what you know from other 3D renderers like OSMBuildings: By keys, you move your point of view, by mouse or touch, you move the 3D world.

To see all improvements and details, drop by or follow Twitter @OSM__go. To test the latest version of "OSM go", use the new web URL OSMgo.org. There you will see almost daily changes. Its work under construction! It may work or just crash because its also my online test sandbox! You may try older versions at OSMgo.org/versions. And all information to “OSM go" is on the wiki page

Nodes & Data

The first versions of "OSM go" only showed ways or areas, no POI. But now the Overpass query is extended to get all nodes to. It startet by an student of HSR Rapperswil. He tested how hard it is, to extend OSM2WORLD to add 3D models of ‘’’tables’'' with chairs (amenity=="table”). It worked fine and I got the code to, rewrote it to Javascript and so the first OSM object was visible in "OSM go". It motivated me to write a small library to create 3D types dynamically by the actual OSM tag values. I also also added a more popular OSM node leisure==“picnic_table”. Because I was on holiday at the seaside at that time, I also added "generator:source"=“wind”. This is now the first animated node type. Exiting to visit a wind park and see them all spinning.

Tische

There are so many different node types, to much work to build them all in 3D. But anyway, now (almost) all nodes are visible, mostly by a read tetrahedron. It is a big step to the goal of "OSM go", to make all OSM data accessable. Klick on a 'red gem' to get all the tags listet. There are quite a lot of nodes visible now! For some, it is not really useful to show them:

  • If it is only a level tag of a way, it will not be visible. Also if it is only a tag "created_by"
  • It doesn’t make sense to show a railway- or highway-crossing, does it? It is visual by the ways crossing anyway. What about imaginary objects like stop positions of “public_transport”? There may be a busstop sign anyway. You may want to see this abstract “ghost objects” or not. User the new URL parameter “&abs” to decide, default is off.

Now or then, types of nodes will be designed in 3D. The first are realised: “natural"==“tree” and “barrier"==“bollard”. That was rather easy. A busstop will be more difficult because each country may have it’s own sign. Sure, they could all be put in a “database”. Much work. Firstly I will use the same symbols as the 2D renderer.

Reasendly I did not find a power:substation, which I had seen before. So an url parameter “&f=“ for filter/find was added. It checks tag names, values and OSM ids. The found objects may be marked by spikes or exposed by dimming all other objects. Quite impressing to use (try “f=!surveillance”!). And it is again a step to OSM data handling. See the Wiki for details.

Filter

Rendering in the 3rd dimension

Inspired by a drawing of the London underground I wanted to make some “in earth mapping”. Now the subway tubes are visible as such. It took me a few days of trying until the steps were really correct going up and down in 3D. It is written in the Wiki: Steps don’t need level tags. Levels are defined by the connected nodes or ways anyway. A big problem is the meaning of the tags level and layer. This could get us into an extended discussion. To see under ground without “diving down" by the keyboard commands you may use the experimental URL parameter “&sub=1"

Untergrund

What if a building height is not defined? There was an default by 6m. But now it is calculated by the footprint of the building, the bigger the more height. This is still incorrect but looks much better than an unique value. On the other hand: How do I see, if a building lacks height and levels? Now there is another URL value “&hei=“ to set your own unique height. try “&hei=0.5” and you will see clearly the difference (looks like in "Pokemon GO” :-)

Fighting the render time

All that improvements used to increase the needed render time! My knowledge to optimize this is limited, anyone like to help? Luckily, to show OSM data, it is not necessary to show Buildings till the horizon. Less level of details will be done for remote tiles eventually. Additional time is needed to download tiles in the background. That has been reworked some times already and will be again.

Anyway, the handling of SOM go may get nasty, if many objects and greater areas are shown.

  • Press Shift-L to reload the scene with only the local area.
  • Hit the key H to see the dt between frames and the frames per second (fps) actual and as less or more average.
  • Switching of the shadows by “&sha=0” may help a bit.
  • To keep the FPS above 5, now the far-plane will be reduced, remote buildings and roads will disappear. You may set this limit even to 0/off by the URL parameter “&fps="

Next?

First steps to a real tile handling; deleting tiles is necessary. The fps must be stable to keep the keyboard handling running. May be a "3rd person view” will clarify how a user may move in the 3D world. The Cardboard-Mode is under construction: Head twist should control direction and speed. The data display must be more large for smartphones.

I am not sure about the user experience. What should be changed, improved, added? I would apprichiate any feedback. Please do a test, send me screenshots of your favourite places. Tell me what you dislike or enjoy.

Private Road

Posted by Huttite on 9 January 2017 in English (English)

I just realised it has been 18 months since I made a diary entry! Rather than writing diary entries, I have been busy mapping. It has been over a year since Andrews Bridge at Birchville collapsed (on 29 October 2015) and I subsequently mapped this in OSM, along with the then proposed emergency access road that the Upper Hutt City Council had commenced building. Within days of me adding the proposed road as an OSM way another OSM mapper had plotted it using GPS! I was impressed. And the road was still being built, too! (This even motivated me to get my own GPS unit.) Since then I have been back and forth over this Private Road many time, usually with my own GPS unit plotting my track. (One day I should upload these tracks to OSM.)

A few days ago I sort of fell over the OSM Inspector and went back and looked at some of the work I had done over the last 18 months. I came across a few issues, but nothing that I couldn't correct fairly easily, except that Bridge Road remains an island, despite being connected to the rest of the world by a "Private Road" even though I have changed the tags on the way to indicate there is designated restricted access rather than the road actually being "private".

I suppose this OSM Inspector issue actually makes sense. Because the Private Road is not tagged as a public road so there is no publicly available routing to Bridge Road. Hopefully the issue will be resolved once the new bridge is installed - I am told - at the end of the month. Currently only the foundations are in place. So I think I will need to wait until opening day, so I can walk across the new bridge while plotting a GPS track.

Location: Totara Park, Upper Hutt, Upper Hutt City, Wellington, New Zealand

2016 Washington New Users Report

Posted by Glassman on 9 January 2017 in English (English)

This is the second annual results report on welcoming new mappers. 2016 saw a large increase in new mappers in Washington State over 2015. Also a record number, 403, welcome messages sent. Last year I reported sending 106 messages with a 9% response rate. This year the response rate was 7.4% which I partially attribute to the larger sample size and to the increase in MAPS.ME users who seem to never respond.

Recently I starting using Toby Murry's ChangesetMD tool to help identify new users. While I'm still using the IRC-Bot to identify new users, I expect to switch over to using minutely changesets with Toby's ChangesetMD tool.

Using the new tool I was able to start capturing some new data.

  • Total new users in Washington State = 562
  • Welcome Messages Set = 403
  • Responses received = 30
  • Response rate = 7.4%
  • Percent of new users getting a Welcome Message = 72%
  • Total number of changesets by new users = 14,119

Editor Used

  • iD 474
  • MAPS.ME 53
  • Potlatch 18
  • JOSM 5
  • Go Map!! 4
  • OsmAnd 4
  • Rosemary 2
  • Gnome Maps 1
  • Vespucci 1

Some interesting statistics

  • Average number of edits by users that received a Welcome Message = 29.0
  • Average span [1] of days editing by users that received a message = 17.4
  • Average number of edits by users that did not receive a Welcome Message = 15.2
  • Average span [1] of days editing by users that did not get a message = 13.6

The numbers are encouraging me to continue to send Welcome Messages to new users. I plan to add a section with suggestions of what to edit. Cities like Seattle have quite a few features already mapped which might discouraged new users. Conversely, rural cities are pretty barren which can be just as discouraging.

Check out my current process on GitHub which includes my updated Welcome Message which includes a link to tips for Pokemon Go users.

[1] span = the number of days between first edit and last edit.

Clifford

Fixing routing errors from alternativaslibres faster

Posted by Rodrigo Rega on 8 January 2017 in English (English)

I just writted a new post in my blog about fixing routing errors from alternativaslibres faster.

If you use this error reportings from alternativaslibres check it out!

#PDCSurabaya Destroyed Surabaya (and clarification below)

Posted by everyone_sinks_starco on 8 January 2017 in English (English)

= Update: See the comment section for clarification from HOT OSM Indonesia. Thanks bro/sist, they're do what I thinking about during writing of this rant =

My first entry is full of rants and criticism to HOT OSM Indonesia team, the people behind #PDCSurabaya event, who allowed their participant to corrupt and demolished much of Surabaya's data integrity on OpenStreetMap.

Despite all of "hard work" they made, I have discovered that before I partially fixed them (Gedung Keuangan Negara, schools and post office in Central Surabaya, name a few), many of already-good map data in Surabaya on OSM was lost or mangled. Building polygon 'merged' into area polygon as part of relations, and relations have much non-standard basic entries (address, school ownership and others, but I appreciate data additions about buildings although it is inaccurate), making it very difficult to simplify for better rendering on much-universal OSM data-based applications. Also, all third- (kodya), fourth- (kecamatan) and fifth-level (kelurahan) administrative borders are wiped (addition: not just wiping, they REALLY corrupted them. Querying locations around the Surabaya returned with empty Enclosing Features, and showing maxlat uncaught exception error on browser's inspect tool. This is never happened outside Surabaya where administrative borders are preserved). Polygon quality are mixed, mostly poor.

If HOT OSM wishes to make another PDC on other cities in Indonesia, PLEASE RESPECT OLD DATA BEFORE EDITING! It is a valuable basis and example to be copied for the project, not egoistically wiped them for your mangled data, which for me, needs more clarity. Government or individuals must openly provide data to them, to ease their work, especially on administrative border. If you want good example, see what I mostly have done in Denpasar and Amlapura (my hometown). Unfortunately I have no time to do mapping recently due to my own real-life issues.

To be honest, they should go outside the home for REAL survey.

And yeah, OSM Indonesia should expand beyond their disaster preparedness-related agenda, as OSM community in other countries RARELY made OSM just for disaster-related mapping. It is disastrous.

Location: the first entry where I have fixed building/landuse polygon amalgamation issues arising from #PDCSurabaya data demolition party.

== Everyone Sinks Starco ==

Location: Jalan Indrapura, Surabaya, Bululawang, East Java, 60175, Indonesia

Don't just do a mechanical edit, look at the area and look for other mistakes!

Posted by rorym on 8 January 2017 in English (English)

I am using Osmose to find and fix polygon errors in Ireland. I fixed a problem in a golf course in Youghal, Co. Cork. I could have stopped there, and moved on, however the JOSM validator found some errors, so I kept working on that little area. This led me to spot some not great mapping around a school. Some houses tagged with name=Residential Dwelling, that kind of thing. I cleaned up the area. Removed unneeded name tags, fixed tagging of roads etc. I found the mapper, and changeset where this was added, and was able to leave a changeset comment on it. I'm not the first to notice, but maybe this mapper might return to OSM.

So I feel like I have improved the map in this area. I would not have known to look there if I hadn't use a QA tool like Osmose, or the JOSM Validator. However if I was just looking at closed polygons, then I would have stopped as soon as I fixed that polygon, and moved on.

At State of the Map 2016, Frederik Ramm talked about Mechanical Edits, and one problem he finds with mechanical edits is that sometimes people just mechanically and automatically fix the problem that the QA tool has found, rather than looking at the area, or other contributions from the same mapper, and try to fix the larger problem, and fix other problems. There is often talk about more automatic and manual imports, with some suggesting that humans are expensive, let's not use them too often. But you need to have humans there, to find and recognise other mistakes which the tool can miss, as my example shows.

Older Entries | Newer Entries