Carlton & Nottingham love their Lions ([1] [2] [3] [4]) but I’m now mapping Gedling, and here is one of the latest photos of Gedling Church ([1] [2]), taken from near the top of Queen’s Avenue, to prove it:–

Queen’s Avenue is in the heart of Phoenix Farm Ward, and very close to the location of Phoenix Farm. The farm was demolished in 1954, just as the Estate named after it was being built (councillors, planners & builders love demolishing the old and building new estates) (one clue to the age of these houses is that they all have coal-holes).

The houses that I’m currently mapping all seem to have Royalty — and the then Royal Family in particular — as an (unannounced) theme:–

• King’s Avenue
• Queen’s Avenue
• Princess Close
• Mountbatten Grove
• Margaret Crescent
• Elizabeth Grove
• Philip Grove
• Charles Close

… See full entry

It took a few days before the penny dropped for me with this house-name from Imperial Avenue, Gedling:

For the benefit of those whose only connection with English is Received Pronunciation (“RP”):

Those speaking RP will always pronounce the ‘H’ in “his” or “her’s”. There are many regional dialects within England that would never pronounce the ‘H’ (mine own dialect was Yorkshire, although now diluted by spending 30+ years in Nottingham). It is most typical within colloquial English to hear the ‘H’ dropped in such words.

PS
What a classic street-name for the 1920/30s!

You may be interested to observe the anal retention (twice over) in this view of St.Mary’s Avenue, Gedling.

1. The first is in the spelling of the street, as in the signpost at left foreground. Notice the full-stop after the “ST” & the apostrophe within “Mary’s”. The street to the south runs parallel to St.Mary’s & is called “St.Michael’s” (same stop & apostrophe). Excellent. I’m with Lynne Truss on this.
2. The second is the weather being anal retentive, due to the presence of an inversion layer.

Chris Fawkes, the weather forecaster on PM, BBC Radio 4 (56:16), spoke of a weather balloon launched today at Nottingham (where I live) which measured the base of the inversion at only 100m from the ground. This inversion is pretty much country-wide and is responsible for some foul air, particularly in the cities.

… See full entry

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

I’m having stunning problems being able to debug terracer from within Eclipse and, after much investment of my time & attention, I am greatly concerned that it may prove impossible. I’ve asked for help in my bugreport & have received zilch. There has been small responses here (many thanks) but those have not helped either. One possible option is to use a different IDE. So, here is yet another attempt to prevent others from having to go through as much pain as me just to get the NetBeans IDE installed (help from NetBeans here + youtube here):

… See full entry

Goodness, but the folks in Gedling love their stick-men ([1] [2] [3] [4] [5]). The lady of the house told me that her grand-dad had made this one (unfortunately I had to use extreme digital zoom to get a decent view of it sat above the lintel of the front-door):

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

Sure enough, after working my way up Besecar Avenue I reached Phoenix Avenue and Boom! as I tried to create a new semi-detached house on the corner of Besecar & Phoenix terracer throws an exception. I did not mind that, but Eclipse carried on as if nothing had happened. Now, that is truly mean!

In my earlier Diary (7) Eclipse was accurately debugging on JOSM exceptions thrown by JOSM core. How do I launch JOSM from Eclipse so that Eclipse will react to exceptions thrown by JOSM plugins?

Gaah!

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

This is so annoying. I’ve got JOSM up and running in Debug mode from Eclipse (see the previous entries 1 ⇒ 7, but only if you have a great deal of time & patience). As per usual I’ve loaded Bing aerial imagery. You can tell that that is also in Debug mode as it has a vast listing printed over the top of the map down the left-hand edge, showing Cache stats, current zoom, etc., etc.. I wish I knew how to get rid of those, because it is very distracting.

My last survey began at Cantley Avenue (8 days ago!) so that is where I started adding houses in JOSM. A couple of nips ‘n’ tucks for the street, a bit of street furniture + some garages + surface-parking at the top of the street. That used terracer, but not in any way that should cause an exception. Next would be a semi-detached house, and that should definitely cause an exception if I put a tick in “create an associatedStreet relation”. So, I saved everything added up to this point.

‘B’ to switch on Building Tools + draw over the top of the house & select it, then ‘Shift-T’ to bring up the terracer dialog. Enter all the values & then do the thing that I haven’t dared to do for 6 months:– put the tick in to create the street relation + press ‘OK’ (then dive under the desk to avoid the shrapnel).

GODDAMMIT! It creates the semi-detached house + relation without a whisper of complaint. Oh really, that is simply too much. The first was 1+3 so next I do 5+7. Still no exception, but it does forget to add the street-name now into the house (it adds the add:street key/value into the house if associatedStreet for that street is empty, but not if there is any value in it). That’s a bug, so I start to feel a little better.

… See full entry

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

tl;dr: It seems that you simply need to be pig-headed & ignore all errors, clean the Build & restart & do it again (below is what I had to go through to discover this).

… See full entry

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

… See full entry

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’

… See full entry

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.

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.

… See full entry

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:

… See full entry

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.

… See full entry

I started mapping in March 2016, and began producing these Diary entries based on the results of some of that mapping shortly after.

An October post got a bit of attention: > The Smallest Street in Porchester Gardens, Nottingham

Afterwards, I realised that there was a street much more local to me that was just as short (The Street With NoName). In fact, in many ways it was even odder:

1. It had no name
   (noname=yes)
2. It provides service access for not a single house

Many of these no-name streets provide service access to the rear of some flats or houses, and once a week or so the bin-lorries will make use of it. Not this one. The tarmac is in good condition, but nary a vehicle makes use of it.

I only took some pictures today. I’m recovering from ‘flu and the pics are bad because of it (not very steady, as I was ‘cough, cough, cough’ all the time):

There is a very-mysterious “Gedling Wharf” on the OS_OpenData_StreetView north of Arnold Lane and, having finally been able to join together just what it was and where it was, I’ve added it to the map.

The Wharf (more accurately “Bottom Wharf” — see Gedling Country Park) was where Gedling Colliery distributed coal from the pit:– > - Coal was sold from the Top and Bottom Wharfs:
- The Top Wharf was at the top of the colliery site (now Chartwell Heights) and was the main selling point for domestic sales to local firms Leapers and Trumans. - The Bottom Wharf was closer to Gedling village (the old Grey Goose Pub, now Gedling Village Care Home). From here coal was sold directly from the weighbridge. Leapers would deliver coal collected from here to all local miners.

… See full entry

My September diary entry contained a view from near the top of Marshall Hill, looking north down the length of Chatsworth Avenue at the spire of All Hallows Church in the middle distance (All Hallows is the CoE parish-church for Gedling village). I believe that that was my first photo of that church spire.

My mapping since September seems to have taken me in a clockwise-rotation around the spire, and I am now approaching the church from the west.

Most householders do not like having photos taken of their homes, and I try my very best to respect that. At the same time, I know that panoramic shots of a district are one of the best ways to allow strangers to get a feel for an area, and I do my best to include such shots if I’m lucky enough to come across one.

Below is, I believe, only the 2nd shot that I’ve taken of the Gedling Spire. It is at a very similar distance to the first (as listed at top), but this time looking east from a walk at the top of Linby Close:—

OpenStreetView? You are no longer hostage to Google’s car-driven vision
(14 Dec 2016, The Register)

One of the great bright lights of open-source software and user-driven community projects is OpenStreetMap, which offers an open-source mapping platform similar to, but also very philosophically different than, Google Maps.

This review is about Telenav’s OpenStreetView. I find it a little odd, because it mentions OSM at the top of the article (extract above) and also has a link to Mapillary and yet, does not contain a single link to either the topic of the article (OpenStreetView) nor to OSM. Most odd.

Coda:

(with thanks to mmd (see comments)):

The Register review is already well out-of-date as, after OSV attracted the wrong kind of attention from Google, OSV changed it’s name to OpenStreetCam on 25 Nov 2016 and can now be found at openstreetcam.org.

Last Friday 9 December I thought that I’d spotted yet more Khazis on houses near the head of Perlethorpe Drive but in fact it was more interesting than that. These 1959 houses had been built with combo Wash-houses and Coal-Sheds.

These two are in superb condition:

(if you get a broken picture then try another browser)
(for me, this page is broken in Chromium though fine in Firefox)
(2016-Dec-12: upgrade to 55.0.2883.75 fixed the broken Mapillary photos)

It is soon to be Xmas and that is the starting-gun for spammers.

(15) 24 Hours since creation: 0 Edits, 0 Traces & 1 spam (removed - thank you) for a Hungarian Lockmaker: Zarkiraly (user removed)