Quantcast
Channel: DotSpatial
Viewing all 3973 articles
Browse latest View live
↧

Edited Feature: Legend detailed properties [23701]

January 7, 2014, 8:16 am
$
0
0
You should definitely include the full path to the shape file referenced by this layer in these properties.

Also, consider removing some properties that are not helpful (e.g., DrawnStates array).
↧
Search

Source code checked in, #73619

January 7, 2014, 9:41 am
$
0
0
Legend detailed properties: exclude some not helpful properties, show full path to the shape file. #23701
↧
↧

Commented Feature: Legend detailed properties [23701]

January 7, 2014, 9:42 am
$
0
0
You should definitely include the full path to the shape file referenced by this layer in these properties.

Also, consider removing some properties that are not helpful (e.g., DrawnStates array).
Comments: Associated with changeset 73619.
↧

Edited Feature: Legend detailed properties [23701]

January 7, 2014, 9:45 am
$
0
0
You should definitely include the full path to the shape file referenced by this layer in these properties.

Also, consider removing some properties that are not helpful (e.g., DrawnStates array).
Comments: ** Comment from web user: mogikanin **

Now full path is showing inside category "Feature set". Also some not helpful properties removed from legend detailed properties.

↧

Source code checked in, #73620

January 7, 2014, 12:13 pm
$
0
0
Fixed IndexOutOfRange bug in EnvelopeExt.Intersection. #24604
↧
↧

Commented Unassigned: bug IndexOutOfRange EnvelopeExt.Intersection(this IEnvelope self, ILineSegment segment) [24604]

January 7, 2014, 12:13 pm
$
0
0
DotSpatial.Topology.EnvelopeExt.Intersection(this IEnvelope self, ILineSegment segment)

This method throws an IndexOutOfRangeException because we try to check more than two borderpoints
if we already have two Points we break instead

Before
Line 845

for (int i = 0; i < 4; i++)
{
borderPoints[count] = border[i].Intersection(segment);
if (borderPoints[count] != null)
{
count++;
}
}

After
Line 845

for (int i = 0; i < 4; i++)
{
borderPoints[count] = border[i].Intersection(segment);
if (borderPoints[count] != null)
{
count++;
if (count > 1)
break;
}
}
Comments: Associated with changeset 73620: Fixed IndexOutOfRange bug in EnvelopeExt.Intersection. #24604
↧

Edited Issue: bug IndexOutOfRange EnvelopeExt.Intersection(this IEnvelope self, ILineSegment segment) [24604]

January 7, 2014, 12:15 pm
$
0
0
DotSpatial.Topology.EnvelopeExt.Intersection(this IEnvelope self, ILineSegment segment)

This method throws an IndexOutOfRangeException because we try to check more than two borderpoints
if we already have two Points we break instead

Before
Line 845

for (int i = 0; i < 4; i++)
{
borderPoints[count] = border[i].Intersection(segment);
if (borderPoints[count] != null)
{
count++;
}
}

After
Line 845

for (int i = 0; i < 4; i++)
{
borderPoints[count] = border[i].Intersection(segment);
if (borderPoints[count] != null)
{
count++;
if (count > 1)
break;
}
}
Comments: ** Comment from web user: mogikanin **

Thank you for posting this bug. Now it's fixed.

↧

Commented Unassigned: Multipolygon intersection problem [24400]

January 7, 2014, 12:58 pm
$
0
0
I found a bug in ClipPolygonWithLine.ClipPolygonFeatureSetWithPolygon.
When multipolygon are input to the above sub it leads to no result, although debugging the code it seems it finds the right geometry of intersection.

However the problem is evidenced in the function below

```
public static IFeature Intersection(this IFeature self, IFeature other, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
IFeature f = Intersection(self, other);
if (f != null)
{
UpdateFields(self, other, f, destinationFeatureSet, joinType);
}
return f;
}

```

although intersection works, self and other featuretype and shapetype are polygon, the resulting Ifeature f has no specified featuretype, and going inside UpdateFields, I find the code below

```
private static void UpdateFields(IFeature self, IFeature other, IFeature result, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
if (destinationFeatureSet.FeatureType != result.FeatureType) return;

...
```

which avoid the code to proceed because result.FeatureType turns out to be unspecified.

I don't know how to deal with such a problem, it is above my programming skills.

Oscar
Comments: ** Comment from web user: mogikanin **

Oscar, so the issue can be closed?

↧
Search

Commented Issue: ManhattanShapes error [24146]

January 7, 2014, 1:00 pm
$
0
0
I am experiencing a little problem in converting an integer raster to polygon shapefile using manhattanshapes.

here is the code

Dim a As New DotSpatial.Plugins.Taudem.Port.ManhattanShapes(fname)

Dim g As New FeatureSet(FeatureType.Polygon)
g.Filename = TextBox1.Text

g = a.GridToShapeManhattan()

the instructions above works fine, the problem I am encountering is that the create shapefile often has errors such as the one in the attached capture.

Basically gridToShapeManhattan is supposed to create shapefiles with only vertical and horizontal borders, while sometimes I find such errors.
Comments: ** Comment from web user: mogikanin **

Oscar, can we close this issue?

↧
↧

Source code checked in, #73621

January 7, 2014, 1:19 pm
↧

Commented Issue: ManhattanShapes error [24146]

January 7, 2014, 2:22 pm
$
0
0
I am experiencing a little problem in converting an integer raster to polygon shapefile using manhattanshapes.

here is the code

Dim a As New DotSpatial.Plugins.Taudem.Port.ManhattanShapes(fname)

Dim g As New FeatureSet(FeatureType.Polygon)
g.Filename = TextBox1.Text

g = a.GridToShapeManhattan()

the instructions above works fine, the problem I am encountering is that the create shapefile often has errors such as the one in the attached capture.

Basically gridToShapeManhattan is supposed to create shapefiles with only vertical and horizontal borders, while sometimes I find such errors.
Comments: ** Comment from web user: Oscarafone77 **

Well the problem is still there. Unless there an alternative to manhattanshapes to convert a raster to polygon i would keep it open. What do you think?

Oscar

↧

Commented Unassigned: Multipolygon intersection problem [24400]

January 7, 2014, 2:25 pm
$
0
0
I found a bug in ClipPolygonWithLine.ClipPolygonFeatureSetWithPolygon.
When multipolygon are input to the above sub it leads to no result, although debugging the code it seems it finds the right geometry of intersection.

However the problem is evidenced in the function below

```
public static IFeature Intersection(this IFeature self, IFeature other, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
IFeature f = Intersection(self, other);
if (f != null)
{
UpdateFields(self, other, f, destinationFeatureSet, joinType);
}
return f;
}

```

although intersection works, self and other featuretype and shapetype are polygon, the resulting Ifeature f has no specified featuretype, and going inside UpdateFields, I find the code below

```
private static void UpdateFields(IFeature self, IFeature other, IFeature result, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
if (destinationFeatureSet.FeatureType != result.FeatureType) return;

...
```

which avoid the code to proceed because result.FeatureType turns out to be unspecified.

I don't know how to deal with such a problem, it is above my programming skills.

Oscar
Comments: ** Comment from web user: Oscarafone77 **

Yes this issue was my fault. Sorry about that.

Thank you

Oscar

↧

Commented Issue: ManhattanShapes error [24146]

January 7, 2014, 2:38 pm
$
0
0
I am experiencing a little problem in converting an integer raster to polygon shapefile using manhattanshapes.

here is the code

Dim a As New DotSpatial.Plugins.Taudem.Port.ManhattanShapes(fname)

Dim g As New FeatureSet(FeatureType.Polygon)
g.Filename = TextBox1.Text

g = a.GridToShapeManhattan()

the instructions above works fine, the problem I am encountering is that the create shapefile often has errors such as the one in the attached capture.

Basically gridToShapeManhattan is supposed to create shapefiles with only vertical and horizontal borders, while sometimes I find such errors.
Comments: ** Comment from web user: mogikanin **

Did you tried DotSpatial.Tools.RasterToPolygon?

↧
↧

Closed Unassigned: Multipolygon intersection problem [24400]

January 7, 2014, 2:39 pm
$
0
0
I found a bug in ClipPolygonWithLine.ClipPolygonFeatureSetWithPolygon.
When multipolygon are input to the above sub it leads to no result, although debugging the code it seems it finds the right geometry of intersection.

However the problem is evidenced in the function below

```
public static IFeature Intersection(this IFeature self, IFeature other, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
IFeature f = Intersection(self, other);
if (f != null)
{
UpdateFields(self, other, f, destinationFeatureSet, joinType);
}
return f;
}

```

although intersection works, self and other featuretype and shapetype are polygon, the resulting Ifeature f has no specified featuretype, and going inside UpdateFields, I find the code below

```
private static void UpdateFields(IFeature self, IFeature other, IFeature result, IFeatureSet destinationFeatureSet, FieldJoinType joinType)
{
if (destinationFeatureSet.FeatureType != result.FeatureType) return;

...
```

which avoid the code to proceed because result.FeatureType turns out to be unspecified.

I don't know how to deal with such a problem, it is above my programming skills.

Oscar
Comments: Not an issue
↧

Closed Feature: Show dataset file location in layer properties window [23126]

January 7, 2014, 2:50 pm
$
0
0
Somewhere in the layer detailed properties, I would like to see the file path (or web url address or database name) of the dataset that is the source dataset of the map layer)
Comments: Duplicate of https://dotspatial.codeplex.com/workitem/23701
↧
Search

Commented Issue: ShapeFiles with PointZ are assumed to have four values, when it can be only three [23224]

January 8, 2014, 12:34 am
$
0
0
DotSpatial assumes that ShapeFiles with PointZ have four values (x, y, z and m). Our ShapeFiles that are PointZ only have three values (x, y and z).
 
This makes DotSpatial crash since it's trying to read too much data from the ShapeFile.
Comments: ** Comment from web user: VitecMarkus **

I have a duplicate issue here with more comments and an attached file already: http://dotspatial.codeplex.com/workitem/23123

↧

Commented Issue: ShapeFiles with PointZ are assumed to have four values, when it can be only three [23224]

January 8, 2014, 1:06 am
$
0
0
DotSpatial assumes that ShapeFiles with PointZ have four values (x, y, z and m). Our ShapeFiles that are PointZ only have three values (x, y and z).
 
This makes DotSpatial crash since it's trying to read too much data from the ShapeFile.
Comments: ** Comment from web user: mogikanin **

Ok, then i'm closing this issue.

↧
↧

Closed Issue: ShapeFiles with PointZ are assumed to have four values, when it can be only three [23224]

January 8, 2014, 1:06 am
$
0
0
DotSpatial assumes that ShapeFiles with PointZ have four values (x, y, z and m). Our ShapeFiles that are PointZ only have three values (x, y and z).
 
This makes DotSpatial crash since it's trying to read too much data from the ShapeFile.
Comments: Duplicate of https://dotspatial.codeplex.com/workitem/23123
↧

Commented Issue: ManhattanShapes error [24146]

January 8, 2014, 3:58 am
$
0
0
I am experiencing a little problem in converting an integer raster to polygon shapefile using manhattanshapes.

here is the code

Dim a As New DotSpatial.Plugins.Taudem.Port.ManhattanShapes(fname)

Dim g As New FeatureSet(FeatureType.Polygon)
g.Filename = TextBox1.Text

g = a.GridToShapeManhattan()

the instructions above works fine, the problem I am encountering is that the create shapefile often has errors such as the one in the attached capture.

Basically gridToShapeManhattan is supposed to create shapefiles with only vertical and horizontal borders, while sometimes I find such errors.
Comments: ** Comment from web user: Oscarafone77 **

I tried following Dan answers to this old post of mine

https://dotspatial.codeplex.com/discussions/439483

i could not make it work since I do not really know how to create or deal with a cancelprogresshandler

Oscar

↧

Commented Issue: ManhattanShapes error [24146]

January 8, 2014, 4:37 am
$
0
0
I am experiencing a little problem in converting an integer raster to polygon shapefile using manhattanshapes.

here is the code

Dim a As New DotSpatial.Plugins.Taudem.Port.ManhattanShapes(fname)

Dim g As New FeatureSet(FeatureType.Polygon)
g.Filename = TextBox1.Text

g = a.GridToShapeManhattan()

the instructions above works fine, the problem I am encountering is that the create shapefile often has errors such as the one in the attached capture.

Basically gridToShapeManhattan is supposed to create shapefiles with only vertical and horizontal borders, while sometimes I find such errors.
Comments: ** Comment from web user: mogikanin **

if you do not want to use cancelprogresshandler create and pass instance of this class

```
class MockProgressHandler : ICancelProgressHandler
{
public void Progress(string key, int percent, string message)
{
//nothing
}

public bool Cancel { get { return false; } }
}

```
But i'll also check why it not working with null.

↧
Viewing all 3973 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>