Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some area geometries created in Territory exports as LineString #743

Open
rudokemper opened this issue Aug 14, 2023 · 1 comment
Open

Some area geometries created in Territory exports as LineString #743

rudokemper opened this issue Aug 14, 2023 · 1 comment
Labels

Comments

@rudokemper
Copy link
Member

Describe the bug
In Territory, when an Area is created with a preset that can be mapped only as an area (and not line), the feature type in the GeoJSON export is LineString instead of the expected Polygon. This appears only to be happening for presets that can be created as an area exclusively - for presets that can be mapped as both area and line geometry types, the GeoJSON type is set to the correct geometry.

Can you do the same thing twice?
The exact steps to see the problem again.

  1. Import a configuration that has some presets with only the area value, and some presets with both area and line values, in the geometry key (and the same association in defaults.json)
  2. In Mapeo Desktop Territory, create some areas with both of these presets.
  3. Export the data as GeoJSON.
  4. See that the areas created with a preset with only area geometry will be exported as LineString

Expected behavior
Areas should always be type: polygon.

Screenshots
image

Mapeo Version:

  • Desktop v5.6.0
@rudokemper rudokemper added the bug label Aug 14, 2023
@jencastrodoesstuff
Copy link

I'm very sure I know less than you all here but I recall an older instruction for writing preset jsons. That all needed to be points even if they were polygons. I'm pretty sure any of my technical knowledge on the territory date and the config builder is way out of date.
@rudokemper can I confirm that you were able to replicate the issue with the default as well?
I'm pretty sure that there was no work done on export features recently.
All energy is going into the refactor these days so fixing bugs is an easier process for our team.
I can flag this issue as part of the export revisioning that we started last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants