[OSM-talk] Local map making - truncating ways on boundary?

[Dirk-Lüder Kreie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karl Newman schrieb:
| On Thu, Apr 3, 2008 at 7:38 PM, Brett Henderson <brett at bretth.com> wrote:
|
|> I hope the job loss isn't too much of a downer, best of luck finding
|> something better.
|>
|> As for tiling, I hadn't considered polygons.  They sound nasty.  I'd
|> been thinking of something far simpler.  For ways I was thinking of
|> splitting them at tile boundaries, adding synthetic nodes as required,
|> and creating new way ids where one way becomes multiple ways.  Polygons
|> change all that.  Initial thoughts are just detect closed ways and split
|> accordingly to make closed polygons inside each tile.  It sounds like
|> that may not be appropriate though.  Splitting polygon types according
|> to tags and rules adds a huge level of complexity and will constantly
|> require updates as new tags and polygon types are defined.  I also get
|> the impression from your wiki page that this will be very Garmin
|> specific, and perhaps that's the only way to go.
|>
|> I'm going to have to back away slowly from this one and pretend I didn't
|> see anything ;-)
|>
|
| Well, I knew about my job loss since November. I have a couple
prospects in
| the works (I'm an automation/controls engineer). Monday was my last day of
| work so this is my first few days of unemployment. I have a bit of
severance
| pay, so it's okay so far.
|
| My proposed rules file on my Wiki page is currently targeted for making
| routable Garmin GPS maps, but I plan to make it generic enough that it
could
| be used for tiling or filtering by tags, and possibly other uses. Ideally
| the same rules file could be used for tiling, filtering and then
generating
| a routable map, by just picking the part that is of interest to the
| particular task.
|
| If OSM had a polygon type, or if every closed way was guaranteed to have a
| "area=yes" tag, then we could deal with tiling in a generic way, but since
| it doesn't (who knows why... I believe all professional GIS systems
do, for
| a good reason)
There are closed ways that are not areas.

And the reason for the area type not there is because it has not been
used when it was there.

up to now it just has been simpler for most cases to just use closed
ways and tag them appropriately.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH9mv8FUbODdpRVDwRApkRAKCN7720/lQPdTwsvlyAAE83nKSQ9QCgy0YS
XgXF1uuu57pV5Ri2o33VLv8=
=DgW6
-----END PGP SIGNATURE-----