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 D. Rosenberg, Ph.D. 600 Lanidex Plaza
Cisco Fellow Parsippany, NJ 07054-2711
[email protected] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
Ecrit mailing list