Yeah, I guess it makes sense to deprecate it..
John Cartwright wrote:
Thanks, that'll be great. Can you also remove or deprecate the toText
method at that time?
--john
Martin Davis wrote:
Cool - I'll add this for ver 1.11
John Cartwright wrote:
I like that suggestion even better!
--john
Martin Davis wrote:
Good point, Ken.
Maybe even better would be toWKT() and toWKB() methods - that would
be very explicit about what is being returned.
Ken Tanaka wrote:
I think that it's reasonable that the methods toString and toText
are the same, but the toString output shouldn't be relied on for
WKT representations--typically toString contains whatever the
author of the API feels is useful to know about the object and its
format may change in future implementations unless the JavaDoc
defines and commits to maintain a given format into the future.
The toText is expected conform to the WKT format
-Ken
John Cartwright wrote:
Hello All,
I'm just looking for a little clarification on converting a
Geometry to it's WKT representation. It looks to me like
Geometry#toString and Geometry#toText produce the same result. Is
there any reason to use one over the other? Given both these
return the WKT, why would one choose to use the WKTWriter#write
method?
Thanks!
--john
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
jts-devel mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jts-devel
