Udo Giacomozzi wrote:
> Of course I realize that now the OSM data format can't be extended to
> curves without breaking existing renderes and tools...
You can extend it to NURBS without breaking tools ;) Think about the
control point approximation ;) So every embedded device that isn't fast
or d
Hello Cartinus,
Sunday, March 15, 2009, 2:57:30 AM, you wrote:
C> Because to do curves _right_ you need more data then you have now. First you
C> need to know if a line has to curve at a point at all. (I wouldn't want to
C> have rounded corners on every square.) If the line curves, then you need t
On Saturday 14 March 2009 15:21:19 Udo Giacomozzi wrote:
> Is there a good reason why all map databases seem to be fixed on
> straight lines and do not support some kind of bezier curves?
Because to do curves _right_ you need more data then you have now. First you
need to know if a line has to cu
On Sat, Mar 14, 2009 at 09:47, Frederik Ramm wrote:
> 5325 E. Pacific Coast Hwy
> Long Beach, CA 90804
Short parsing of what it is:
Building number: 5325
Street name: E Pacific Coast Hwy
City: Long Beach
State: CA
Postcode: 90804
You are correct that the "E" references east, but it's not the eas
Karl covers it pretty well. When the "E.", "W.", "N." or "S." appears before
the street, it can be considered part of the street name and usually identifies
part of the street on one side of a boundary. For example, all street numbers
in Chicago start with 0 at State and Madison. If you go e
On Sat, Mar 14, 2009 at 7:47 AM, Frederik Ramm wrote:
> Hi,
>
> Stefan Breunig wrote:
> > True about \d. But this regex doesn't match any housenumber in "3rd
> > street". It matches
> > [number][maybe a single letter][word boundary].
>
> Could someone from the US shed some light on this type of a
Udo Giacomozzi wrote:
> Saturday, March 14, 2009, 4:44:10 PM, you wrote:
> SdK> Basically my storage model thinks everything in simple linear lines.
> SdK> Adding weight will give you NURBS ;) Infinite weight gives you an
> SdK> absolute point. I guess you get the idea now.
>
> Not sure I really
Hello Stefan,
Saturday, March 14, 2009, 4:44:10 PM, you wrote:
SdK> Basically my storage model thinks everything in simple linear lines.
SdK> Adding weight will give you NURBS ;) Infinite weight gives you an
SdK> absolute point. I guess you get the idea now.
Not sure I really understand the conc
+1 for that!!!
I could easily create and store all the canvec2osm created files on my
GoogleApps website www.acrosscanadatrails.com
(as well as the geobase2osm NRN data, which is already being archived on
http://www.mediafire.com)
I would of-course have it all in a single layer, (but better to ha
Udo Giacomozzi wrote:
> Is there a good reason why all map databases seem to be fixed on
> straight lines and do not support some kind of bezier curves? After
> all, streets most of the time have curves and only at junctions or in
> other rare situations have corners.
>
> Using bezier curves would
On 3/14/09, Frederik Ramm wrote:
> Hi,
>
> Stefan Breunig wrote:
>> True about \d. But this regex doesn't match any housenumber in "3rd
>> street". It matches
>> [number][maybe a single letter][word boundary].
>
> Could someone from the US shed some light on this type of address:
>
> 5325 E. Pacif
forwarded to list
-- Forwarded message --
From: Eddy Petrișor
Date: Sat, 14 Mar 2009 17:26:18 +0200
Subject: Re: [OSM-dev] extracting house-number from string
To: Marcus Wolschon
Gnu locales define the format of addresses in each of the defined locales.
I'd suggest you look int
Hi,
Stefan Breunig wrote:
> True about \d. But this regex doesn't match any housenumber in "3rd
> street". It matches
> [number][maybe a single letter][word boundary].
Could someone from the US shed some light on this type of address:
5325 E. Pacific Coast Hwy
Long Beach, CA 90804
The "E." is,
Hello Marcus,
Friday, March 13, 2009, 4:28:24 PM, you wrote:
MW> does anyone know a good algorithm to extract
MW> the house-number from a string containing
MW> street-name and house-number?
Why not treat any word that begins with a digit as house number?
Note that street names sometimes contain
Is there a good reason why all map databases seem to be fixed on
straight lines and do not support some kind of bezier curves? After
all, streets most of the time have curves and only at junctions or in
other rare situations have corners.
Using bezier curves would at the same time lead to more smo
On Fri, Mar 13, 2009 at 02:21:18AM +0100, Stefan de Konink wrote:
> Now it is nice you put 32GB (extra expensive) memory in there, but most
> likely your hot performance would be far better with more (cheap) memory
> than more disks. At the time I wrote my paper on OSM Dec2008, there was
The EC
Sounds cool !! so point 3 deleted,looking forward to work on point 1 or 2 (
in order of preference ) ,I really want to work on Accessibility issue and
make OSM one-stop choice for people who are visually impaired. Lots of big
companies are trying hard on it,as part of my informal proposal something
On 13/03/2009, rajan vaish wrote:
> Hi,
> I am Rajan,a CS major from India.I interned online for One Laptop per Child
> creating a Geography teaching tool using GeoRSS,MapServer and OpenLayers in
> summer'08. I am really looking forward to participate and work for OSM this
> year and there are few
18 matches
Mail list logo
