Recent diary entries
'Data' is still linked to API 0.4
I guess Microsoft is feeling the pressure from the GCC toolchain and have made various version of their development tools available for free download. Getting eMbedded Visual C installed on my notebook involved copying registry entries from a second XP machine, but now it's running smoothly and integrating well with the debugger.
Now that the serial port works (another hiccup), I can write some NMEA code, bypassing gpsd.
Then I need to make some major changes to gosmore relating to API0.5 and the rapidly growing planet file. I also want to add searching of all tags (not just the names) and when duplicates are encountered they will be ordered from near to farthest.
So there's an exciting new version of gosmore in the pipeline. (Or frighting if you're the leading handset manufacturer and you recently purchased a mapping company).
It looks like the current version of JOSM is modeless. It is a step in the right direction (more user friendly) because most text editors (like the one I'm typing right now) are modeless.
The problem is that unwilling users are be bullied into using something that "should still be considered an alpha release".
The good news about API0.5 is that it simplifies things by getting rid of segments. The bad news about it is that referential integrity w.r.t. relationships may cause endless frustrations for newbies who may not know how to delete ways created in error. And some of the ways have become part of the 'multipolygon' relationship during the conversion to API0.5, so this is already a real problem.
I requested that 5 tiles be rerendered, but 2 of them was never rerendered and all my requests are ignored (not even queued)
But it doesn't matter since none-one is using the POI editor AFAIK. Mapnik and Frankieandshadow (and gosmore) will catch up soon enough.