Classic Mac OS Software (Discussions on Applications) > Photo/Image/Graphics Viewing & Editing


(1/2) > >>

I looked into the source code of osmconvert. Then I wrote my own programs:
* Count OSM makes some statistics.
* Filter OSM removes unnecessary attributes.
* Renumber OSM renumbers the IDs sequentially starting from zero.
After the IDs are renumbered some data can be stored in arrays and the IDs can be used as indexes. This saves memory and it's faster than hash tables or trees. Calculating bounding boxes will be fast for example.

Now the data have to be turned into a quad tree. Then it has to be saved into one file so that everything that you want to draw can be retreived as fast as possible. I have never done this before. I have no idea where to start. Any advice?

Then I have to draw it. I'll use QuickDraw GX for the text and QuickDraw for the rest. I draw it at 200% and then scale it 50% using QuickTime. Then I'll have some antialiasing. If I define this in a plugin then you can write your own plugin.

And it has to be able to export PNG tiles.

OSM is a very good idea.

Iím close to bringing all OSM maps to OS 9. The main problem is the limited memory. The maps are now twice as big compared to 4 years ago. I have to anticipate that the size will increase further so all conversions have to be file-based. This means that for large maps a conversion will require multiple passes.

what memory size are we talking about?

400 MB was enough to renumber the map of Belgium.

Count OSM needed 16 minutes to process Belgium.osm (FW). Filter OSM needed 39 minutes to remove the unnecessary attributes from Belgium.osm (FW). Renumber OSM needed 34 minutes to renumber the IDs in Belgium.osm (ATA).


[0] Message Index

[#] Next page

Go to full version