DotSpatial Issue Tracker Rss Feed

Closed Issue: Unicode Character Support in Attribute Data [22524]

arnolde — Thu, 16 May 2013 12:11:24 GMT

There is a problem in showing unicode characters, UTF-8, Persian and other languages character sets when loading .dbf file attribute data fields. These characters are shown by "?" character.
Please provide help on this issue.

Closed Issue: Unrestricted Zooming Out [23748]

ericch — Thu, 16 May 2013 12:11:21 GMT

Zooming in or out on any given map does not have any constraints. Zooming out specifically should be limited to the point where the user does not go beyond the map image itself into white space.

Closed Issue: TableEditor Plugin [23788]

danames — Thu, 16 May 2013 12:11:21 GMT

The TableEditor __falsely__ assumes every layer has at least two ContextMenuItems, as it always wants to place its own entry at index 2.

IMHO, for basemap/background image layers an attribute table doesn't make sense so I would not want an entry for editing the attribute table at all.

Closed Issue: Bug in SerializationMap [23793]

danames — Thu, 16 May 2013 12:11:21 GMT

The SerializationMap prevents setting values for fields that are marked as readonly, even when they have the SerializeAttribute with a ConstructorArgumentIndex >= 0.

Closed Issue: Unnecessary creation of PyramidImage in GdalImageProvider [23813]

shieldst — Thu, 16 May 2013 12:11:20 GMT

If a raster is loaded that has a Width of Height > 8000, GdalImageProvider always creates a pyramid image even if the image itself contains overviews. This is slow and unnecessary.

The attached patch fixes this.

Closed Issue: Ribbon download not working [23887]

aparks — Thu, 16 May 2013 12:11:20 GMT

When setting up a new user to use a DS app with the ribbon control the download dies with the attached error screen.

Aaron Parks

Closed Issue: Removing layer with map.layers.remove destroys underlying FS [23896]

danames — Thu, 16 May 2013 12:11:20 GMT

When using map.layers.remove the underlying featureset is no longer available.

This is problematic when using IMPLs with another control to add/remove layers.

Created Issue: Labels.LineOrientation [24232]

KwameAnsu — Sun, 05 May 2013 10:54:55 GMT

In mapWindow 4.x one can easily place labels parallel to line features by setting the Labels.LineOrientation property for a given shape file.

I expected that this method should be easy to port to dotspatial since mapwindow 4.x was developed in either c# or vb.net.

If it is a matter of uniformity, I think it should be possible to derive from the labels and add this feature specifically for line features.

As you can see from the threads, a lot of people are seeking to use this feature, which made labelline such a breeze in mapwindow 4.x.

I know the answer would be to use mapwindow 4.x if we want to access this feature. However, would it not be more practical if this feature is available in the fully-managed dotspatial, which, I have to admit, has a lot of great features.

Thanks for considering my request.

Commented Issue: Problem with LAEA projection [23987]

Yvan_B — Tue, 30 Apr 2013 18:33:00 GMT

Hello,

I'm new to Dot Spatial and really enthusiast to play with this great tool.
I am trying to convert lat/lng values to ETRS LAEA Europe coordinate system (EPSG:3035) but I always get NAN values (Not A Numeric). I think that this closed issue is probably the same: http://dotspatial.codeplex.com/workitem/22212

here is my code (VB.NET) :

```
Dim xy(1) As Double
xy(0) = 5
xy(1) = 50
Dim z(0) As Double
z(0) = 1
Dim pStart As ProjectionInfo = KnownCoordinateSystems.Geographic.World.WGS1984
Dim pEnd As ProjectionInfo = ProjectionInfo.FromProj4String("+proj=laea +lat_0=52 +lon_0=10 +x_0=4321000 +y_0=3210000 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs")
Try
Reproject.ReprojectPoints(xy, z, pStart, pEnd, 0, 1)
Catch ex As Exception

End Try
MsgBox("The points have been reporjected." & vbCrLf & xy(0) & "," & xy(1))

```

The code works well with other coordinate systems. It doesn't work with KnownCoordinateSystems.Projected.Europe.ETRS1989LAEA nor if I use the definition found in AuthorityCodeToProj4.txt (line 1006)
The Proj4 definition I use in the code is correct (verified in the epsg file of PROJ4).

Any idea?

Yvan
Comments: ** Comment from web user: Yvan_B **

Thanks for the last suggestion. I came already to the same conclusion about .Net Wrapper (and it works)

Yvan

Commented Issue: Legend to image file [24221]

VictorVelarde — Tue, 30 Apr 2013 11:37:29 GMT

Hi everybody,

I have a MapRasterLayer and I would like to render its associated simbology to disk as a PNG file, getting a simple image from its 'legend'. I would like to know the minimum set of classes that I have to instantiate and combine in order to get it.

I'm working in a simple class library, not a windows form app.

Any help would be much appreciated,
Comments: ** Comment from web user: VictorVelarde **

I'm sorry but this is not an issue.
I wanted to publish it as a question in 'discussions'

Created Issue: Legend to image file [24221]

VictorVelarde — Tue, 30 Apr 2013 11:33:04 GMT

Created Issue: Can't find MapControl in Visual Studio 2012 [24217]

realxu — Mon, 29 Apr 2013 07:09:35 GMT

I create a Winform project in Visual Stduio 2012 with .Net framework 4. Then install DotSpatial.Control and its dependency by NuGet.
Every thing is OK. But when I choose DotSpatial.Control to add toolbox items, I found there's no MapControl!
![Image](http://pic.yupoo.com/sinaweibo1283765694_v/CP45QXU6/PaLCa.png)

Can you tell me how to resolve? Thanks!

Commented Issue: Newbie question: Layer Extents [24210]

epsoft1969 — Sun, 28 Apr 2013 08:30:10 GMT

Hi, I'm new to DotSpatial but I've managed to create a map with a point layer and line layer. This all works fine but I'm having trouble getting the map view to zoom to the extents of the visible layers. I've tried setting map.viewextents = mylayer.extent (or mylayer.dataset.extent) but neither appears to work. The view either doesn't change or zooms out way beyond the extent of the data.

I feel I'm missing something fundamental.

Any suggestions?

Thanks

Rob :)
Comments: ** Comment from web user: epsoft1969 **

I think I solved this one, although I'm not entirely sure how!

Commented Issue: Problem with LAEA projection [23987]

tmanthey — Sat, 27 Apr 2013 12:41:55 GMT

Working workaround is to use the .Net Wrapper for the native dll. Some good instructions are [here](http://www.spatialmarkets.com/blog/2012/8/2/using-proj4-in-net.html)

Commented Issue: Problem with LAEA projection [23987]

tmanthey — Sat, 27 Apr 2013 12:26:51 GMT

I can confirm this issue

Commented Issue: Newbie question: Layer Extents [24210]

epsoft1969 — Fri, 26 Apr 2013 02:56:51 GMT

Sorry, newbie mistake. I probably should have posted this in discussions rather than issue tracker!

Commented Issue: Newbie question #2: IndexOutofRangeException [24211]

epsoft1969 — Fri, 26 Apr 2013 02:56:36 GMT

Hi again, another newbie question. I'm getting an exception when trying to clear a featureset (in readyness to re-populate it).

IndexOutOfRangeException was unhandled
The given DataRow is not in the current DataRowCollection

I read something somewhere about the underlying indexes getting out of sync with the data but not sure if that's related to this at all.

Any help would be greatly appretiated. Sorry if this is obvious but my usual trick of Googling the problem is not yielding many results.

Have I missed something fundamental about how to create and re-create layers/features etc?

Thanks
Comments: ** Comment from web user: epsoft1969 **

Sorry, newbie mistake. I probably should have posted this in discussions rather than issue tracker!

Created Issue: Newbie question #2: IndexOutofRangeException [24211]

epsoft1969 — Fri, 26 Apr 2013 02:49:46 GMT

Created Issue: Newbie question: Layer Extents [24210]

epsoft1969 — Fri, 26 Apr 2013 02:38:25 GMT

Closed Issue: Polygon.Buffer sometimes returns empty geometry [24205]

kellison — Wed, 24 Apr 2013 19:03:34 GMT

Buffering the polygon shown below by a value of 0.01 returns an empty geometry. The actual defect is in the
DotSpatial.Topology.PrecisionModel.MakePrecise(double val) method when _modelType is PrecisionModelType.Fixed. The result is being scaled BEFORE being rounded. It should be scaled after rounding.

+ badpoly {POLYGON ((119.9999998058790000 -0.0000000000640483, 119.0000000000000000 -0.0000001608012496, 119.0000000000000000 0.9999999999999720, 119.9999998705860000 0.9999999999999720, 119.9999998058790000 -0.0000000000640483))} DotSpatial.Topology.Polygon
Comments: Resolved with changeset 71942.