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

Layer CRS has to match project CRS #58

Closed
m-kuhn opened this issue Jul 22, 2016 · 6 comments
Closed

Layer CRS has to match project CRS #58

m-kuhn opened this issue Jul 22, 2016 · 6 comments

Comments

@m-kuhn
Copy link
Member

m-kuhn commented Jul 22, 2016

Newly added geometries are always written to the layer in project CRS.

If the two CRS definitions do not match, the newly added geometry ends up at the wrong position.

Digitizied geometries will need to be reprojected into the layer CRS before saving.

For now, just make sure that the two CRS match for layers for which you want to digitize geometries.

@ludodo
Copy link

ludodo commented Jul 22, 2016

Well, I managed to have all my layers in the same projection EPSG 3857, no more projection on the fly in the project.
Still doesn't work. I join the project file, maybe something is wrong I don't see ?

formation_projet_qfield_45.qgs.txt

@m-kuhn
Copy link
Member Author

m-kuhn commented Jul 22, 2016

I remember having troubles with shp. Can you save the layer as spatialite and try with that? Make sure it's added with the spatialite provider and not with the ogr provider. (Layer => Add => SpatiaLite)

@ludodo
Copy link

ludodo commented Jul 22, 2016

Well well...
I transformed 3 layers in spatialite, 2 polygons layers and the point one. The polyline layer didn't pass in the spatialite file. So I had it in the project as Shapefile.
Result : edition works both for the point layer in the spatialite base AND for the polyline layer that didn't work until this...

Conclusion :

  • be careful to have the same SCR for all layers and the project,
  • shapefile can cause problems, but not all time !

Thank's a lot for your help and for this project in wich I really believe.
By the way do you plan to develop :

  • polygon editing ?
  • layer control ?

@m-kuhn
Copy link
Member Author

m-kuhn commented Jul 22, 2016

shapefile can cause problems, but not all time !

Were you able to isolate the cause?

By the way do you plan to develop :

  • polygon editing ?
  • layer control ?
  • Polygon is very probable to be included in a nearby project
  • Layer control is a big topic. We have no (closeby) project dealing with this. I started to write down some ideas in Legend #59. Volunteers for sponsoring welcome :)

@ludodo
Copy link

ludodo commented Jul 22, 2016

I think my layer's origin is part of the problem. This is IGN's data (french institutional organism in geographic data) from BD Topo in a strange SCR and not in UTF8 encoding. I already had problems to transform them from shapefile to spatialite and had to cut the data with my study zone to make it work.

We (french Conservatoires espaces naturels) recently little sponsored the Qgis project. Maybe I could suggest to have a look to Qfield project too ?

@m-kuhn
Copy link
Member Author

m-kuhn commented Jul 22, 2016

I think my layer's origin is part of the problem. This is IGN's data (french institutional organism in geographic data) from BD Topo in a strange SCR and not in UTF8 encoding. I already had problems to transform them from shapefile to spatialite and had to cut the data with my study zone to make it work.

If you have any indication that you think may be helpful to identify the root of this problem, please let me know.

We (french Conservatoires espaces naturels) recently little sponsored the Qgis project. Maybe I could suggest to have a look to Qfield project too ?

Much appreciated 👍
Si tu vois des possibilités, n’hésite pas nous contacter.

m-kuhn added a commit that referenced this issue Sep 3, 2016
@m-kuhn m-kuhn closed this as completed in 43f026c Sep 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants