Review of Summary Outputs - suggestions for implementation

[andrewhunter2066]

• [x] 1. Output IDs for all elements
• [x] 2. In the Points section, the first column always appears to be None. What is it meant to be output? Should it be dropped?
• [x] 3. What is the difference between Monuments and Points? In the JSON data they are not separate things.
• [x] 4. Column 2 in the observedVectors section is also None. What is it meant to be output? Should it be dropped?
• [x] 5. Columns, 4, 6 and 7 in the Parcels section is None. What is it meant to be output? Should they be dropped?
• [x] 6. The datum for the NZ 3D points example is specified in the JSON as "compoundCRS": "epsg:9528", but the summary says the projection is wgs84. Issue is probably the element name. For 2D data it is "horizontalCRS". for 3D it is either "horizontalCRS" plus "verticalDatum" OR "compoundCRS". PanCadastre needs to test for this pattern. The Summary should also include the "verticalDatum" when provided, or make it clear that a compund datum is being used.
• [x] 7. Arc Observations are not displaying correctly. The first two examples should just be arcs, the third should be an arc and a chord. Arcs should display radius and arc length.
• [x] 8. Observation details (bearing/distance/ID) are not displayed in the GeoJSON.
• [x] 9. Lot details (ID, label, area) are not displayed in the GeoJSON.
• [x] 10. For the 3D Summary, only X & Y are reported. Should include Z as well.
• [x] 11. When a GeodeticReferenceMark is included, report the "geodeticid"
• [x] 12. Subtended angle information should be displayed when they exist.
• [x] 13. Subtended angle information does not appear in the summary.
• [x] 14. Arc summary should include radius and arc length.
• [x] 15. Circle geometry needs to be displayed.
• [x] 16. Report the supporting documents that have been included.
• [ ] 17. Polygon for WA Topographic String example is not plotting correctly. The natural feature is not currently the edge of the polygon. It is right-lined from the start of the natural feature to the end.
• [x] 18. Spline geometry needs to be displayed.
• [x] 19. Report the Annotation that have been included.

[alcinnz]

In the "Points" section, the first column was meant to be the name. I've now removed this section for duplicating the monuments section, after filling in IDs for blank values. Points are locations on earth whether they're monumented or not, the distinction came from LandXML & I find it convenient to split the datamodel up into more objects whenever there's a disagreement between schemas. Easier to parse that way without complicating serialization, but I don't need to make this visible in the report!

The second column of Observations should be the date. Column 4 of parcels should be the centerpoint, 6 the classification, & 7 should be a description. I'm ensuring the latter doesn't display if absent.

You can get spline geometry in the GeoJSON by passing the --interpolate flag. Should I tweak the GitHub action to include this?

I'll run some tests to figure out how to resolve more of these issues! Which may involve improving the intermediary datamodel.

[andrewhunter2066]

I'm not sure we should be following LandXML structures - my preference would be to use CSDM structures/names, so Survey Point, Survey Mark (Survey Points that have been monumented) and Occupation Marks. Or they could be organized by mark type: Boundary Mark; Cadastral Mark; Geodetic Reference Mark; and Occupation Mark.

Bit confused re ...7 should be a description.... There is no parcel description element in the JSON. Do you mean the name/label?

Why is there a parcel center point? There isn't one specified in the JSON? That is a LandXML requirement, not a CSDM one as far as I'm aware.

If the --interpolate flag fixes the polygon construction issue where spline boundaries are included, then yes.

[alcinnz]

I'm moving towards CSDM structures where I find that makes a difference. However jumping in head-first on such a refactor would involve rewriting the whole thing which I am not keen on, and might make future uses for PanCadastre harder to implement.

I think there was a "comment" property I can parse as a description? I haven't yet, but I've now hidden descriptions where they're missing from the schema or data.

I'll remove the parcel center point from the output.

[alcinnz]

I've now tackled 3D coordinates, with a naming-refactor to address some previous confusions me and Byron had. This might have unearthed some bugs (I need to do more thorough testing), but it should have helped us avoid feature ones.

Also, we need to figure out how to properly handle the 3rd dimension.

[alcinnz]

I think I've worked my way through most of these features, though my testing has been quite light.

For 17: Specifically which file are you talking about?

For 19: Can you point me to where the annotations in the CSDM schema?

I should have this all done tomorrow morning!

[andrewhunter2066]

Re 17, have a look at this

There are two annotation examples at the moment. The WA version is here and the VIC version is here

[alcinnz]

Regarding 17, when you filed this issue it might have had something to do with me not supporting subtended angles yet. Now it appears you're referencing one observation from another, which could prove tricky to handle. Can I rely on the subtended angles being listed last?

So that any observations it references occurs earlier in the file?

[andrewhunter2066]

I'm not sure we can assume subtended angles will be recorded last, at least there is nothing I'm aware of that says they should be. Is it necessary that they must be?

Regarding polygon construction I'm not sure that it matters as subtended angles are not included in the polygon specification, only types of curves are.

[alcinnz]

O.K., so I'll iterate over that list twice to separate out the subtended angles then!

So are the references in a subtended angle always other observations or are can they also be points?

[alcinnz]

I've moved past that subtended angle issue, and now its complaining about the projection the file is in. Pyproj doesn't recognize it!

[andrewhunter2066]

This document covers the specification of Subtended Angles.

Probably need to update your pyproj package to the latest version.

[andrewhunter2066]

Getting the following error on a number of examples when I run the visualisation action:

build/tests/profiles/nz/3d-surveypoints.jsonld
ReferencedCSD.__init__() missing 1 required positional argument: 'time'

[alcinnz]

Fixed the issue with referenced CSDs, very minor!

It seems I somehow read the datamodel as being bearing & rotation as opposed to a bearing-rotation.

[alcinnz]

Updating PyProj did help locally, but I'm not sure if/why that might be a problem in the GitHub Actions. Can you check that?

Regardless I still have some projections to manually throw support in for, & I need to support for Cubic Splines.

[andrewhunter2066]

I believe GitHub uses Leaflet to render GeoJSON, so transformation capabilities may be limited. I assume the PanCadastre runtime doesn't compile each time it runs from a GitHub action so not clear to me why PanCadastre wouldn't work the same way it does locally...

[andrewhunter2066]

Just checking the Pancadastre output, Most files were last commited 4 hours ago.

Looks from the validation reports that things generally passed, but many of the error logs contain the following (this is an aggregation.

Object of type datetime is not JSON serializable
'list' object has no attribute 'get'
Unresolvable link or missing property! 'adminUnit'
'monumentedBy' property is mandatory! 4494876 {'name': {'label': 'Post I LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'I'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 7.6 m North East of Peg 1 LT 584372', 'age': '40+ years'}
Unexpected observedVector topology-type:  ArcByChord
name 'get' is not defined

GeoJSON does not look to be complete/correct.

Seems to be an issue across all 3 jurisdictions.

[alcinnz]

I'll double check, but I've spent yesterday fixing those issues!

[andrewhunter2066]

Still seeing the same issues as yesterday. This is after having run the "Generate visualisations and pass/validate action" in 3d-csdm-profiles. I note that the last github/pancadastre commit was 4 days ago. Is that correct?

For NZ 3D Survey Points the error log says:

build/tests/profiles/nz/3d-surveypoints.jsonld
Object of type datetime is not JSON serializable

The geoJSON is truncated, and there is no summary report.

For NZ Arc Observations the error log says:

build/tests/profiles/nz/arc-observations.jsonld
Unexpected observedVector topology-type:  ArcByChord
name 'get' is not defined

The geoJSON is empty, and there is no summary report.

For NZ example_1_1 the error log says:

build/tests/profiles/nz/example_1_1.jsonld
Unresolvable link or missing property! 'adminUnit'

There is no geojson, nor a summary.

For NZ Observation the error log says:

build/tests/profiles/nz/observations.jsonld
name 'get' is not defined

The geoJSON is empty, and there is no summary report.

For NZ Occupation the error log says:

build/tests/profiles/nz/occupation.jsonld
'monumentedBy' property is mandatory! 4494876 {'name': {'label': 'Post I LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'I'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 7.6 m North East of Peg 1 LT 584372', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494877 {'name': {'label': 'Post II LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'II'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494878 {'name': {'label': 'Post III LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'III'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Gate Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494879 {'name': {'label': 'Post IV LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'IV'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Gate Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494880 {'name': {'label': 'Post V LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'V'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.14m South West of Peg 2 LT 584372', 'age': '60+ years'}
'monumentedBy' property is mandatory! 4494881 {'name': {'label': 'Post VI LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'VI'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.55m South East of Peg 8 LT 584372', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494882 {'name': {'label': 'Post VII LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'VII'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.15 North of Peg 8 SO 503288', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494883 {'name': {'label': 'Post VIII LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'VIII'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post. Peg 4 LT 584372 on North face of post. Post is 13.8m South West of gate post.', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494884 {'name': {'label': 'Post IX LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'IX'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Old Totara Post 1.5m North West of Peg 4 SO 503288', 'age': '60+ years'}
'monumentedBy' property is mandatory! 4494885 {'name': {'label': 'Post X LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanStamp', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkStamp', 'label': 'X'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT 584372', 'note': 'Wooden Post 0.72m South West of Peg 7 LT 584372', 'age': '40+ years'}
'list' object has no attribute 'get'

Note that the validation files all passed for these examples.

VIC and WA outputs are similar.

[alcinnz]

Yeah, I did notice I failed to commit some changes.

I've committed these changes on Friday. Though there's still issues rendering the circular observation.

[andrewhunter2066]

Reviewed output: Summary report for NZ 3D survey points is empty.

NZ Arc Observations arcs are not displaying. There appear to be two chords displayed that are not in the dataset, and the chord that is does not display. Point names are not displaying. Summary report is empty.

NZ Arc Observation error log

build/tests/profiles/nz/arc-observations.jsonld
Unexpected observedVector topology-type:  ArcByChord
'ReferencedCSD' object has no attribute 'link'

NZ example_1_1 has no geojson file. Summary report is empty. Error log contains

build/tests/profiles/nz/example_1_1.jsonld
'list' object has no attribute 'get'

NZ extended example has no geojson file, There is no summary report. The error log contains:

build/tests/profiles/nz/extended_example.jsonld
'list' object has no attribute 'get'

NZ observation example summary file is empty. Error log contains:

build/tests/profiles/nz/observations.jsonld
'ReferencedCSD' object has no attribute 'link'

NZ occupation example error log contains:

build/tests/profiles/nz/occupation.jsonld
'monumentedBy' property is mandatory! 4494876 {'name': {'label': 'Post I LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'I'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 7.6 m North East of Peg 1 LT 584372', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494877 {'name': {'label': 'Post II LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'II'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494878 {'name': {'label': 'Post III LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'III'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Gate Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494879 {'name': {'label': 'Post IV LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'IV'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Gate Post', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494880 {'name': {'label': 'Post V LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'V'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.14m South West of Peg 2 LT 584372', 'age': '60+ years'}
'monumentedBy' property is mandatory! 4494881 {'name': {'label': 'Post VI LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'VI'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.55m South East of Peg 8 LT 584372', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494882 {'name': {'label': 'Post VII LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'VII'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post 0.15 North of Peg 8 SO 503288', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494883 {'name': {'label': 'Post VIII LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'VIII'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Wooden Post. Peg 4 LT 584372 on North face of post. Post is 13.8m South West of gate post.', 'age': '40+ years'}
'monumentedBy' property is mandatory! 4494884 {'name': {'label': 'Post IX LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'IX'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT_584372', 'note': 'Old Totara Post 1.5m North West of Peg 4 SO 503288', 'age': '60+ years'}
'monumentedBy' property is mandatory! 4494885 {'name': {'label': 'Post X LT 584372', 'hasPart': [{'type': 'PlanType', 'label': 'LT'}, {'type': 'PlanNumber', 'label': '584372'}, {'type': 'MarkType', 'label': 'Post'}, {'type': 'MarkIdentifier', 'label': 'X'}]}, 'purpose': 'nz-surveypoint-purpose:occupation', 'fromSurvey': 'LT 584372', 'note': 'Wooden Post 0.72m South West of Peg 7 LT 584372', 'age': '40+ years'}
'list' object has no attribute 'get'

MonumentedBy is not mandatory for Occupation Marks.

There is no summary file nor a geojson file.

The remainder of the examples, including VIC and WA examples seem to have similar errors so I'll let you deal with them.

[alcinnz]

Bizarre, I'm not seeing these issues running it locally...

[andrewhunter2066]

Have you checked what is happening at https://github.com/icsm-au/3d-csdm-profiles/tree/main/build/tests/profiles which is what the Jurisdictions have access to? That is what I have been reviewing.

I first run the Generate visualisations and parse/validate action, pancadastre.yaml

[alcinnz]

Ugh! What's the difference there? It should be cloning a fresh PanCadastre each time. It is running Python3.11 which is same as I'm running locally...

[andrewhunter2066]

I'll leave that to you to sort out :)

[andrewhunter2066]

Just starting a review of the pancadastre outputs. I see the summary does not include coordinates. Was this intentional?

[andrewhunter2066]

For the 3D output I didn't see the height value anywhere? Is that intentional? Doesn't help with understanding the points are 3D points.

[andrewhunter2066]

For the NZ arc observation the ArcWithCentre is drawn incorrectly. The arc should be to the left of the chord between the start and end point. It is on the right the centre point.

The ArcByChord is not displaying. I have added a linestring for the chord, which the observation refers to.

Getting the following error report

build/tests/profiles/nz/arc-observations.jsonld
Unexpected observedVector topology-type:  ArcByChord
WARNING: Non-contiguous line segments! Line 0(0 -> 1) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 1(2 -> 3) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 2(4 -> 5) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 3(6 -> 7) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments (last)! Line 4(8 -> 9) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 0(0 -> 1) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 1(2 -> 3) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 2(4 -> 5) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 3(6 -> 7) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments (last)! Line 4(8 -> 9) [Line 0(0 -> 1), Line 1(2 -> 3), Line 2(4 -> 5), Line 3(6 -> 7), Line 4(8 -> 9)]
WARNING: Non-contiguous line segments! Line 0(10 -> 11) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 1(12 -> 13) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 2(14 -> 15) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 3(16 -> 17) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments (last)! Line 4(18 -> 19) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 0(10 -> 11) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 1(12 -> 13) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 2(14 -> 15) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments! Line 3(16 -> 17) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]
WARNING: Non-contiguous line segments (last)! Line 4(18 -> 19) [Line 0(10 -> 11), Line 1(12 -> 13), Line 2(14 -> 15), Line 3(16 -> 17), Line 4(18 -> 19)]

[andrewhunter2066]

The VIC extended example seems to have passed validation, the error report says

build/tests/profiles/vic/extended-example.jsonld
'str' object has no attribute 'get'

but there is no GeoJSON nor summary report. Any idea why?

[andrewhunter2066]

The WA Subtended Observation Angle has no summary report. The error report says:

build/tests/profiles/wa/obs-subtendedangle.jsonld
'ReducedObservation' object has no attribute 'stationName'

Not sure why ReducedObservation is being referred to, nor stationName as neither are CSDM terms.

[andrewhunter2066]

parcels-angles.jsonld-geojson.json doesn't include a polygon? Nor a summary report. The error report says '''' build/tests/profiles/wa/parcels-angles.jsonld 'ReducedObservation' object has no attribute 'stationName' ''''

[andrewhunter2066]

parcels.jsonld-geojson.json doesn't include a polygon?

[alcinnz]

I made an interface change, & the rerun of the GitHub action I just triggered should give you a "-parcel.json" file.

[andrewhunter2066]

Same issue with: secondary-parcel.jsonld-geojson.json circle-parcel.jsonld-geojson.json

• no polygons

[andrewhunter2066]

No related documents are reported in the summary for build/tests/profiles/wa/related_documents.jsonld

[andrewhunter2066]

WA topographic string is reporting the following errors:

build/tests/profiles/wa/topographic-string.jsonld
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
Invalid schema! Not attaching monument info!
WARNING! Subtended angle setup referencing an observation instead of point!
Unresolvable link or missing property! 'v11'

Passed validation

Same issue with spline version

[andrewhunter2066]

Getting the following error reported for the WA extended example:

build/tests/profiles/wa/extended-example.jsonld
Unresolvable link or missing property! 'features'

The error it is reporting was fixed yesterday...need to see what is going on.

[alcinnz]

"-parcel.json" files are now being generated, the polygons have been moved there. I checked.

I thought this way would look cleaner, but it just seems to be causing confusion.

[ByronCinNZ]

We have found that this occurs when the order for subtended angles is obs, obs, pnt instead pnt, obs, obs

On 14/12/2023, at 12:48 PM, Andrew Hunter @.***> wrote:

WA topographic string is reporting the following errors:

build/tests/profiles/wa/topographic-string.jsonld Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! Invalid schema! Not attaching monument info! WARNING! Subtended angle setup referencing an observation instead of point! Unresolvable link or missing property! 'v11' — Reply to this email directly, view it on GitHub https://github.com/OpenWork-NZ/pancadastre/issues/15#issuecomment-1854866664, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIJCPCZO2FEFRAGTRTO4NDYJI5ELAVCNFSM6AAAAAA73UTCBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUHA3DMNRWGQ. You are receiving this because you are subscribed to this thread.