RE: [Ecrit] comments on LoST

["Brian Rosen" <br at brianrosen.net>]

You have the polygons for "city" "county" "state" etc.  You intersect them
with the service boundary polygon.  You take the smallest, totally enclosed
area.

Brian

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen at cisco.com]
> Sent: Wednesday, February 14, 2007 11:16 AM
> To: Brian Rosen
> Cc: 'ECRIT'
> Subject: Re: [Ecrit] comments on LoST
> 
> 
> 
> Brian Rosen wrote:
> 
> > Well, there are two ways to do this.  One is to keep the data for both,
> a
> > real polygon for the geo, and appropriate values in fields of the civic.
> >
> > The other way is to use geocoding to convert civic to geo and use the
> > polygons in all cases.  Conversion in this case is acceptable, both
> because
> > you don't forward the converted value, and because the database used can
> be
> > precisely the database used for other routing purposes.
> 
> So here is my concern. The client sends its query using a <location>
> object in civic form. The server has all its information in geodesic.
> So, it converts the civic <location> to geodesic and does its work. But
> now, it has to return the boundary information in civic format. But, in
> this case, it doesn't have it - you only have it in polygon format.
> 
> So how does this work.
> 
> -Jonathan R.
> 
> 
> 
> --
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ 07054-2711
> Cisco Systems
> jdrosen at cisco.com                              FAX:   (973) 952-5050
> http://www.jdrosen.net                         PHONE: (973) 952-5000
> http://www.cisco.com


_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit