# Invalid WKT

**URL:** <https://community.thinkgeo.com/t/invalid-wkt/3270>\
**Category:** WPF\
**Created:** [August 10, 2012, 10:59am UTC](https://community.thinkgeo.com/t/invalid-wkt/3270 "2012-08-10T10:59:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://community.thinkgeo.com/u/Ryan1)\
**Post date:** [August 10, 2012, 10:59am UTC](https://community.thinkgeo.com/t/invalid-wkt/3270/1 "2012-08-10T10:59:16Z")

</div>

We&nbsp;are&nbsp;running&nbsp;into&nbsp;an&nbsp;issue&nbsp;where&nbsp;some&nbsp;of&nbsp;the&nbsp;WKT&nbsp;values&nbsp;we’ve&nbsp;previously&nbsp;generated&nbsp;using&nbsp;MapSuite&nbsp;and&nbsp;stored&nbsp;in&nbsp;the&nbsp;database&nbsp;are&nbsp;exploding&nbsp;when&nbsp;we&nbsp;try&nbsp;to&nbsp;create&nbsp;a&nbsp;BaseShape&nbsp;from&nbsp;them.&nbsp;&nbsp;We&nbsp;get&nbsp;the&nbsp;following&nbsp;error:  
  
The&nbsp;format&nbsp;of&nbsp;the&nbsp;well&nbsp;known&nbsp;text&nbsp;is&nbsp;incorrect.  
Parameter&nbsp;name:&nbsp;wellKnownText  
  
An&nbsp;example&nbsp;of&nbsp;WKT&nbsp;that&nbsp;gets&nbsp;this&nbsp;is:  
  
LINESTRING(68.9062449459175&nbsp;33.9999938472282,68.9062446106414&nbsp;34.0000059171687,68.9062446106414&nbsp;34.0000059171687)  
  
We’ve&nbsp;upgraded&nbsp;to&nbsp;the&nbsp;SQLTypes&nbsp;(maybe&nbsp;that&nbsp;has&nbsp;something&nbsp;to&nbsp;do&nbsp;with&nbsp;it)&nbsp;but&nbsp;haven’t&nbsp;seen&nbsp;this&nbsp;issue&nbsp;before&nbsp;today.  
  
  
We&nbsp;are&nbsp;using&nbsp;WPF&nbsp;version&nbsp;6.0.74.0  
  
  
Any&nbsp;insight&nbsp;would&nbsp;be&nbsp;appreciated.&nbsp;&nbsp;Thank&nbsp;you.  
  
.Ryan.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://community.thinkgeo.com/u/Ryan1)\
**Post date:** [August 10, 2012, 4:27pm UTC](https://community.thinkgeo.com/t/invalid-wkt/3270/2 "2012-08-10T16:27:12Z")

</div>

I’ve&nbsp;reverted&nbsp;back&nbsp;to&nbsp;6.0.4.0&nbsp;and&nbsp;everything&nbsp;loads&nbsp;fine&nbsp;coming&nbsp;out&nbsp;of&nbsp;the&nbsp;same&nbsp;database.

---

<div class="post-metadata">

**Author:** ![David](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/aeb1de/32.png) [@David](https://community.thinkgeo.com/u/David)\
**Post date:** [August 10, 2012, 7:29pm UTC](https://community.thinkgeo.com/t/invalid-wkt/3270/3 "2012-08-10T19:29:56Z")

</div>

Ryan,&nbsp;  
&nbsp;&nbsp;  
&nbsp;&nbsp;&nbsp;The&nbsp;SQLTypes&nbsp;are&nbsp;much&nbsp;more&nbsp;strict&nbsp;with&nbsp;the&nbsp;WKT&nbsp;and&nbsp;WKB&nbsp;they&nbsp;allow&nbsp;however&nbsp;I’m&nbsp;sure&nbsp;there&nbsp;is&nbsp;something&nbsp;we&nbsp;can&nbsp;do&nbsp;to&nbsp;fix&nbsp;this.&nbsp;&nbsp;What&nbsp;we&nbsp;need&nbsp;to&nbsp;do&nbsp;is&nbsp;add&nbsp;some&nbsp;exception&nbsp;checking&nbsp;so&nbsp;that&nbsp;if&nbsp;it&nbsp;is&nbsp;invalid&nbsp;that&nbsp;we&nbsp;call&nbsp;the&nbsp;new&nbsp;MakeValid&nbsp;on&nbsp;it&nbsp;and&nbsp;in&nbsp;99%&nbsp;of&nbsp;the&nbsp;cases&nbsp;it&nbsp;repairs&nbsp;it&nbsp;and&nbsp;makes&nbsp;it&nbsp;valid.&nbsp;&nbsp;These&nbsp;things&nbsp;have&nbsp;been&nbsp;slowly&nbsp;surfacing&nbsp;so&nbsp;we&nbsp;need&nbsp;to&nbsp;take&nbsp;care&nbsp;of&nbsp;that.&nbsp;&nbsp;Thanks&nbsp;for&nbsp;pointing&nbsp;that&nbsp;out&nbsp;and&nbsp;we&nbsp;plan&nbsp;to&nbsp;get&nbsp;a&nbsp;fix&nbsp;in&nbsp;early&nbsp;next&nbsp;week.&nbsp;  
&nbsp;&nbsp;  
&nbsp;David

---

<div class="post-metadata">

**Author:** ![Ryan1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://community.thinkgeo.com/u/Ryan1)\
**Post date:** [August 13, 2012, 11:06am UTC](https://community.thinkgeo.com/t/invalid-wkt/3270/4 "2012-08-13T11:06:35Z")

</div>

Thanks&nbsp;David,&nbsp;could&nbsp;you&nbsp;let&nbsp;me&nbsp;know&nbsp;when&nbsp;this&nbsp;is&nbsp;up&nbsp;for&nbsp;testing&nbsp;so&nbsp;I&nbsp;can&nbsp;verify&nbsp;it&nbsp;for&nbsp;you?&nbsp;  
&nbsp;&nbsp;  
&nbsp;.Ryan.

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [September 4, 2012, 4:31am UTC](https://community.thinkgeo.com/t/invalid-wkt/3270/5 "2012-09-04T04:31:05Z")

</div>

&nbsp;Hi&nbsp;Ryan,

&nbsp;  
Sorry&nbsp;for&nbsp;the&nbsp;long&nbsp;time&nbsp;delay,&nbsp;but&nbsp;we&nbsp;are&nbsp;still&nbsp;working&nbsp;on&nbsp;it,&nbsp;we&nbsp;cannot&nbsp;guarantee&nbsp;we'll&nbsp;cover&nbsp;all&nbsp;the&nbsp;scenarios&nbsp;because&nbsp;of&nbsp;the&nbsp;performance,&nbsp;so&nbsp;we&nbsp;are&nbsp;looking&nbsp;for&nbsp;a&nbsp;best&nbsp;solution&nbsp;to&nbsp;balance&nbsp;the&nbsp;performance&nbsp;and&nbsp;the&nbsp;validation.&nbsp;Can&nbsp;you&nbsp;use&nbsp;the&nbsp;following&nbsp;code&nbsp;as&nbsp;a&nbsp;workaround&nbsp;first?  
&nbsp;  
`            BaseShape.GeometryLibrary = GeometryLibrary.Managed;            Feature feature = new Feature("LINESTRING(68.9062449459175 33.9999938472282,68.9062446106414 34.0000059171687,68.9062446106414 34.0000059171687)");            BaseShape.GeometryLibrary = GeometryLibrary.Unmanaged;            feature = feature.MakeValid();`  
&nbsp;  
Or&nbsp;you&nbsp;can&nbsp;use&nbsp;the&nbsp;BaseShape.GeometryLibrary&nbsp;=&nbsp;GeometryLibrary.Managed.&nbsp;all&nbsp;the&nbsp;time&nbsp;to&nbsp;use&nbsp;the&nbsp;old&nbsp;NTS&nbsp;topology&nbsp;rules.Once&nbsp;we&nbsp;have&nbsp;a&nbsp;result,&nbsp;we'll&nbsp;let&nbsp;you&nbsp;know.  
&nbsp;  
Thanks,  
&nbsp;  
Edgar